public static final class PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder extends Object
@Nonnull public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder purgQuotaArrangementItem(PurgQuotaArrangementItem... value)
value
- The PurgQuotaArrangementItems to build this PurchasingQuotaArrangement with.public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder quotaArrangement(@Nullable String quotaArrangement)
Original property name from the Odata EDM: QuotaArrangement
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder validityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder validityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
quota arrangement becomes valid.
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder minQtyForSpltQuota(@Nullable BigDecimal minQtyForSpltQuota)
Original property name from the Odata EDM: MinQtyForSpltQuota
If the lot is smaller than or equal to the minimum quantity, the system will proceed on the basis of the usual quota arrangement logic.Allocation by quota using splitting quotas is only carried out via a requirement planning run, subject to the following preconditions:Through the appropriate entry in the field Quota arrangement usage (on the MRP data screen 2 or Purchasing screen) it must have been specified that a quota arrangement is to be applied in the planning run.The indicator for the splitting quota must be set for the the lot-sizing procedure used for materials planning purposes in Customizing.
among several sources of supply in the planning run.public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder lastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder userDescription(@Nullable String userDescription)
Original property name from the Odata EDM: UserDescription
public PurchasingQuotaArrangement.PurchasingQuotaArrangementBuilder materialBaseUnit(@Nullable String materialBaseUnit)
Original property name from the Odata EDM: MaterialBaseUnit
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.public PurchasingQuotaArrangement build()
Copyright © 2019 SAP SE. All rights reserved.