public static final class PurgPricingConditionType.PurgPricingConditionTypeBuilder extends Object
@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder text(PurgPrcgCndnTypeText... value)
value
- The PurgPrcgCndnTypeTexts to build this PurgPricingConditionType with.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionUsage(@Nullable String conditionUsage)
Original property name from the Odata EDM: ConditionUsage
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionApplication(@Nullable String conditionApplication)
Original property name from the Odata EDM: ConditionApplication
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionType(@Nullable String conditionType)
Original property name from the Odata EDM: ConditionType
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionCalculationType(@Nullable String conditionCalculationType)
Original property name from the Odata EDM: ConditionCalculationType
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder cndnManualEntries(@Nullable String cndnManualEntries)
Original property name from the Odata EDM: CndnManualEntries
Make the following entries according to your requirements:_: No limitationsA: Freely definableB: The automatic entry has priority. If a condition record exists, the condition cannot be entered manually.C: The manual entry has priority. When you enter the condition manually, the system does not check whether a condition record exists.D: Cannot be processed manually
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder cndnAppliesHeader(@Nullable Boolean cndnAppliesHeader)
Original property name from the Odata EDM: CndnAppliesHeader
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder cndnAppliesItems(@Nullable Boolean cndnAppliesItems)
Original property name from the Odata EDM: CndnAppliesItems
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionCategory(@Nullable String conditionCategory)
Original property name from the Odata EDM: ConditionCategory
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder accessSequence(@Nullable String accessSequence)
Original property name from the Odata EDM: AccessSequence
the condition tables used to access the condition recordsthe sequence of the condition tableswhich field contents are the criteria for reading the tables
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionClass(@Nullable String conditionClass)
Original property name from the Odata EDM: ConditionClass
Allows standardized processing of individual condition classes within the system.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnAmountRoundingRule(@Nullable String prcgCndnAmountRoundingRule)
Original property name from the Odata EDM: PrcgCndnAmountRoundingRule
In the standard rounding rule '_', values are rounded off according to business standards:10.454 -> 10.45 DEM10.455 -> 10.46 DEMIn rounding rule 'A', values are always rounded up:10.459 -> 10.46 DEM10.451 -> 10.46 DEMIn rounding rule 'B', values are always rounded down:1045.9 -> 1045 LIT1045.1 -> 1045 LITIn this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder structureCondition(@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.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgConditionAmountSign(@Nullable String prcgConditionAmountSign)
Original property name from the Odata EDM: PrcgConditionAmountSign
If the condition amount can be either positive or negative, leave the field blank. Otherwise, enter one of the indicators that specify plus or minus.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder isGroupCondition(@Nullable String isGroupCondition)
Original property name from the Odata EDM: IsGroupCondition
For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.A sales order contains two items. Both items belong to the material group 01.Material Quantity Material groupA 150 01B 100 01The group condition indicator is set in the definition of the condition type for material group discounts. The condition record for material group 01 includes the following pricing scale:Scale quantity Discountfrom 1 pc -1%from 200 pc -2%Neither item alone qualifies for the 2% discount. However, when the items are combined as part of a group condition, the combined quantity creates a basis of 250 pieces. This basis then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnRndngDiffsIsSettled(@Nullable Boolean prcgCndnRndngDiffsIsSettled)
Original property name from the Odata EDM: PrcgCndnRndngDiffsIsSettled
If the indicator is set, the system compares the condition value at header level with the total of the condition values at item level. The difference is then added to the largest item.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgGroupConditionRoutine(@Nullable String prcgGroupConditionRoutine)
Original property name from the Odata EDM: PrcgGroupConditionRoutine
You can specify a routine, for example, that totals the value of all items in a document in order to determine the basis for a discount.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnTypeDeletionIsAllowed(@Nullable Boolean prcgCndnTypeDeletionIsAllowed)
Original property name from the Odata EDM: PrcgCndnTypeDeletionIsAllowed
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnAmountChangedIsAllowed(@Nullable Boolean prcgCndnAmountChangedIsAllowed)
Original property name from the Odata EDM: PrcgCndnAmountChangedIsAllowed
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnCnvrsnFctrChgIsAllowed(@Nullable Boolean prcgCndnCnvrsnFctrChgIsAllowed)
Original property name from the Odata EDM: PrcgCndnCnvrsnFctrChgIsAllowed
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnValChgIsAllwd(@Nullable Boolean prcgCndnValChgIsAllwd)
Original property name from the Odata EDM: PrcgCndnValChgIsAllwd
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnPrpsdValidFromDateCode(@Nullable String prcgCndnPrpsdValidFromDateCode)
Original property name from the Odata EDM: PrcgCndnPrpsdValidFromDateCode
You can, for example, specify that the system proposes the first day of the current week, month, or year.If you want the system to propose the current date, leave the field blank. Otherwise, enter one of the values predefined for your system.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnPrpsdValidToDateCode(@Nullable String prcgCndnPrpsdValidToDateCode)
Original property name from the Odata EDM: PrcgCndnPrpsdValidToDateCode
The system proposes this value for the Valid to date when you create condition records.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder pricingProcedure(@Nullable String pricingProcedure)
Original property name from the Odata EDM: PricingProcedure
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgConditionDeletionMethod(@Nullable String prcgConditionDeletionMethod)
Original property name from the Odata EDM: PrcgConditionDeletionMethod
You have the following options:SPACE: You can set an indicator so that the condition record is no longer used in pricing. The condition record is then archived in the archiving run. This is how things happened before Release 4.6A.A: You can delete the condition records from the database. You then receive a popup, asking whether the condition record should actually be deleted or whether the deletion indicator should simply be set.B: You delete the condition records from the database. You only receive a popup if there are condition supplements available.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder pricingScaleBasisShort(@Nullable String pricingScaleBasisShort)
Original property name from the Odata EDM: PricingScaleBasisShort
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder pricingScaleCheckingRule(@Nullable String pricingScaleCheckingRule)
Original property name from the Odata EDM: PricingScaleCheckingRule
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder pricingScaleType(@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.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder pricingScaleRoutine(@Nullable String pricingScaleRoutine)
Original property name from the Odata EDM: PricingScaleRoutine
You can use this routine to specify calculation methods that are not provided in the standard system.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder pricingScaleUnit(@Nullable String pricingScaleUnit)
Original property name from the Odata EDM: PricingScaleUnit
The system proposes the unit of measure when you maintain records for group conditions that are either weight or volume dependent.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnCrcyCnvrsnIsAftMltpl(@Nullable Boolean prcgCndnCrcyCnvrsnIsAftMltpl)
Original property name from the Odata EDM: PrcgCndnCrcyCnvrsnIsAftMltpl
To calculate a condition value in a document, the system multiplies the amount that results from the condition record by the item quantity. This indicator controls whether the system carries out currency conversion before or after the multiplication takes place.If you mark the field, the system converts the condition value into the document currency after multiplication. If you leave the field blank, the system converts the condition value into the document currency before multiplication.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder isRelevantForAccrual(@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.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionIsForConfiguration(@Nullable Boolean conditionIsForConfiguration)
Original property name from the Odata EDM: ConditionIsForConfiguration
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder prcgCndnQtyCnvrsnIsActivated(@Nullable Boolean prcgCndnQtyCnvrsnIsActivated)
Original property name from the Odata EDM: PrcgCndnQtyCnvrsnIsActivated
The field is only relevant for calculation rule 'C' (quantity- dependent).It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.Rounding errors can occur during quantity conversion.Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder cndnIsRelevantForIntcoBilling(@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.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder conditionExclusion(@Nullable String conditionExclusion)
Original property name from the Odata EDM: ConditionExclusion
You can set this indicator in two ways:For a particular condition record (the field appears on the Details screen)For all records of a particular condition type (the field appears on the screen where you define the condition type)If you set the indicator to exclude conditions, there are several things to consider:The system will still take into account any condition supplements that are part of the condition record for the price (condition type PR00, for example)You can allow for exceptions where you want to include discounts in spite of the condition exclusion indicator (for a particular discount condition you can specify a requirement that applies the discount ONLY when the indicator is set)
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder cndnValueZeroProcgCode(@Nullable String cndnValueZeroProcgCode)
Original property name from the Odata EDM: CndnValueZeroProcgCode
If you leave this field blank, the following applies:Conditions are not considered in the condition exclusion logic when their value is equal to zero.Price conditions are deactivated during the price calculation if their amount and value are equal to zero.If you set the value of this indicator to "A" for this condition type, the following applies:Conditions of this type will be considered in the exclusion logic even if their value is equal to zeroIf this is a condition type with condition class "Price", conditions of this type will not be deactivated during the price calculationYou may set this indicator for all condition types except taxes.
this
.@Nonnull public PurgPricingConditionType.PurgPricingConditionTypeBuilder isRelevantForSalesPriceCalc(@Nullable Boolean isRelevantForSalesPriceCalc)
Original property name from the Odata EDM: IsRelevantForSalesPriceCalc
The indicator can be maintained during definition of condition types and is taken as a default value when condition records are generated. This default can be changed when the "Pricing relevance can be changed" indicator is set.In scales, the indicator is used to select the scale line used for price determination in Sales Price Calculation.The pricing relevance can only be changed if the Pricing relevance can be changed indicator has been set.
this
.@Nonnull public PurgPricingConditionType build()
Copyright © 2021 SAP SE. All rights reserved.