public class DebitMemoReqItemPrcgElmnt extends VdmEntity<DebitMemoReqItemPrcgElmnt>
Original entity name from the Odata EDM: A_DebitMemoReqItemPrcgElmntType
Modifier and Type | Class and Description |
---|---|
static class |
DebitMemoReqItemPrcgElmnt.DebitMemoReqItemPrcgElmntBuilder
Helper class to allow for fluent creation of DebitMemoReqItemPrcgElmnt instances.
|
Modifier and Type | Field and Description |
---|---|
static DebitMemoReqItemPrcgElmntField<String> |
ACCESS_NUMBER_OF_ACCESS_SEQUENCE
Use with available fluent helpers to apply the AccessNumberOfAccessSequence field to query operations.
|
static DebitMemoReqItemPrcgElmntSelectable |
ALL_FIELDS
Selector for all available fields of DebitMemoReqItemPrcgElmnt.
|
static DebitMemoReqItemPrcgElmntField<Boolean> |
CNDN_IS_RELEVANT_FOR_INTCO_BILLING
Use with available fluent helpers to apply the CndnIsRelevantForIntcoBilling field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CNDN_IS_RELEVANT_FOR_INVOICE_LIST
Use with available fluent helpers to apply the CndnIsRelevantForInvoiceList field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CNDN_ROUNDING_OFF_DIFF_AMOUNT
Use with available fluent helpers to apply the CndnRoundingOffDiffAmount field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_ALTERNATIVE_CURRENCY
Use with available fluent helpers to apply the ConditionAlternativeCurrency field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_AMOUNT
Use with available fluent helpers to apply the ConditionAmount field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_AMOUNT_IN_LOCAL_CRCY
Use with available fluent helpers to apply the ConditionAmountInLocalCrcy field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_APPLICATION
Use with available fluent helpers to apply the ConditionApplication field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_BASE_VALUE
Use with available fluent helpers to apply the ConditionBaseValue field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_CALCULATION_TYPE
Use with available fluent helpers to apply the ConditionCalculationType field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_CATEGORY
Use with available fluent helpers to apply the ConditionCategory field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_CLASS
Use with available fluent helpers to apply the ConditionClass field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_CONTROL
Use with available fluent helpers to apply the ConditionControl field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_CURRENCY
Use with available fluent helpers to apply the ConditionCurrency field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_INACTIVE_REASON
Use with available fluent helpers to apply the ConditionInactiveReason field to query operations.
|
static DebitMemoReqItemPrcgElmntField<Boolean> |
CONDITION_IS_FOR_CONFIGURATION
Use with available fluent helpers to apply the ConditionIsForConfiguration field to query operations.
|
static DebitMemoReqItemPrcgElmntField<Boolean> |
CONDITION_IS_FOR_STATISTICS
Use with available fluent helpers to apply the ConditionIsForStatistics field to query operations.
|
static DebitMemoReqItemPrcgElmntField<Boolean> |
CONDITION_IS_MANUALLY_CHANGED
Use with available fluent helpers to apply the ConditionIsManuallyChanged field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_ORIGIN
Use with available fluent helpers to apply the ConditionOrigin field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_QUANTITY
Use with available fluent helpers to apply the ConditionQuantity field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_QUANTITY_UNIT
Use with available fluent helpers to apply the ConditionQuantityUnit field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_RATE_VALUE
Use with available fluent helpers to apply the ConditionRateValue field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_RECORD
Use with available fluent helpers to apply the ConditionRecord field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_SCALE_BASIS_CURRENCY
Use with available fluent helpers to apply the ConditionScaleBasisCurrency field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_SCALE_BASIS_UNIT
Use with available fluent helpers to apply the ConditionScaleBasisUnit field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_SCALE_BASIS_VALUE
Use with available fluent helpers to apply the ConditionScaleBasisValue field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_SEQUENTIAL_NUMBER
Use with available fluent helpers to apply the ConditionSequentialNumber field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_TO_BASE_QTY_DNMNTR
Use with available fluent helpers to apply the ConditionToBaseQtyDnmntr field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CONDITION_TO_BASE_QTY_NMRTR
Use with available fluent helpers to apply the ConditionToBaseQtyNmrtr field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
CONDITION_TYPE
Use with available fluent helpers to apply the ConditionType field to query operations.
|
static DebitMemoReqItemPrcgElmntField<BigDecimal> |
CUMULATED_CONDITION_BASIS_VALUE
Use with available fluent helpers to apply the CumulatedConditionBasisValue field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
DEBIT_MEMO_REQUEST
Use with available fluent helpers to apply the DebitMemoRequest field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
DEBIT_MEMO_REQUEST_ITEM
Use with available fluent helpers to apply the DebitMemoRequestItem field to query operations.
|
static DebitMemoReqItemPrcgElmntField<Double> |
FACTOR_FOR_CONDITION_BASIS_VALUE
Use with available fluent helpers to apply the FactorForConditionBasisValue field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
IS_GROUP_CONDITION
Use with available fluent helpers to apply the IsGroupCondition field to query operations.
|
static DebitMemoReqItemPrcgElmntField<Boolean> |
IS_RELEVANT_FOR_ACCRUAL
Use with available fluent helpers to apply the IsRelevantForAccrual field to query operations.
|
static DebitMemoReqItemPrcgElmntField<Double> |
PERIOD_FACTOR_FOR_CNDN_BASIS_VALUE
Use with available fluent helpers to apply the PeriodFactorForCndnBasisValue field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
PRCG_PROCEDURE_COUNTER_FOR_HEADER
Use with available fluent helpers to apply the PrcgProcedureCounterForHeader field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
PRICING_DATE_TIME
Use with available fluent helpers to apply the PricingDateTime field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
PRICING_PROCEDURE_COUNTER
Use with available fluent helpers to apply the PricingProcedureCounter field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
PRICING_PROCEDURE_STEP
Use with available fluent helpers to apply the PricingProcedureStep field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
PRICING_SCALE_BASIS
Use with available fluent helpers to apply the PricingScaleBasis field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
PRICING_SCALE_TYPE
Use with available fluent helpers to apply the PricingScaleType field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
STRUCTURE_CONDITION
Use with available fluent helpers to apply the StructureCondition field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
TAX_CODE
Use with available fluent helpers to apply the TaxCode field to query operations.
|
static DebitMemoReqItemPrcgElmntOneToOneLink<DebitMemoRequest> |
TO_DEBIT_MEMO_REQUEST
Use with available fluent helpers to apply the to_DebitMemoRequest navigation property to query
operations.
|
static DebitMemoReqItemPrcgElmntOneToOneLink<DebitMemoRequestItem> |
TO_DEBIT_MEMO_REQUEST_ITEM
Use with available fluent helpers to apply the to_DebitMemoRequestItem navigation property to query
operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
VARIANT_CONDITION
Use with available fluent helpers to apply the VariantCondition field to query operations.
|
static DebitMemoReqItemPrcgElmntField<String> |
WITHHOLDING_TAX_CODE
Use with available fluent helpers to apply the WithholdingTaxCode field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
DebitMemoReqItemPrcgElmnt() |
DebitMemoReqItemPrcgElmnt(String debitMemoRequest,
String debitMemoRequestItem,
String pricingProcedureStep,
String pricingProcedureCounter,
String conditionApplication,
String conditionType,
String pricingDateTime,
String conditionCalculationType,
BigDecimal conditionBaseValue,
BigDecimal conditionRateValue,
String conditionCurrency,
BigDecimal conditionQuantity,
String conditionQuantityUnit,
BigDecimal conditionToBaseQtyNmrtr,
BigDecimal conditionToBaseQtyDnmntr,
String conditionCategory,
Boolean conditionIsForStatistics,
String pricingScaleType,
Boolean isRelevantForAccrual,
String cndnIsRelevantForInvoiceList,
String conditionOrigin,
String isGroupCondition,
String accessNumberOfAccessSequence,
String conditionRecord,
String conditionSequentialNumber,
String taxCode,
String withholdingTaxCode,
BigDecimal cndnRoundingOffDiffAmount,
BigDecimal conditionAmount,
String transactionCurrency,
String conditionControl,
String conditionInactiveReason,
String conditionClass,
String prcgProcedureCounterForHeader,
Double factorForConditionBasisValue,
String structureCondition,
Double periodFactorForCndnBasisValue,
String pricingScaleBasis,
BigDecimal conditionScaleBasisValue,
String conditionScaleBasisUnit,
String conditionScaleBasisCurrency,
String conditionAlternativeCurrency,
BigDecimal conditionAmountInLocalCrcy,
Boolean cndnIsRelevantForIntcoBilling,
Boolean conditionIsManuallyChanged,
BigDecimal cumulatedConditionBasisValue,
Boolean conditionIsForConfiguration,
String variantCondition,
DebitMemoRequest toDebitMemoRequest,
DebitMemoRequestItem toDebitMemoRequestItem) |
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 DebitMemoReqItemPrcgElmnt.DebitMemoReqItemPrcgElmntBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
DebitMemoRequest |
fetchDebitMemoRequest()
Fetches the DebitMemoRequest entity (one to one) associated with this entity.
|
DebitMemoRequestItem |
fetchDebitMemoRequestItem()
Fetches the DebitMemoRequestItem entity (one to one) associated with this entity.
|
static <T> DebitMemoReqItemPrcgElmntField<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 |
getAccessNumberOfAccessSequence()
Constraints: Not nullable, Maximum length: 3
|
Boolean |
getCndnIsRelevantForIntcoBilling()
Constraints: none
|
String |
getCndnIsRelevantForInvoiceList()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getCndnRoundingOffDiffAmount()
Constraints: Not nullable, Precision: 6, Scale: 3
|
String |
getConditionAlternativeCurrency()
Constraints: Not nullable, Maximum length: 5
|
BigDecimal |
getConditionAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
BigDecimal |
getConditionAmountInLocalCrcy()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getConditionApplication()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getConditionBaseValue()
Constraints: Not nullable, Precision: 24, Scale: 9
|
String |
getConditionCalculationType()
Constraints: Not nullable, Maximum length: 3
|
String |
getConditionCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getConditionClass()
Constraints: Not nullable, Maximum length: 1
|
String |
getConditionControl()
Constraints: Not nullable, Maximum length: 1
|
String |
getConditionCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getConditionInactiveReason()
Constraints: Not nullable, Maximum length: 1
|
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
|
String |
getConditionQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getConditionRateValue()
Constraints: Not nullable, Precision: 24, Scale: 9
|
String |
getConditionRecord()
Constraints: Not nullable, Maximum length: 10
|
String |
getConditionScaleBasisCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getConditionScaleBasisUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getConditionScaleBasisValue()
Constraints: Not nullable, Precision: 24, Scale: 9
|
String |
getConditionSequentialNumber()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getConditionToBaseQtyDnmntr()
Constraints: Not nullable, Precision: 10, Scale: 0
|
BigDecimal |
getConditionToBaseQtyNmrtr()
Constraints: Not nullable, Precision: 10, Scale: 0
|
String |
getConditionType()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getCumulatedConditionBasisValue()
Constraints: Not nullable, Precision: 24, Scale: 9
|
String |
getDebitMemoRequest()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
io.vavr.control.Option<DebitMemoRequest> |
getDebitMemoRequestIfPresent()
Retrieval of associated DebitMemoRequest entity (one to one).
|
String |
getDebitMemoRequestItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
io.vavr.control.Option<DebitMemoRequestItem> |
getDebitMemoRequestItemIfPresent()
Retrieval of associated DebitMemoRequestItem entity (one to one).
|
DebitMemoRequestItem |
getDebitMemoRequestItemOrFetch()
Retrieval of associated DebitMemoRequestItem entity (one to one).
|
DebitMemoRequest |
getDebitMemoRequestOrFetch()
Retrieval of associated DebitMemoRequest entity (one to one).
|
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.
|
Double |
getFactorForConditionBasisValue()
Constraints: none
|
String |
getIsGroupCondition()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getIsRelevantForAccrual()
Constraints: none
|
protected Map<String,Object> |
getKey() |
Double |
getPeriodFactorForCndnBasisValue()
Constraints: none
|
String |
getPrcgProcedureCounterForHeader()
Constraints: Not nullable, Maximum length: 3
|
String |
getPricingDateTime()
Constraints: Not nullable, Maximum length: 14
|
String |
getPricingProcedureCounter()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getPricingProcedureStep()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getPricingScaleBasis()
Constraints: Not nullable, Maximum length: 3
|
String |
getPricingScaleType()
Constraints: Not nullable, Maximum length: 1
|
String |
getStructureCondition()
Constraints: Not nullable, Maximum length: 1
|
String |
getTaxCode()
Constraints: Not nullable, Maximum length: 2
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<DebitMemoReqItemPrcgElmnt> |
getType() |
String |
getVariantCondition()
Constraints: Not nullable, Maximum length: 26
|
String |
getWithholdingTaxCode()
Constraints: Not nullable, Maximum length: 2
|
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 |
setCndnRoundingOffDiffAmount(BigDecimal cndnRoundingOffDiffAmount)
Constraints: Not nullable, Precision: 6, Scale: 3
|
void |
setConditionAlternativeCurrency(String conditionAlternativeCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionAmount(BigDecimal conditionAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setConditionAmountInLocalCrcy(BigDecimal conditionAmountInLocalCrcy)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setConditionApplication(String conditionApplication)
Constraints: Not nullable, Maximum length: 2
|
void |
setConditionBaseValue(BigDecimal conditionBaseValue)
Constraints: Not nullable, Precision: 24, Scale: 9
|
void |
setConditionCalculationType(String conditionCalculationType)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionCategory(String conditionCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionClass(String conditionClass)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionControl(String conditionControl)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionCurrency(String conditionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionInactiveReason(String conditionInactiveReason)
Constraints: Not nullable, Maximum length: 1
|
void |
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
|
void |
setConditionQuantityUnit(String conditionQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionRateValue(BigDecimal conditionRateValue)
Constraints: Not nullable, Precision: 24, Scale: 9
|
void |
setConditionRecord(String conditionRecord)
Constraints: Not nullable, Maximum length: 10
|
void |
setConditionScaleBasisCurrency(String conditionScaleBasisCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionScaleBasisUnit(String conditionScaleBasisUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionScaleBasisValue(BigDecimal conditionScaleBasisValue)
Constraints: Not nullable, Precision: 24, Scale: 9
|
void |
setConditionSequentialNumber(String conditionSequentialNumber)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionToBaseQtyDnmntr(BigDecimal conditionToBaseQtyDnmntr)
Constraints: Not nullable, Precision: 10, Scale: 0
|
void |
setConditionToBaseQtyNmrtr(BigDecimal conditionToBaseQtyNmrtr)
Constraints: Not nullable, Precision: 10, Scale: 0
|
void |
setConditionType(String conditionType)
Constraints: Not nullable, Maximum length: 4
|
void |
setCumulatedConditionBasisValue(BigDecimal cumulatedConditionBasisValue)
Constraints: Not nullable, Precision: 24, Scale: 9
|
void |
setDebitMemoRequest(DebitMemoRequest value)
Overwrites the associated DebitMemoRequest entity for the loaded navigation property
to_DebitMemoRequest.
|
void |
setDebitMemoRequest(String debitMemoRequest)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setDebitMemoRequestItem(DebitMemoRequestItem value)
Overwrites the associated DebitMemoRequestItem entity for the loaded navigation property
to_DebitMemoRequestItem.
|
void |
setDebitMemoRequestItem(String debitMemoRequestItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setFactorForConditionBasisValue(Double factorForConditionBasisValue)
Constraints: none
|
void |
setIsGroupCondition(String isGroupCondition)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsRelevantForAccrual(Boolean isRelevantForAccrual)
Constraints: none
|
void |
setPeriodFactorForCndnBasisValue(Double periodFactorForCndnBasisValue)
Constraints: none
|
void |
setPrcgProcedureCounterForHeader(String prcgProcedureCounterForHeader)
Constraints: Not nullable, Maximum length: 3
|
void |
setPricingDateTime(String pricingDateTime)
Constraints: Not nullable, Maximum length: 14
|
void |
setPricingProcedureCounter(String pricingProcedureCounter)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setPricingProcedureStep(String pricingProcedureStep)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setPricingScaleBasis(String pricingScaleBasis)
Constraints: Not nullable, Maximum length: 3
|
void |
setPricingScaleType(String pricingScaleType)
Constraints: Not nullable, Maximum length: 1
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setStructureCondition(String structureCondition)
Constraints: Not nullable, Maximum length: 1
|
void |
setTaxCode(String taxCode)
Constraints: Not nullable, Maximum length: 2
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setVariantCondition(String variantCondition)
Constraints: Not nullable, Maximum length: 26
|
void |
setWithholdingTaxCode(String withholdingTaxCode)
Constraints: Not nullable, Maximum length: 2
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final DebitMemoReqItemPrcgElmntSelectable ALL_FIELDS
public static final DebitMemoReqItemPrcgElmntField<String> DEBIT_MEMO_REQUEST
public static final DebitMemoReqItemPrcgElmntField<String> DEBIT_MEMO_REQUEST_ITEM
public static final DebitMemoReqItemPrcgElmntField<String> PRICING_PROCEDURE_STEP
public static final DebitMemoReqItemPrcgElmntField<String> PRICING_PROCEDURE_COUNTER
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_APPLICATION
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_TYPE
public static final DebitMemoReqItemPrcgElmntField<String> PRICING_DATE_TIME
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_CALCULATION_TYPE
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_BASE_VALUE
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_RATE_VALUE
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_CURRENCY
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_QUANTITY
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_QUANTITY_UNIT
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_TO_BASE_QTY_NMRTR
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_TO_BASE_QTY_DNMNTR
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_CATEGORY
public static final DebitMemoReqItemPrcgElmntField<Boolean> CONDITION_IS_FOR_STATISTICS
public static final DebitMemoReqItemPrcgElmntField<String> PRICING_SCALE_TYPE
public static final DebitMemoReqItemPrcgElmntField<Boolean> IS_RELEVANT_FOR_ACCRUAL
public static final DebitMemoReqItemPrcgElmntField<String> CNDN_IS_RELEVANT_FOR_INVOICE_LIST
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_ORIGIN
public static final DebitMemoReqItemPrcgElmntField<String> IS_GROUP_CONDITION
public static final DebitMemoReqItemPrcgElmntField<String> ACCESS_NUMBER_OF_ACCESS_SEQUENCE
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_RECORD
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_SEQUENTIAL_NUMBER
public static final DebitMemoReqItemPrcgElmntField<String> TAX_CODE
public static final DebitMemoReqItemPrcgElmntField<String> WITHHOLDING_TAX_CODE
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CNDN_ROUNDING_OFF_DIFF_AMOUNT
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_AMOUNT
public static final DebitMemoReqItemPrcgElmntField<String> TRANSACTION_CURRENCY
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_CONTROL
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_INACTIVE_REASON
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_CLASS
public static final DebitMemoReqItemPrcgElmntField<String> PRCG_PROCEDURE_COUNTER_FOR_HEADER
public static final DebitMemoReqItemPrcgElmntField<Double> FACTOR_FOR_CONDITION_BASIS_VALUE
public static final DebitMemoReqItemPrcgElmntField<String> STRUCTURE_CONDITION
public static final DebitMemoReqItemPrcgElmntField<Double> PERIOD_FACTOR_FOR_CNDN_BASIS_VALUE
public static final DebitMemoReqItemPrcgElmntField<String> PRICING_SCALE_BASIS
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_SCALE_BASIS_VALUE
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_SCALE_BASIS_UNIT
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_SCALE_BASIS_CURRENCY
public static final DebitMemoReqItemPrcgElmntField<String> CONDITION_ALTERNATIVE_CURRENCY
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CONDITION_AMOUNT_IN_LOCAL_CRCY
public static final DebitMemoReqItemPrcgElmntField<Boolean> CNDN_IS_RELEVANT_FOR_INTCO_BILLING
public static final DebitMemoReqItemPrcgElmntField<Boolean> CONDITION_IS_MANUALLY_CHANGED
public static final DebitMemoReqItemPrcgElmntField<BigDecimal> CUMULATED_CONDITION_BASIS_VALUE
public static final DebitMemoReqItemPrcgElmntField<Boolean> CONDITION_IS_FOR_CONFIGURATION
public static final DebitMemoReqItemPrcgElmntField<String> VARIANT_CONDITION
public static final DebitMemoReqItemPrcgElmntOneToOneLink<DebitMemoRequest> TO_DEBIT_MEMO_REQUEST
public static final DebitMemoReqItemPrcgElmntOneToOneLink<DebitMemoRequestItem> TO_DEBIT_MEMO_REQUEST_ITEM
public DebitMemoReqItemPrcgElmnt()
public DebitMemoReqItemPrcgElmnt(@Nullable String debitMemoRequest, @Nullable String debitMemoRequestItem, @Nullable String pricingProcedureStep, @Nullable String pricingProcedureCounter, @Nullable String conditionApplication, @Nullable String conditionType, @Nullable String pricingDateTime, @Nullable String conditionCalculationType, @Nullable BigDecimal conditionBaseValue, @Nullable BigDecimal conditionRateValue, @Nullable String conditionCurrency, @Nullable BigDecimal conditionQuantity, @Nullable String conditionQuantityUnit, @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 String accessNumberOfAccessSequence, @Nullable String conditionRecord, @Nullable String conditionSequentialNumber, @Nullable String taxCode, @Nullable String withholdingTaxCode, @Nullable BigDecimal cndnRoundingOffDiffAmount, @Nullable BigDecimal conditionAmount, @Nullable String transactionCurrency, @Nullable String conditionControl, @Nullable String conditionInactiveReason, @Nullable String conditionClass, @Nullable String prcgProcedureCounterForHeader, @Nullable Double factorForConditionBasisValue, @Nullable String structureCondition, @Nullable Double periodFactorForCndnBasisValue, @Nullable String pricingScaleBasis, @Nullable BigDecimal conditionScaleBasisValue, @Nullable String conditionScaleBasisUnit, @Nullable String conditionScaleBasisCurrency, @Nullable String conditionAlternativeCurrency, @Nullable BigDecimal conditionAmountInLocalCrcy, @Nullable Boolean cndnIsRelevantForIntcoBilling, @Nullable Boolean conditionIsManuallyChanged, @Nullable BigDecimal cumulatedConditionBasisValue, @Nullable Boolean conditionIsForConfiguration, @Nullable String variantCondition, @Nullable DebitMemoRequest toDebitMemoRequest, @Nullable DebitMemoRequestItem toDebitMemoRequestItem)
@Nonnull public Class<DebitMemoReqItemPrcgElmnt> getType()
getType
in class VdmObject<DebitMemoReqItemPrcgElmnt>
public void setDebitMemoRequest(@Nullable String debitMemoRequest)
Original property name from the Odata EDM: DebitMemoRequest
debitMemoRequest
- The number that uniquely identifies the sales document.public void setDebitMemoRequestItem(@Nullable String debitMemoRequestItem)
Original property name from the Odata EDM: DebitMemoRequestItem
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.
debitMemoRequestItem
- The number that uniquely identifies the condition item.public void setPricingProcedureStep(@Nullable String pricingProcedureStep)
Original property name from the Odata EDM: PricingProcedureStep
pricingProcedureStep
- Number that determines the sequence of the condition within a procedure.public void setPricingProcedureCounter(@Nullable String pricingProcedureCounter)
Original property name from the Odata EDM: PricingProcedureCounter
During automatic pricing, the system takes into account the sequence specified by the counter.
pricingProcedureCounter
- Access number of the conditions within a step in the pricing procedure.public void setConditionApplication(@Nullable String conditionApplication)
Original property name from the Odata EDM: ConditionApplication
conditionApplication
- Subdivides the usage of a condition (for example, pricing) for use in different application areas (for
example, sales & distribution or purchasing).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 setPricingDateTime(@Nullable String pricingDateTime)
Original property name from the Odata EDM: PricingDateTime
pricingDateTime
- Timestamp for Pricingpublic void setConditionCalculationType(@Nullable String conditionCalculationType)
Original property name from the Odata EDM: ConditionCalculationType
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.
conditionCalculationType
- Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the
system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or
weight.public void setConditionBaseValue(@Nullable BigDecimal conditionBaseValue)
Original property name from the Odata EDM: ConditionBaseValue
During the pricing process in a business document, for each condition type used in the pricing procedure, the system calculates the condition value as follows:For several calculation types (for example, A, C, D, E, F, H, I, J, K, M, N, O, P, W), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, A, C, D, E, F, H, I, M, N, O, P), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, C, D, E, F, H, I, M, N, O, P), the value of the condition basis refers to a unit of measure. If the unit of measure of the conditions basis differs from the unit of measure of the price condition (condition unit), the system automatically converts it into the unit of measure of the condition unit. For calculation types C, M, N, O, and P, the item quantity is the default value for the condition basis.For several calculation types (for example, A, B, H, I, J, K, W), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.For several calculation types (for example, A, B, H, I), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.Note: The standard number of decimal places for a currency is two.Currencies that use a different number of decimal places must in addition be entered into table TCURX, where you can explicitly define the number of decimal places, for example, zero decimals for Japanese yen JPY.Deviations are preconfigured depending on the currency, for example, zero decimals for Japanese yen JPY.If you have defined scales, the system uses the condition basis to determine the valid scale line with the corresponding condition amount.In usage-based pricing models, the usage corresponds to the condition basis.The condition basis can be aQuantityWeightVolumeCurrency AmountA sales order includes an item with a quantity of 120 pieces:The determined list price of USD 101 (condition amount) multiplied with the quantity of 120 pieces (condition basis) results in a condition value of USD 12120.Two discounts are applied to the item of this sales order:The first discount (-1 USD / PC) is based on the quantity ordered that is the condition basis equals the item quantity and the result is - 120 USD.The second discount (- 2 %) is calculated as a percentage which is applied to the results of the list price (USD 12120) and the first discount (- 120 USD). Its result (12000 USD) is the condition basis for the second discount. The result of the second discount is - 240 USD.
conditionBaseValue
- Defines the value in a business document that the system uses together with the condition amount to
calculate the condition value for the price condition.public void setConditionRateValue(@Nullable BigDecimal conditionRateValue)
Original property name from the Odata EDM: ConditionRateValue
Depending on the condition type, it can be a fixed amount, a percentage, or per mille. If the condition includes a pricing scale, the condition amount or percentage displays the first line of the scale.The following examples illustrate how you can use the condition amount or percentage in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you create a condition based on percentage, such as discounts or surcharges (for example, a customer-specific discount), you enter the value of a percentage. If the condition is a discount, the system automatically enters a minus sign behind the amount and a percent sign in the Condition Unit field.
conditionRateValue
- Determines how the system calculates prices using a specific condition.public void setConditionCurrency(@Nullable String conditionCurrency)
Original property name from the Odata EDM: ConditionCurrency
conditionCurrency
- Currency key for amounts in the system.public void setConditionQuantity(@Nullable BigDecimal conditionQuantity)
Original property name from the Odata EDM: ConditionQuantity
You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.
conditionQuantity
- The quantity on which the amount or percentage is based. The quantity is expressed in sales units (for
example, bottles).public void setConditionQuantityUnit(@Nullable String conditionQuantityUnit)
Original property name from the Odata EDM: ConditionQuantityUnit
conditionQuantityUnit
- Quantity unit, to which the condition amount or percentage refers.public void 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 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
- The denominator of the conversion factor that the system uses to convert condition units into base
units of measure.public void setConditionCategory(@Nullable String conditionCategory)
Original property name from the Odata EDM: ConditionCategory
conditionCategory
- A classification of conditions according to pre-defined categories (for example, all conditions that
relate to freight costs).public void setConditionIsForStatistics(@Nullable Boolean conditionIsForStatistics)
Original property name from the Odata EDM: ConditionIsForStatistics
conditionIsForStatistics
- This indicator causes a surcharge or discount to be set in the document statistically (that is,
without altering the value).public void 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 setIsRelevantForAccrual(@Nullable Boolean isRelevantForAccrual)
Original property name from the Odata EDM: IsRelevantForAccrual
If you mark this indicator, the condition appears in the document as a statistical condition.
isRelevantForAccrual
- Indicates that the system posts the amounts resulting from this condition to financial accounting as
accruals.public void setCndnIsRelevantForInvoiceList(@Nullable String cndnIsRelevantForInvoiceList)
Original property name from the Odata EDM: CndnIsRelevantForInvoiceList
cndnIsRelevantForInvoiceList
- Indicates that the condition type is relevant for internal costing.public void setConditionOrigin(@Nullable String conditionOrigin)
Original property name from the Odata EDM: ConditionOrigin
conditionOrigin
- Indicates where the condition originated (for example, whether you entered the condition manually or
whether the system determined it automatically).public void setIsGroupCondition(@Nullable String isGroupCondition)
Original property name from the Odata EDM: IsGroupCondition
For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.A sales order contains two items. Both items belong to the material group 01.Material Quantity Material groupA 150 01B 100 01The group condition indicator is set in the definition of the condition type for material group discounts. The condition record for material group 01 includes the following pricing scale:Scale quantity Discountfrom 1 pc -1%from 200 pc -2%Neither item alone qualifies for the 2% discount. However, when the items are combined as part of a group condition, the combined quantity creates a basis of 250 pieces. This basis then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount.
isGroupCondition
- Indicates whether the system calculates the scale base value or the condition value taking all related
items of the business document into account.public void setAccessNumberOfAccessSequence(@Nullable String accessNumberOfAccessSequence)
Original property name from the Odata EDM: AccessNumberOfAccessSequence
accessNumberOfAccessSequence
- Indicates the number of the access within the access sequence.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 setTaxCode(@Nullable String taxCode)
Original property name from the Odata EDM: TaxCode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
taxCode
- The tax code represents a tax category which must be taken into consideration when making a tax return
to the tax authorities.public void setWithholdingTaxCode(@Nullable String withholdingTaxCode)
Original property name from the Odata EDM: WithholdingTaxCode
Note that when processing a business transaction, no more than one withholding tax code can be assigned per withholding tax type. If the business transaction is subject to more than one withholding taxes, these must be represented in the system by defining various withholding tax types.
withholdingTaxCode
- One or more "withholding tax codes" are assigned to each withholding tax type. One of the things these
codes determine is the various percentage rates for the withholding tax type.public void setCndnRoundingOffDiffAmount(@Nullable BigDecimal cndnRoundingOffDiffAmount)
Original property name from the Odata EDM: CndnRoundingOffDiffAmount
cndnRoundingOffDiffAmount
- Rounding-Off Difference of the Conditionpublic void setConditionAmount(@Nullable BigDecimal conditionAmount)
Original property name from the Odata EDM: ConditionAmount
This value is used as a total for the condition in the pricing procedure.
conditionAmount
- The value, resulting from pricing, for a particular condition, total, or subtotal in a document.public void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency
- The currency that applies to the document (for example, to a sales order or an invoice).public void setConditionControl(@Nullable String conditionControl)
Original property name from the Odata EDM: ConditionControl
The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.
conditionControl
- Indicates whether the prices or values in a condition are fixed or whether and in what way they
changed.public void setConditionInactiveReason(@Nullable String conditionInactiveReason)
Original property name from the Odata EDM: ConditionInactiveReason
A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing
conditionInactiveReason
- Indicates if the condition is active.public void setConditionClass(@Nullable String conditionClass)
Original property name from the Odata EDM: ConditionClass
Allows standardized processing of individual condition classes within the system.
conditionClass
- Preliminary structuring of condition types, for example, in surcharges and discounts or prices.public void setPrcgProcedureCounterForHeader(@Nullable String prcgProcedureCounterForHeader)
Original property name from the Odata EDM: PrcgProcedureCounterForHeader
prcgProcedureCounterForHeader
- Condition Counter (Header)public void setFactorForConditionBasisValue(@Nullable Double factorForConditionBasisValue)
Original property name from the Odata EDM: FactorForConditionBasisValue
factorForConditionBasisValue
- Factor for Condition Base Valuepublic void setStructureCondition(@Nullable String structureCondition)
Original property name from the Odata EDM: StructureCondition
This control is only helpful when you use bill of materials or configurable materials:' ' - None'A' - Duplication Condition: A duplicated condition is duplicated into all assigned items.'B' - Cumulation Condition: A cumulated condition contains the net value of all assigned items.
structureCondition
- Controls whether the condition type is a duplicated condition or a cumulated condition.public void setPeriodFactorForCndnBasisValue(@Nullable Double periodFactorForCndnBasisValue)
Original property name from the Odata EDM: PeriodFactorForCndnBasisValue
periodFactorForCndnBasisValue
- Factor for Condition Basis (Period)public void setPricingScaleBasis(@Nullable String pricingScaleBasis)
Original property name from the Odata EDM: PricingScaleBasis
pricingScaleBasis
- Determines how the system interprets a pricing scale in a condition. For example, the scale can be
based on quantity, weight, or volume.public void setConditionScaleBasisValue(@Nullable BigDecimal conditionScaleBasisValue)
Original property name from the Odata EDM: ConditionScaleBasisValue
The scale base value can be a condition value or the value of a quantity, weight, and so on that has been entered in the document.You create a price condition based on a simple quantity scale with scale type A: Base scale:Quantity Price per Unit10 12 USD100 11 USD1000 10 USDA sales order item with 150 units qualifies for the condition scale quantity of 100 units and the price per unit of USD 11. In this case, the scale base value that determines the price is 150.
conditionScaleBasisValue
- A value or quantity that the system uses to access a pricing scale to determine a scale level.public void setConditionScaleBasisUnit(@Nullable String conditionScaleBasisUnit)
Original property name from the Odata EDM: ConditionScaleBasisUnit
conditionScaleBasisUnit
- Unit of measure to which the quantity scale refers.public void setConditionScaleBasisCurrency(@Nullable String conditionScaleBasisCurrency)
Original property name from the Odata EDM: 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
- Specifies a currency for a pricing scale in a condition record.public void setConditionAlternativeCurrency(@Nullable String conditionAlternativeCurrency)
Original property name from the Odata EDM: ConditionAlternativeCurrency
conditionAlternativeCurrency
- Condition Currency (for Cumulation Fields)public void setConditionAmountInLocalCrcy(@Nullable BigDecimal conditionAmountInLocalCrcy)
Original property name from the Odata EDM: ConditionAmountInLocalCrcy
This value is used as a total for the condition in the pricing procedure.
conditionAmountInLocalCrcy
- The value, resulting from pricing, for a particular condition, total, or subtotal in a document.public void setCndnIsRelevantForIntcoBilling(@Nullable Boolean cndnIsRelevantForIntcoBilling)
Original property name from the Odata EDM: CndnIsRelevantForIntcoBilling
Intercompany conditions are usually statistical in the sales order and the customer invoice and not statistical in the intercompany invoice.
cndnIsRelevantForIntcoBilling
- Indicator that defines a condition as relevant for the intercompany process.public void setConditionIsManuallyChanged(@Nullable Boolean conditionIsManuallyChanged)
Original property name from the Odata EDM: ConditionIsManuallyChanged
conditionIsManuallyChanged
- If this flag is set, the condition has been manually or automatically changed or created (by entry in
the condition screen).public void setCumulatedConditionBasisValue(@Nullable BigDecimal cumulatedConditionBasisValue)
Original property name from the Odata EDM: CumulatedConditionBasisValue
During the pricing process in a business document, for each condition type used in the pricing procedure, the system calculates the condition value as follows:For several calculation types (for example, A, C, D, E, F, H, I, J, K, M, N, O, P, W), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, A, C, D, E, F, H, I, M, N, O, P), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, C, D, E, F, H, I, M, N, O, P), the value of the condition basis refers to a unit of measure. If the unit of measure of the conditions basis differs from the unit of measure of the price condition (condition unit), the system automatically converts it into the unit of measure of the condition unit. For calculation types C, M, N, O, and P, the item quantity is the default value for the condition basis.For several calculation types (for example, A, B, H, I, J, K, W), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.For several calculation types (for example, A, B, H, I), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.Note: The standard number of decimal places for a currency is two.Currencies that use a different number of decimal places must in addition be entered into table TCURX, where you can explicitly define the number of decimal places, for example, zero decimals for Japanese yen JPY.Deviations are preconfigured depending on the currency, for example, zero decimals for Japanese yen JPY.If you have defined scales, the system uses the condition basis to determine the valid scale line with the corresponding condition amount.In usage-based pricing models, the usage corresponds to the condition basis.The condition basis can be aQuantityWeightVolumeCurrency AmountA sales order includes an item with a quantity of 120 pieces:The determined list price of USD 101 (condition amount) multiplied with the quantity of 120 pieces (condition basis) results in a condition value of USD 12120.Two discounts are applied to the item of this sales order:The first discount (-1 USD / PC) is based on the quantity ordered that is the condition basis equals the item quantity and the result is - 120 USD.The second discount (- 2 %) is calculated as a percentage which is applied to the results of the list price (USD 12120) and the first discount (- 120 USD). Its result (12000 USD) is the condition basis for the second discount. The result of the second discount is - 240 USD.
cumulatedConditionBasisValue
- Defines the value in a business document that the system uses together with the condition amount to
calculate the condition value for the price condition.public void setConditionIsForConfiguration(@Nullable Boolean conditionIsForConfiguration)
Original property name from the Odata EDM: ConditionIsForConfiguration
conditionIsForConfiguration
- A condition that is relevant for variant configuration.public void setVariantCondition(@Nullable String variantCondition)
Original property name from the Odata EDM: VariantCondition
To model the price for a variant of a configurable material, you typically use a larger number of variant condition keys.In a business document, the price for a selected variant is realized as surcharges and discounts specific for this variant: The sales price of a bike depends on the material that is used to produce the frame. You define a characteristic FRAME_MATERIAL that can have the values steel, aluminum, and carbon with the following surcharges:Steel: 0.0 USD per pieceAluminum: + 300 USD per pieceCarbon: + 1000 USD per pieceYou define three different variant condition keys FRAME_STEEL, FRAME_ALU, and FRAME_CARBON and maintain the above-mentioned surcharges as condition records. During order creation, you select the variant of the bike with the carbon frame. This will lead to a surcharge of 1000 USD that corresponds to the variant condition key FRAME_CARBON.
variantCondition
- Freely definable attribute that determines the valid price components of a configurable material.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<DebitMemoReqItemPrcgElmnt>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<DebitMemoReqItemPrcgElmnt>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<DebitMemoReqItemPrcgElmnt>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<DebitMemoReqItemPrcgElmnt>
@Nonnull public static <T> DebitMemoReqItemPrcgElmntField<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> DebitMemoReqItemPrcgElmntField<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<DebitMemoReqItemPrcgElmnt>
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<DebitMemoReqItemPrcgElmnt>
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<DebitMemoReqItemPrcgElmnt>
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<DebitMemoReqItemPrcgElmnt>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<DebitMemoReqItemPrcgElmnt>
@Nullable public DebitMemoRequest fetchDebitMemoRequest() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
null
if an entity is not associated.com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nullable public DebitMemoRequest getDebitMemoRequestOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_DebitMemoRequest of a queried DebitMemoReqItemPrcgElmnt is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<DebitMemoRequest> getDebitMemoRequestIfPresent()
If the navigation property for an entity DebitMemoReqItemPrcgElmnt has not been resolved yet, this method
will not query further information. Instead its Option
result state will be
empty
.
Option
with result state
empty
is returned.public void setDebitMemoRequest(DebitMemoRequest value)
value
- New DebitMemoRequest entity.@Nullable public DebitMemoRequestItem fetchDebitMemoRequestItem() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
null
if an entity is not associated.com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nullable public DebitMemoRequestItem getDebitMemoRequestItemOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_DebitMemoRequestItem of a queried DebitMemoReqItemPrcgElmnt is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<DebitMemoRequestItem> getDebitMemoRequestItemIfPresent()
If the navigation property for an entity DebitMemoReqItemPrcgElmnt has not been resolved yet, this method
will not query further information. Instead its Option
result state will be
empty
.
Option
with result state
empty
is returned.public void setDebitMemoRequestItem(DebitMemoRequestItem value)
value
- New DebitMemoRequestItem entity.@Nonnull public static DebitMemoReqItemPrcgElmnt.DebitMemoReqItemPrcgElmntBuilder builder()
@Nullable public String getDebitMemoRequest()
Original property name from the Odata EDM: DebitMemoRequest
@Nullable public String getDebitMemoRequestItem()
Original property name from the Odata EDM: DebitMemoRequestItem
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()
Original property name from the Odata EDM: PricingProcedureStep
@Nullable public String getPricingProcedureCounter()
Original property name from the Odata EDM: PricingProcedureCounter
During automatic pricing, the system takes into account the sequence specified by the counter.
@Nullable public String getConditionApplication()
Original property name from the Odata EDM: ConditionApplication
@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 getPricingDateTime()
Original property name from the Odata EDM: PricingDateTime
@Nullable public String getConditionCalculationType()
Original property name from the Odata EDM: ConditionCalculationType
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.
@Nullable public BigDecimal getConditionBaseValue()
Original property name from the Odata EDM: ConditionBaseValue
During the pricing process in a business document, for each condition type used in the pricing procedure, the system calculates the condition value as follows:For several calculation types (for example, A, C, D, E, F, H, I, J, K, M, N, O, P, W), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, A, C, D, E, F, H, I, M, N, O, P), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, C, D, E, F, H, I, M, N, O, P), the value of the condition basis refers to a unit of measure. If the unit of measure of the conditions basis differs from the unit of measure of the price condition (condition unit), the system automatically converts it into the unit of measure of the condition unit. For calculation types C, M, N, O, and P, the item quantity is the default value for the condition basis.For several calculation types (for example, A, B, H, I, J, K, W), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.For several calculation types (for example, A, B, H, I), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.Note: The standard number of decimal places for a currency is two.Currencies that use a different number of decimal places must in addition be entered into table TCURX, where you can explicitly define the number of decimal places, for example, zero decimals for Japanese yen JPY.Deviations are preconfigured depending on the currency, for example, zero decimals for Japanese yen JPY.If you have defined scales, the system uses the condition basis to determine the valid scale line with the corresponding condition amount.In usage-based pricing models, the usage corresponds to the condition basis.The condition basis can be aQuantityWeightVolumeCurrency AmountA sales order includes an item with a quantity of 120 pieces:The determined list price of USD 101 (condition amount) multiplied with the quantity of 120 pieces (condition basis) results in a condition value of USD 12120.Two discounts are applied to the item of this sales order:The first discount (-1 USD / PC) is based on the quantity ordered that is the condition basis equals the item quantity and the result is - 120 USD.The second discount (- 2 %) is calculated as a percentage which is applied to the results of the list price (USD 12120) and the first discount (- 120 USD). Its result (12000 USD) is the condition basis for the second discount. The result of the second discount is - 240 USD.
@Nullable public BigDecimal getConditionRateValue()
Original property name from the Odata EDM: ConditionRateValue
Depending on the condition type, it can be a fixed amount, a percentage, or per mille. If the condition includes a pricing scale, the condition amount or percentage displays the first line of the scale.The following examples illustrate how you can use the condition amount or percentage in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you create a condition based on percentage, such as discounts or surcharges (for example, a customer-specific discount), you enter the value of a percentage. If the condition is a discount, the system automatically enters a minus sign behind the amount and a percent sign in the Condition Unit field.
@Nullable public String getConditionCurrency()
Original property name from the Odata EDM: ConditionCurrency
@Nullable public BigDecimal getConditionQuantity()
Original property name from the Odata EDM: ConditionQuantity
You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.
@Nullable public String getConditionQuantityUnit()
Original property name from the Odata EDM: ConditionQuantityUnit
@Nullable public 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 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()
Original property name from the Odata EDM: ConditionCategory
@Nullable public Boolean getConditionIsForStatistics()
Original property name from the Odata EDM: ConditionIsForStatistics
@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 Boolean getIsRelevantForAccrual()
Original property name from the Odata EDM: IsRelevantForAccrual
If you mark this indicator, the condition appears in the document as a statistical condition.
@Nullable public String getCndnIsRelevantForInvoiceList()
Original property name from the Odata EDM: CndnIsRelevantForInvoiceList
@Nullable public String getConditionOrigin()
Original property name from the Odata EDM: ConditionOrigin
@Nullable public String getIsGroupCondition()
Original property name from the Odata EDM: IsGroupCondition
For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.A sales order contains two items. Both items belong to the material group 01.Material Quantity Material groupA 150 01B 100 01The group condition indicator is set in the definition of the condition type for material group discounts. The condition record for material group 01 includes the following pricing scale:Scale quantity Discountfrom 1 pc -1%from 200 pc -2%Neither item alone qualifies for the 2% discount. However, when the items are combined as part of a group condition, the combined quantity creates a basis of 250 pieces. This basis then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount.
@Nullable public String getAccessNumberOfAccessSequence()
Original property name from the Odata EDM: AccessNumberOfAccessSequence
@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 String getTaxCode()
Original property name from the Odata EDM: TaxCode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
@Nullable public String getWithholdingTaxCode()
Original property name from the Odata EDM: WithholdingTaxCode
Note that when processing a business transaction, no more than one withholding tax code can be assigned per withholding tax type. If the business transaction is subject to more than one withholding taxes, these must be represented in the system by defining various withholding tax types.
@Nullable public BigDecimal getCndnRoundingOffDiffAmount()
Original property name from the Odata EDM: CndnRoundingOffDiffAmount
@Nullable public BigDecimal getConditionAmount()
Original property name from the Odata EDM: ConditionAmount
This value is used as a total for the condition in the pricing procedure.
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable public String getConditionControl()
Original property name from the Odata EDM: ConditionControl
The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.
@Nullable public String getConditionInactiveReason()
Original property name from the Odata EDM: ConditionInactiveReason
A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing
@Nullable public String getConditionClass()
Original property name from the Odata EDM: ConditionClass
Allows standardized processing of individual condition classes within the system.
@Nullable public String getPrcgProcedureCounterForHeader()
Original property name from the Odata EDM: PrcgProcedureCounterForHeader
@Nullable public Double getFactorForConditionBasisValue()
Original property name from the Odata EDM: FactorForConditionBasisValue
@Nullable public String getStructureCondition()
Original property name from the Odata EDM: StructureCondition
This control is only helpful when you use bill of materials or configurable materials:' ' - None'A' - Duplication Condition: A duplicated condition is duplicated into all assigned items.'B' - Cumulation Condition: A cumulated condition contains the net value of all assigned items.
@Nullable public Double getPeriodFactorForCndnBasisValue()
Original property name from the Odata EDM: PeriodFactorForCndnBasisValue
@Nullable public String getPricingScaleBasis()
Original property name from the Odata EDM: PricingScaleBasis
@Nullable public BigDecimal getConditionScaleBasisValue()
Original property name from the Odata EDM: ConditionScaleBasisValue
The scale base value can be a condition value or the value of a quantity, weight, and so on that has been entered in the document.You create a price condition based on a simple quantity scale with scale type A: Base scale:Quantity Price per Unit10 12 USD100 11 USD1000 10 USDA sales order item with 150 units qualifies for the condition scale quantity of 100 units and the price per unit of USD 11. In this case, the scale base value that determines the price is 150.
@Nullable public String getConditionScaleBasisUnit()
Original property name from the Odata EDM: ConditionScaleBasisUnit
@Nullable public String getConditionScaleBasisCurrency()
Original property name from the Odata EDM: 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.
@Nullable public String getConditionAlternativeCurrency()
Original property name from the Odata EDM: ConditionAlternativeCurrency
@Nullable public BigDecimal getConditionAmountInLocalCrcy()
Original property name from the Odata EDM: ConditionAmountInLocalCrcy
This value is used as a total for the condition in the pricing procedure.
@Nullable public Boolean getCndnIsRelevantForIntcoBilling()
Original property name from the Odata EDM: CndnIsRelevantForIntcoBilling
Intercompany conditions are usually statistical in the sales order and the customer invoice and not statistical in the intercompany invoice.
@Nullable public Boolean getConditionIsManuallyChanged()
Original property name from the Odata EDM: ConditionIsManuallyChanged
@Nullable public BigDecimal getCumulatedConditionBasisValue()
Original property name from the Odata EDM: CumulatedConditionBasisValue
During the pricing process in a business document, for each condition type used in the pricing procedure, the system calculates the condition value as follows:For several calculation types (for example, A, C, D, E, F, H, I, J, K, M, N, O, P, W), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, A, C, D, E, F, H, I, M, N, O, P), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, C, D, E, F, H, I, M, N, O, P), the value of the condition basis refers to a unit of measure. If the unit of measure of the conditions basis differs from the unit of measure of the price condition (condition unit), the system automatically converts it into the unit of measure of the condition unit. For calculation types C, M, N, O, and P, the item quantity is the default value for the condition basis.For several calculation types (for example, A, B, H, I, J, K, W), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.For several calculation types (for example, A, B, H, I), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.Note: The standard number of decimal places for a currency is two.Currencies that use a different number of decimal places must in addition be entered into table TCURX, where you can explicitly define the number of decimal places, for example, zero decimals for Japanese yen JPY.Deviations are preconfigured depending on the currency, for example, zero decimals for Japanese yen JPY.If you have defined scales, the system uses the condition basis to determine the valid scale line with the corresponding condition amount.In usage-based pricing models, the usage corresponds to the condition basis.The condition basis can be aQuantityWeightVolumeCurrency AmountA sales order includes an item with a quantity of 120 pieces:The determined list price of USD 101 (condition amount) multiplied with the quantity of 120 pieces (condition basis) results in a condition value of USD 12120.Two discounts are applied to the item of this sales order:The first discount (-1 USD / PC) is based on the quantity ordered that is the condition basis equals the item quantity and the result is - 120 USD.The second discount (- 2 %) is calculated as a percentage which is applied to the results of the list price (USD 12120) and the first discount (- 120 USD). Its result (12000 USD) is the condition basis for the second discount. The result of the second discount is - 240 USD.
@Nullable public Boolean getConditionIsForConfiguration()
Original property name from the Odata EDM: ConditionIsForConfiguration
@Nullable public String getVariantCondition()
Original property name from the Odata EDM: VariantCondition
To model the price for a variant of a configurable material, you typically use a larger number of variant condition keys.In a business document, the price for a selected variant is realized as surcharges and discounts specific for this variant: The sales price of a bike depends on the material that is used to produce the frame. You define a characteristic FRAME_MATERIAL that can have the values steel, aluminum, and carbon with the following surcharges:Steel: 0.0 USD per pieceAluminum: + 300 USD per pieceCarbon: + 1000 USD per pieceYou define three different variant condition keys FRAME_STEEL, FRAME_ALU, and FRAME_CARBON and maintain the above-mentioned surcharges as condition records. During order creation, you select the variant of the bike with the carbon frame. This will lead to a surcharge of 1000 USD that corresponds to the variant condition key FRAME_CARBON.
@Nonnull public String toString()
toString
in class VdmObject<DebitMemoReqItemPrcgElmnt>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<DebitMemoReqItemPrcgElmnt>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<DebitMemoReqItemPrcgElmnt>
public int hashCode()
hashCode
in class VdmObject<DebitMemoReqItemPrcgElmnt>
Copyright © 2020 SAP SE. All rights reserved.