public static final class ProductSalesDelivery.ProductSalesDeliveryBuilder extends Object
@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder salesTax(ProductSalesTax... value)
value
- The ProductSalesTaxs to build this ProductSalesDelivery with.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder salesText(ProductSalesText... value)
value
- The ProductSalesTexts to build this ProductSalesDelivery with.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder product(@Nullable String product)
Original property name from the Odata EDM: Product
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productSalesOrg(@Nullable String productSalesOrg)
Original property name from the Odata EDM: ProductSalesOrg
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
sales organization may include legal liability for products and customer claims.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productDistributionChnl(@Nullable String productDistributionChnl)
Original property name from the Odata EDM: ProductDistributionChnl
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
wholesale, retail, or direct sales.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder minimumOrderQuantity(@Nullable BigDecimal minimumOrderQuantity)
Original property name from the Odata EDM: MinimumOrderQuantity
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder supplyingPlant(@Nullable String supplyingPlant)
Original property name from the Odata EDM: SupplyingPlant
This plant is automatically copied into the sales order item as the default value.If there is no default value when you process the sales order item, enter a delivering plant.The value proposed in the item is eitherfrom the customer master record of the goods recipient, orfrom the material master recordThe system checks whether it can propose a value (and for your own plants, whether the material has been created in the plant). If the system can propose a value, the plant is copied to the sales order item where you can change it as required.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder priceSpecificationProductGroup(@Nullable String priceSpecificationProductGroup)
Original property name from the Odata EDM: PriceSpecificationProductGroup
You can create condition records for a product price group using the following condition types:Product price group (for example, all non-food products)A combination of customer and product price groupA combination of customer price group and product price group (for example, all wholesale customers and all non-food products)
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder accountDetnProductGroup(@Nullable String accountDetnProductGroup)
Original property name from the Odata EDM: AccountDetnProductGroup
Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder deliveryNoteProcMinDelivQty(@Nullable BigDecimal deliveryNoteProcMinDelivQty)
Original property name from the Odata EDM: DeliveryNoteProcMinDelivQty
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder itemCategoryGroup(@Nullable String itemCategoryGroup)
Original property name from the Odata EDM: ItemCategoryGroup
Depending on the item category group that you apply and the sales document type you are processing, the system automatically proposes an item category in the document.In the standard system, for example, there are standard items, items that represent services (and do not require delivery processing), and items that represent packaging materials.
processing of sales documents.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder deliveryQuantityUnit(@Nullable String deliveryQuantityUnit)
Original property name from the Odata EDM: DeliveryQuantityUnit
The delivery unit consists of a number and a unit of measure. In the case of a delivery unit of 30 pieces, 30, 60, 90, and so on pieces can be delivered, but not, however, 100 pieces.Enter a value in this field only if you want to use a unit of measure differing from the base unit of measure.If the field does not contain an entry, the system will assume that the unit of measure is the base unit of measure.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder deliveryQuantity(@Nullable BigDecimal deliveryQuantity)
Original property name from the Odata EDM: DeliveryQuantity
The delivery unit consists of a number and a unit of measure. In the case of a delivery unit of 30 pieces, 30, 60, 90, and so on pieces can be delivered, but not, however, 100 pieces.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productSalesStatus(@Nullable String productSalesStatus)
Original property name from the Odata EDM: ProductSalesStatus
The distribution-chain-specific material status restricts the usability of the material for the distribution chain concerned, that is, it defines whether a warning or error message is displayed if you include the material in a particular function.The material may be a part under development or one to be discontinued.
Sales.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productSalesStatusValidityDate(@Nullable LocalDateTime productSalesStatusValidityDate)
Original property name from the Odata EDM: ProductSalesStatusValidityDate
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder salesMeasureUnit(@Nullable String salesMeasureUnit)
Original property name from the Odata EDM: SalesMeasureUnit
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder isMarkedForDeletion(@Nullable Boolean isMarkedForDeletion)
Original property name from the Odata EDM: IsMarkedForDeletion
distribution chain level, and deletes the data at this level.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHierarchy(@Nullable String productHierarchy)
Original property name from the Odata EDM: ProductHierarchy
In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.Level Number of characters allowed1 52 53 8You define a product hierarchy with the following levels:Level Example Description1 00005 Electrical goods2 00003 Wet appliances3 00000001 Washing machineIn this case, a washing machine belongs to the product hierarchy 000050000300000001.
is used for analyses and price determination.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder firstSalesSpecProductGroup(@Nullable String firstSalesSpecProductGroup)
Original property name from the Odata EDM: FirstSalesSpecProductGroup
used in the standard SAP System, you can use them as required, for example, for analyses.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder secondSalesSpecProductGroup(@Nullable String secondSalesSpecProductGroup)
Original property name from the Odata EDM: SecondSalesSpecProductGroup
used in the standard SAP System, you can use them as required, for example, for analyses.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder thirdSalesSpecProductGroup(@Nullable String thirdSalesSpecProductGroup)
Original property name from the Odata EDM: ThirdSalesSpecProductGroup
used in the standard SAP System, you can use them as required, for example, for analyses.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder fourthSalesSpecProductGroup(@Nullable String fourthSalesSpecProductGroup)
Original property name from the Odata EDM: FourthSalesSpecProductGroup
used in the standard SAP System, you can use them as required, for example, for analyses.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder fifthSalesSpecProductGroup(@Nullable String fifthSalesSpecProductGroup)
Original property name from the Odata EDM: FifthSalesSpecProductGroup
used in the standard SAP System, you can use them as required, for example, for analyses.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder minimumMakeToOrderOrderQty(@Nullable BigDecimal minimumMakeToOrderOrderQty)
Original property name from the Odata EDM: MinimumMakeToOrderOrderQty
If the order quantity exceeds an exact multiple of the minimum make-to-order quantity, the system indicates the unplanned additional requirements when it processes the order.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder 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
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder logisticsStatisticsGroup(@Nullable String logisticsStatisticsGroup)
Original property name from the Odata EDM: LogisticsStatisticsGroup
You can assign statistics groups to each of the following:Item categorySales document typeCustomerMaterialWhen you generate statistics in the logistics information system, the system uses the combination of specified statistics groups to determine the appropriate update sequence. The update sequence in turn determines for exactly which fields the statistics are generated.
information system.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder volumeRebateGroup(@Nullable String volumeRebateGroup)
Original property name from the Odata EDM: VolumeRebateGroup
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productCommissionGroup(@Nullable String productCommissionGroup)
Original property name from the Odata EDM: ProductCommissionGroup
You can assign two materials to the same commission group as long as each representative who sells these materials receives the same commission percentage for both materials. In other words, the commission percentages within a commission group are always the same for any one representative but may vary for different representatives.Material Rep. 1 Rep. 2 Rep. 3A 5 % 10 % 11 %B 5 % 10 % 11 %Materials A and B are sold by these three representatives only. You can therefore assign them to the same commission group.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder cashDiscountIsDeductible(@Nullable Boolean cashDiscountIsDeductible)
Original property name from the Odata EDM: CashDiscountIsDeductible
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder pricingReferenceProduct(@Nullable String pricingReferenceProduct)
Original property name from the Odata EDM: PricingReferenceProduct
The conditions that apply to the pricing reference material also apply to the material in whose material master record the pricing reference material is stored.A pricing reference material must always have its own material master record.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder roundingProfile(@Nullable String roundingProfile)
Original property name from the Odata EDM: RoundingProfile
In Customizing, enter a threshold value from which the system should round up to the next value per deliverable unit:If the requirements value exceeds the first threshold value, the system always rounds up to the next multiple of the level foundIf the requirements value falls below the first threshold value, the system copies the original requirements value.Two other types of rounding exist:Dynamic rounding profile:These profiles are used to round up quantities to logistical units of measure (for example, layers). The contents of a logistical unit of measure does not have to be know when creating the rounding profile. It is determined by the master data from the material master.Rounding profile with quantity to be added/subtractedWith these profiles, the given quantity is changed either by adding a percentage or subtracting a percentage.Only static rounding profiles are taken into account in requirements planning. Neither dynamic rounding profiles not quantity addition/ subtraction are taken into account.A material's base unit of measure is 1 unit; the purchase order is to be delivered in layers (1 layer corresponds to 5 units) or in pallets (1 pallet corresponds to 8 layers which contains 40 units).You maintain the profile as follows:From a requirements of 2 units, the system is to round up to 5; from a requirement of 32 units, the system is to round up to 40.This results in the following order proposal quantities:Requirement from 1 -> 1 requirement from 31 -> 30Requirement from 2 -> 5 requirement from 32 -> 40Requirement from 6 -> 10 requirement from 74 -> 80Requirement from 7 -> 10If no rounding profile has been entered, the system uses the rounding value entered in the material master record for the planning run.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productUnitGroup(@Nullable String productUnitGroup)
Original property name from the Odata EDM: ProductUnitGroup
You can use the unit of measure group, for example, to define allowed units of measure for a particular material for a vendor or a receiver. This is of significance for when rounding with the dynamic rounding profile if 'check vendor' or 'check customer' is selected in the rounding profiles. In this case, only those units of measure are included in rounding that are defined in the unit of measure group.
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder variableSalesUnitIsNotAllowed(@Nullable Boolean variableSalesUnitIsNotAllowed)
Original property name from the Odata EDM: VariableSalesUnitIsNotAllowed
unit is proposed in Sales and Distribution (SD) documents such as sales orders. If a variable sales unit is not allowed, the unit specified in documents may not differ from that in the master record.this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID01(@Nullable Boolean productHasAttributeID01)
Original property name from the Odata EDM: ProductHasAttributeID01
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID02(@Nullable Boolean productHasAttributeID02)
Original property name from the Odata EDM: ProductHasAttributeID02
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID03(@Nullable Boolean productHasAttributeID03)
Original property name from the Odata EDM: ProductHasAttributeID03
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID04(@Nullable Boolean productHasAttributeID04)
Original property name from the Odata EDM: ProductHasAttributeID04
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID05(@Nullable Boolean productHasAttributeID05)
Original property name from the Odata EDM: ProductHasAttributeID05
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID06(@Nullable Boolean productHasAttributeID06)
Original property name from the Odata EDM: ProductHasAttributeID06
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID07(@Nullable Boolean productHasAttributeID07)
Original property name from the Odata EDM: ProductHasAttributeID07
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID08(@Nullable Boolean productHasAttributeID08)
Original property name from the Odata EDM: ProductHasAttributeID08
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID09(@Nullable Boolean productHasAttributeID09)
Original property name from the Odata EDM: ProductHasAttributeID09
this
.@Nonnull public ProductSalesDelivery.ProductSalesDeliveryBuilder productHasAttributeID10(@Nullable Boolean productHasAttributeID10)
Original property name from the Odata EDM: ProductHasAttributeID10
this
.@Nonnull public ProductSalesDelivery build()
Copyright © 2020 SAP SE. All rights reserved.