public static final class SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder extends Object
@Nonnull public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder slsPrcgCndnRecdValidity(SlsPrcgCndnRecdValidity... value)
value - The SlsPrcgCndnRecdValiditys to build this SlsPrcgCndnRecdSuplmnt with.@Nonnull public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder slsPrcgCndnRecordScale(SlsPrcgCndnRecordScale... value)
value - The SlsPrcgCndnRecordScales to build this SlsPrcgCndnRecdSuplmnt with.@Nonnull public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder slsPrcgConditionRecord(SlsPrcgConditionRecord value)
value - The SlsPrcgConditionRecord to build this SlsPrcgCndnRecdSuplmnt with.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionRecord(@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).
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionSequentialNumber(@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.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionTable(@Nullable String conditionTable)
Original property name from the Odata EDM: ConditionTable
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionApplication(@Nullable String conditionApplication)
Original property name from the Odata EDM: ConditionApplication
example, sales & distribution or purchasing).this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionType(@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.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionValidityEndDate(@Nullable LocalDateTime conditionValidityEndDate)
Original property name from the Odata EDM: ConditionValidityEndDate
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionValidityStartDate(@Nullable LocalDateTime conditionValidityStartDate)
Original property name from the Odata EDM: ConditionValidityStartDate
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionTextID(@Nullable String conditionTextID)
Original property name from the Odata EDM: ConditionTextID
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder 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.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder pricingScaleBasis(@Nullable String pricingScaleBasis)
Original property name from the Odata EDM: PricingScaleBasis
on quantity, weight, or volume.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionScaleQuantity(@Nullable BigDecimal conditionScaleQuantity)
Original property name from the Odata EDM: ConditionScaleQuantity
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionScaleQuantityUnit(@Nullable String conditionScaleQuantityUnit)
Original property name from the Odata EDM: ConditionScaleQuantityUnit
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionScaleAmount(@Nullable BigDecimal conditionScaleAmount)
Original property name from the Odata EDM: ConditionScaleAmount
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionScaleAmountCurrency(@Nullable String conditionScaleAmountCurrency)
Original property name from the Odata EDM: ConditionScaleAmountCurrency
If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value. In the standard version of the SAP System, this field is only relevant in condition records for the following discounts:Price groupPrice group/Material pricing groupYou apply a price group discount to customers in a particular foreign country. When you create a condition record for this discount and enter values in the pricing scale, you can also enter the corresponding foreign currency. During pricing, the system then calculates discounts based on scale values in the foreign currency. The discount amount is then converted into the currency you are using in the sales document.After you enter a currency in this field and save the condition record, you cannot change the currency without deleting the record and creating it again.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder 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.G = FormulaIf you set this value, during the standard pricing for this condition type, the system does not determine a condition base value nor a condition amount or condition value. When the system has executed the standard logic to determine the condition base value and the condition value, the fields are filled with random values.Note: You can use formulas in a pricing procedure without setting calculation type G for the condition type.Follow-up activityFormulas are represented as routines. You must use routines to ensure that the condition base value and the condition value are determined. Therefore, in the pricing procedures that contain the affected condition type, you must assign a routine for the condition base value and a routine for the condition value to this condition type. If the condition base value is of no importance or if both, the condition base value and the condition value, are determined within the routine of the condition value, you do not have to use a routine for the condition base value.Note: If you use the calculation type G, you are responsible for the calculation of the values in the pricing result.
system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionRateValue(@Nullable BigDecimal conditionRateValue)
Original property name from the Odata EDM: ConditionRateValue
The following examples illustrate how you can use the rate in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you are creating a condition based on percentage discounts or surcharges (for example, a customer-specific discount), you enter the value of a percentage. If the condition is a discount, the system automatically enters a minus sign behind the amount and a percent sign in the Rate unit field.
condition type, the rate can be a fixed amount or a percentage. If the condition includes a pricing scale, the rate displays the first line of the scale.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionRateValueUnit(@Nullable String conditionRateValueUnit)
Original property name from the Odata EDM: ConditionRateValueUnit
The following examples illustrate what you can do when using different condition types.If you create a condition that includes prices (for example, prices for a material), you enter the currency that applies to the condition (for example, "USD" for US dollars)If you are creating a condition based on percentage discounts or surcharges (for example, a customer-specific discount), you cannot enter a value in the Condition unit field. Instead, the system automatically enters a percent sign as the condition unit when you enter a value in the Condition Amount field.
a particular currency. The use of the condition unit depends on the condition type (for example, whether the condition is a material price or a customer discount).this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionQuantity(@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.
example, bottles).this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionQuantityUnit(@Nullable String conditionQuantityUnit)
Original property name from the Odata EDM: ConditionQuantityUnit
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionToBaseQtyNmrtr(@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.
measure.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionToBaseQtyDnmntr(@Nullable BigDecimal conditionToBaseQtyDnmntr)
Original property name from the Odata EDM: ConditionToBaseQtyDnmntr
Many material processing functions, such as the creation of production requirements, may require that sales units are converted into base units of measure.You produce a soft-drink in gallons, but sell it in 1 pint bottles. The conversion factor looks like this:8 Pt <=> 1 GThe first number (the denominator) represents the sales units, in this case, pints. The second number (the numerator) represents the equivalent quantity of base units of measure, in this case, gallons.
of measure.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder baseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: BaseUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
enter in other units of measure (alternative units of measure) to the base unit of measure.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionLowerLimit(@Nullable BigDecimal conditionLowerLimit)
Original property name from the Odata EDM: ConditionLowerLimit
When you maintain the scales in a condition record, the system checks whether the scale value falls below the lower limit.
lower limit allowed for the corresponding condition record.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionUpperLimit(@Nullable BigDecimal conditionUpperLimit)
Original property name from the Odata EDM: ConditionUpperLimit
When you maintain a condition record, the system checks automatically whether the scale value exceeds the upper limit.
for the corresponding condition record and/or the condition type.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionAlternativeCurrency(@Nullable String conditionAlternativeCurrency)
Original property name from the Odata EDM: ConditionAlternativeCurrency
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder 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.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionIsDeleted(@Nullable Boolean conditionIsDeleted)
Original property name from the Odata EDM: ConditionIsDeleted
is deleted during the next reorganization run.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder additionalValueDays(@Nullable String additionalValueDays)
Original property name from the Odata EDM: AdditionalValueDays
If you enter a value in this field, you cannot enter a date in the fixed value date field.
document become effective.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder fixedValueDate(@Nullable LocalDateTime fixedValueDate)
Original property name from the Odata EDM: FixedValueDate
If you enter a date in this field, you cannot enter a value in the additional value days field.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder paymentTerms(@Nullable String paymentTerms)
Original property name from the Odata EDM: PaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder cndnMaxNumberOfSalesOrders(@Nullable String cndnMaxNumberOfSalesOrders)
Original property name from the Odata EDM: CndnMaxNumberOfSalesOrders
You introduce a new product for which you offer an introductory discount. The customer gets this discount only on the first two orders - the initial order and the first replenishment order. Thereafter, the discount is inactive. In this case, you enter '2' in this field.To see how many orders have already benefitted from a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record.
record.this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder minimumConditionBasisValue(@Nullable BigDecimal minimumConditionBasisValue)
Original property name from the Odata EDM: MinimumConditionBasisValue
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder maximumConditionBasisValue(@Nullable BigDecimal maximumConditionBasisValue)
Original property name from the Odata EDM: MaximumConditionBasisValue
You use this field to specify a maximum cumulative quantity, weight, or volume for a condition record.You offer a customer a special discount on a certain product but want to limit this discount to a specified total number of cases. You enter the maximum number of cases in this field. As you process orders that use this condition record, the system updates the cumulative quantity. When the maximum quantity is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative condition base value for a particular condition record, you select Extras -> Cumulative values in the overview screen of the condition record.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder maximumConditionAmount(@Nullable BigDecimal maximumConditionAmount)
Original property name from the Odata EDM: MaximumConditionAmount
You use this field to limit the use of a particular condition record to a specified total value.You offer a customer a special discount on a certain product but want to limit this discount to a specified total amount. You enter the maximum amount (for example, 1000 USD) in this field. As you process orders that use this condition record, the system updates the cumulative value. When the maximum value is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative value for a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder incrementalScale(@Nullable String incrementalScale)
Original property name from the Odata EDM: IncrementalScale
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder pricingScaleLine(@Nullable String pricingScaleLine)
Original property name from the Odata EDM: PricingScaleLine
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder conditionReleaseStatus(@Nullable String conditionReleaseStatus)
Original property name from the Odata EDM: ConditionReleaseStatus
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status for conditions.
this.public SlsPrcgCndnRecdSuplmnt.SlsPrcgCndnRecdSuplmntBuilder eTag(@Nullable String eTag)
Original property name from the Odata EDM: ETag
this.public SlsPrcgCndnRecdSuplmnt build()
Copyright © 2020 SAP SE. All rights reserved.