PurgQuotaArrangementItem (SAP S/4HANA Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject<EntityT>
- - com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmEntity<PurgQuotaArrangementItem>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.purchasingquotaarrangement.PurgQuotaArrangementItem

public class PurgQuotaArrangementItem
extends VdmEntity<PurgQuotaArrangementItem>

API for Quota Arrangement Item

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class PurgQuotaArrangementItem.PurgQuotaArrangementItemBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`PurgQuotaArrangementItem.PurgQuotaArrangementItemBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static PurgQuotaArrangementItemSelectable`	`ALL_FIELDS` Selector for all available fields of PurgQuotaArrangementItem.
`static PurgQuotaArrangementItemField<String>`	`MANUFACTURER_MATERIAL` Use with available fluent helpers to apply the ManufacturerMaterial field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`MATERIAL_MAX_LOT_SIZE_QUANTITY` Use with available fluent helpers to apply the MaterialMaxLotSizeQuantity field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`MATERIAL_MIN_LOT_SIZE_QUANTITY` Use with available fluent helpers to apply the MaterialMinLotSizeQuantity field to query operations.
`static PurgQuotaArrangementItemField<String>`	`MATERIAL_PROCUREMENT_CATEGORY` Use with available fluent helpers to apply the MaterialProcurementCategory field to query operations.
`static PurgQuotaArrangementItemField<String>`	`MATERIAL_PROCUREMENT_TYPE` Use with available fluent helpers to apply the MaterialProcurementType field to query operations.
`static PurgQuotaArrangementItemField<String>`	`MATERIAL_ROUNDING_PROFILE` Use with available fluent helpers to apply the MaterialRoundingProfile field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`MAXIMUM_RELEASE_QUANTITY` Use with available fluent helpers to apply the MaximumReleaseQuantity field to query operations.
`static PurgQuotaArrangementItemField<String>`	`NUMBER_OF_PERIODS_PER_REL_QUANTITY` Use with available fluent helpers to apply the NumberOfPeriodsPerRelQuantity field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`PLANNED_DELIVERY_DURATION_IN_DAYS` Use with available fluent helpers to apply the PlannedDeliveryDurationInDays field to query operations.
`static PurgQuotaArrangementItemField<String>`	`PRODUCTION_VERSION` Use with available fluent helpers to apply the ProductionVersion field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`PURCHASING_SOURCE_QUOTA` Use with available fluent helpers to apply the PurchasingSourceQuota field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`QUOTA_ALLOCATED_QUANTITY` Use with available fluent helpers to apply the QuotaAllocatedQuantity field to query operations.
`static PurgQuotaArrangementItemField<String>`	`QUOTA_ARRANGEMENT` Use with available fluent helpers to apply the QuotaArrangement field to query operations.
`static PurgQuotaArrangementItemField<String>`	`QUOTA_ARRANGEMENT_ITEM` Use with available fluent helpers to apply the QuotaArrangementItem field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`QUOTA_BASE_QUANTITY` Use with available fluent helpers to apply the QuotaBaseQuantity field to query operations.
`static PurgQuotaArrangementItemField<String>`	`QUOTA_DETERMINATION_PRIORITY` Use with available fluent helpers to apply the QuotaDeterminationPriority field to query operations.
`static PurgQuotaArrangementItemField<BigDecimal>`	`QUOTA_MAXIMUM_QUANTITY` Use with available fluent helpers to apply the QuotaMaximumQuantity field to query operations.
`static PurgQuotaArrangementItemField<String>`	`QUOTA_RELEASE_PERIOD_TYPE` Use with available fluent helpers to apply the QuotaReleasePeriodType field to query operations.
`static PurgQuotaArrangementItemField<Boolean>`	`SOURCE_OF_SUPPLY_IS_ASSIGNED_ONCE` Use with available fluent helpers to apply the SourceOfSupplyIsAssignedOnce field to query operations.
`static PurgQuotaArrangementItemField<String>`	`SUPPLIER` Use with available fluent helpers to apply the Supplier field to query operations.
`static PurgQuotaArrangementItemField<String>`	`SUPPLYING_PLANT` Use with available fluent helpers to apply the SupplyingPlant field to query operations.
`static PurgQuotaArrangementItemLink<PurchasingQuotaArrangement>`	`TO_PURCHASING_QUOTA_ARRANGEMENT` Use with available fluent helpers to apply the to_PurchasingQuotaArrangement navigation property to query operations.

Constructor Summary

Constructors
Constructor and Description
`PurgQuotaArrangementItem()`
PurgQuotaArrangementItem(String quotaArrangement, String quotaArrangementItem, String materialProcurementCategory, String materialProcurementType, String supplier, String supplyingPlant, BigDecimal purchasingSourceQuota, BigDecimal quotaBaseQuantity, BigDecimal quotaAllocatedQuantity, BigDecimal quotaMaximumQuantity, String productionVersion, BigDecimal materialMaxLotSizeQuantity, BigDecimal materialMinLotSizeQuantity, String materialRoundingProfile, Boolean sourceOfSupplyIsAssignedOnce, BigDecimal maximumReleaseQuantity, String quotaReleasePeriodType, String numberOfPeriodsPerRelQuantity, String quotaDeterminationPriority, String manufacturerMaterial, BigDecimal plannedDeliveryDurationInDays, ErpConfigContext erpConfigContext, PurchasingQuotaArrangement toPurchasingQuotaArrangement)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`static PurgQuotaArrangementItem.PurgQuotaArrangementItemBuilder`	`builder()`
`boolean`	`equals(Object o)`
`PurchasingQuotaArrangement`	`fetchPurchasingQuotaArrangement()` Fetches the PurchasingQuotaArrangement entity (one to one) associated with this entity.
`static <T> PurgQuotaArrangementItemField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`String`	`getManufacturerMaterial()` Constraints: Not nullable, Maximum length: 40
`BigDecimal`	`getMaterialMaxLotSizeQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3 If the shortage (undercoverage) quantity exceeds the maximum lot size, the quota system is re-applied to the remaining quantity.
`BigDecimal`	`getMaterialMinLotSizeQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3 If the shortage (undercoverage) quantity is less than the minimum lot size, the latter quantity will be allocated to the source instead of the former.
`String`	`getMaterialProcurementCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getMaterialProcurementType()` Constraints: Not nullable, Maximum length: 1 A material which is procured externally can be acquired via a delivery schedule or a consignment order
`String`	`getMaterialRoundingProfile()` Constraints: Not nullable, Maximum length: 4 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 found If the requirements value falls below the first threshold value, the system copies the original requirements value.
`BigDecimal`	`getMaximumReleaseQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3 If a source with a maximum release quantity is next in line in a quota arrangement, in total no more than this maximum figure can be allocated to it within the specified period.
`String`	`getNumberOfPeriodsPerRelQuantity()` Constraints: Not nullable, Maximum length: 2
`BigDecimal`	`getPlannedDeliveryDurationInDays()` Constraints: Not nullable, Precision: 3, Scale: 0 If you have different vendors for a material, you must specify an average value.
`String`	`getProductionVersion()` Constraints: Not nullable, Maximum length: 4 The production version determines the following: the BOM alternative for a BOM explosion the task list type, the task list group and the task list group counter for allocation to task lists lot-size restrictions for repetitive manufacturing
`PurchasingQuotaArrangement`	`getPurchasingQuotaArrangementOrFetch()` Retrieval of associated PurchasingQuotaArrangement entity (one to one).
`com.google.common.base.Optional<PurchasingQuotaArrangement>`	`getPurchasingQuotaArrangementOrNull()` Retrieval of associated PurchasingQuotaArrangement entity (one to one).
`BigDecimal`	`getPurchasingSourceQuota()` Constraints: Not nullable, Precision: 3, Scale: 0 If a certain material is to be procured alternately from different suppliers, you can create aquota arrangement item for each supplier and assign a quota to each such item.
`BigDecimal`	`getQuotaAllocatedQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3 This value is updated in planned orders, purchase requisitions, purchase orders, and scheduling agreement delivery schedule lines.
`String`	`getQuotaArrangement()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getQuotaArrangementItem()` (Key Field) Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getQuotaBaseQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3 Using the quota base quantity, you can regulate the quota arrangement without having to change the quota if, for example, a new source is to be included in the arrangement.
`String`	`getQuotaDeterminationPriority()` Constraints: Not nullable, Maximum length: 2 Example without splitting quota: If, for example, you enter priority one along with a maximum release quantity, then this source of supply is always selected until its maximum release quantity has been exhausted.
`BigDecimal`	`getQuotaMaximumQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3
`String`	`getQuotaReleasePeriodType()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getSourceOfSupplyIsAssignedOnce()` Constraints: noneIf a maximum lot size is specified for a source of supply, and if this source has a much lower quota rating than other sources, the following happens: the lot is split up into several order proposals (each of which amounts to the maximum lot size) which are all assigned to the the source in question.
`String`	`getSupplier()` Constraints: Not nullable, Maximum length: 10 With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).
`String`	`getSupplyingPlant()` Constraints: Not nullable, Maximum length: 4 You can only enter one supplier number or one plant per quota arrangement item.
`Class<PurgQuotaArrangementItem>`	`getType()`
`int`	`hashCode()`
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`void`	`setManufacturerMaterial(String manufacturerMaterial)` Constraints: Not nullable, Maximum length: 40
`void`	`setMaterialMaxLotSizeQuantity(BigDecimal materialMaxLotSizeQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3 If the shortage (undercoverage) quantity exceeds the maximum lot size, the quota system is re-applied to the remaining quantity.
`void`	`setMaterialMinLotSizeQuantity(BigDecimal materialMinLotSizeQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3 If the shortage (undercoverage) quantity is less than the minimum lot size, the latter quantity will be allocated to the source instead of the former.
`void`	`setMaterialProcurementCategory(String materialProcurementCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setMaterialProcurementType(String materialProcurementType)` Constraints: Not nullable, Maximum length: 1 A material which is procured externally can be acquired via a delivery schedule or a consignment order
`void`	`setMaterialRoundingProfile(String materialRoundingProfile)` Constraints: Not nullable, Maximum length: 4 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 found If the requirements value falls below the first threshold value, the system copies the original requirements value.
`void`	`setMaximumReleaseQuantity(BigDecimal maximumReleaseQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3 If a source with a maximum release quantity is next in line in a quota arrangement, in total no more than this maximum figure can be allocated to it within the specified period.
`void`	`setNumberOfPeriodsPerRelQuantity(String numberOfPeriodsPerRelQuantity)` Constraints: Not nullable, Maximum length: 2
`void`	`setPlannedDeliveryDurationInDays(BigDecimal plannedDeliveryDurationInDays)` Constraints: Not nullable, Precision: 3, Scale: 0 If you have different vendors for a material, you must specify an average value.
`void`	`setProductionVersion(String productionVersion)` Constraints: Not nullable, Maximum length: 4 The production version determines the following: the BOM alternative for a BOM explosion the task list type, the task list group and the task list group counter for allocation to task lists lot-size restrictions for repetitive manufacturing
`void`	`setPurchasingQuotaArrangement(PurchasingQuotaArrangement value)` Overwrites the associated PurchasingQuotaArrangement entity for the loaded navigation property to_PurchasingQuotaArrangement.
`void`	`setPurchasingSourceQuota(BigDecimal purchasingSourceQuota)` Constraints: Not nullable, Precision: 3, Scale: 0 If a certain material is to be procured alternately from different suppliers, you can create aquota arrangement item for each supplier and assign a quota to each such item.
`void`	`setQuotaAllocatedQuantity(BigDecimal quotaAllocatedQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3 This value is updated in planned orders, purchase requisitions, purchase orders, and scheduling agreement delivery schedule lines.
`void`	`setQuotaArrangement(String quotaArrangement)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setQuotaArrangementItem(String quotaArrangementItem)` (Key Field) Constraints: Not nullable, Maximum length: 3
`void`	`setQuotaBaseQuantity(BigDecimal quotaBaseQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3 Using the quota base quantity, you can regulate the quota arrangement without having to change the quota if, for example, a new source is to be included in the arrangement.
`void`	`setQuotaDeterminationPriority(String quotaDeterminationPriority)` Constraints: Not nullable, Maximum length: 2 Example without splitting quota: If, for example, you enter priority one along with a maximum release quantity, then this source of supply is always selected until its maximum release quantity has been exhausted.
`void`	`setQuotaMaximumQuantity(BigDecimal quotaMaximumQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3
`void`	`setQuotaReleasePeriodType(String quotaReleasePeriodType)` Constraints: Not nullable, Maximum length: 1
`void`	`setSourceOfSupplyIsAssignedOnce(Boolean sourceOfSupplyIsAssignedOnce)` Constraints: noneIf a maximum lot size is specified for a source of supply, and if this source has a much lower quota rating than other sources, the following happens: the lot is split up into several order proposals (each of which amounts to the maximum lot size) which are all assigned to the the source in question.
`void`	`setSupplier(String supplier)` Constraints: Not nullable, Maximum length: 10 With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).
`void`	`setSupplyingPlant(String supplyingPlant)` Constraints: Not nullable, Maximum length: 4 You can only enter one supplier number or one plant per quota arrangement item.
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmEntity
getVersionIdentifier, setVersionIdentifier

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField

Methods inherited from class java.lang.Object
getClass, notify, notifyAll, wait, wait, wait

- Field Detail
  - ALL_FIELDS
```
public static final PurgQuotaArrangementItemSelectable ALL_FIELDS
```
    Selector for all available fields of PurgQuotaArrangementItem.
  - QUOTA_ARRANGEMENT
```
public static final PurgQuotaArrangementItemField<String> QUOTA_ARRANGEMENT
```
    Use with available fluent helpers to apply the QuotaArrangement field to query operations.
  - QUOTA_ARRANGEMENT_ITEM
```
public static final PurgQuotaArrangementItemField<String> QUOTA_ARRANGEMENT_ITEM
```
    Use with available fluent helpers to apply the QuotaArrangementItem field to query operations.
  - MATERIAL_PROCUREMENT_CATEGORY
```
public static final PurgQuotaArrangementItemField<String> MATERIAL_PROCUREMENT_CATEGORY
```
    Use with available fluent helpers to apply the MaterialProcurementCategory field to query operations.
  - MATERIAL_PROCUREMENT_TYPE
```
public static final PurgQuotaArrangementItemField<String> MATERIAL_PROCUREMENT_TYPE
```
    Use with available fluent helpers to apply the MaterialProcurementType field to query operations.
  - SUPPLIER
```
public static final PurgQuotaArrangementItemField<String> SUPPLIER
```
    Use with available fluent helpers to apply the Supplier field to query operations.
  - SUPPLYING_PLANT
```
public static final PurgQuotaArrangementItemField<String> SUPPLYING_PLANT
```
    Use with available fluent helpers to apply the SupplyingPlant field to query operations.
  - PURCHASING_SOURCE_QUOTA
```
public static final PurgQuotaArrangementItemField<BigDecimal> PURCHASING_SOURCE_QUOTA
```
    Use with available fluent helpers to apply the PurchasingSourceQuota field to query operations.
  - QUOTA_BASE_QUANTITY
```
public static final PurgQuotaArrangementItemField<BigDecimal> QUOTA_BASE_QUANTITY
```
    Use with available fluent helpers to apply the QuotaBaseQuantity field to query operations.
  - QUOTA_ALLOCATED_QUANTITY
```
public static final PurgQuotaArrangementItemField<BigDecimal> QUOTA_ALLOCATED_QUANTITY
```
    Use with available fluent helpers to apply the QuotaAllocatedQuantity field to query operations.
  - QUOTA_MAXIMUM_QUANTITY
```
public static final PurgQuotaArrangementItemField<BigDecimal> QUOTA_MAXIMUM_QUANTITY
```
    Use with available fluent helpers to apply the QuotaMaximumQuantity field to query operations.
  - PRODUCTION_VERSION
```
public static final PurgQuotaArrangementItemField<String> PRODUCTION_VERSION
```
    Use with available fluent helpers to apply the ProductionVersion field to query operations.
  - MATERIAL_MAX_LOT_SIZE_QUANTITY
```
public static final PurgQuotaArrangementItemField<BigDecimal> MATERIAL_MAX_LOT_SIZE_QUANTITY
```
    Use with available fluent helpers to apply the MaterialMaxLotSizeQuantity field to query operations.
  - MATERIAL_MIN_LOT_SIZE_QUANTITY
```
public static final PurgQuotaArrangementItemField<BigDecimal> MATERIAL_MIN_LOT_SIZE_QUANTITY
```
    Use with available fluent helpers to apply the MaterialMinLotSizeQuantity field to query operations.
  - MATERIAL_ROUNDING_PROFILE
```
public static final PurgQuotaArrangementItemField<String> MATERIAL_ROUNDING_PROFILE
```
    Use with available fluent helpers to apply the MaterialRoundingProfile field to query operations.
  - SOURCE_OF_SUPPLY_IS_ASSIGNED_ONCE
```
public static final PurgQuotaArrangementItemField<Boolean> SOURCE_OF_SUPPLY_IS_ASSIGNED_ONCE
```
    Use with available fluent helpers to apply the SourceOfSupplyIsAssignedOnce field to query operations.
  - MAXIMUM_RELEASE_QUANTITY
```
public static final PurgQuotaArrangementItemField<BigDecimal> MAXIMUM_RELEASE_QUANTITY
```
    Use with available fluent helpers to apply the MaximumReleaseQuantity field to query operations.
  - QUOTA_RELEASE_PERIOD_TYPE
```
public static final PurgQuotaArrangementItemField<String> QUOTA_RELEASE_PERIOD_TYPE
```
    Use with available fluent helpers to apply the QuotaReleasePeriodType field to query operations.
  - NUMBER_OF_PERIODS_PER_REL_QUANTITY
```
public static final PurgQuotaArrangementItemField<String> NUMBER_OF_PERIODS_PER_REL_QUANTITY
```
    Use with available fluent helpers to apply the NumberOfPeriodsPerRelQuantity field to query operations.
  - QUOTA_DETERMINATION_PRIORITY
```
public static final PurgQuotaArrangementItemField<String> QUOTA_DETERMINATION_PRIORITY
```
    Use with available fluent helpers to apply the QuotaDeterminationPriority field to query operations.
  - MANUFACTURER_MATERIAL
```
public static final PurgQuotaArrangementItemField<String> MANUFACTURER_MATERIAL
```
    Use with available fluent helpers to apply the ManufacturerMaterial field to query operations.
  - PLANNED_DELIVERY_DURATION_IN_DAYS
```
public static final PurgQuotaArrangementItemField<BigDecimal> PLANNED_DELIVERY_DURATION_IN_DAYS
```
    Use with available fluent helpers to apply the PlannedDeliveryDurationInDays field to query operations.
  - TO_PURCHASING_QUOTA_ARRANGEMENT
```
public static final PurgQuotaArrangementItemLink<PurchasingQuotaArrangement> TO_PURCHASING_QUOTA_ARRANGEMENT
```
    Use with available fluent helpers to apply the to_PurchasingQuotaArrangement navigation property to query operations.
- Constructor Detail
  - PurgQuotaArrangementItem
```
public PurgQuotaArrangementItem()
```
  - PurgQuotaArrangementItem
```
public PurgQuotaArrangementItem(@Nullable
                                String quotaArrangement,
                                @Nullable
                                String quotaArrangementItem,
                                @Nullable
                                String materialProcurementCategory,
                                @Nullable
                                String materialProcurementType,
                                @Nullable
                                String supplier,
                                @Nullable
                                String supplyingPlant,
                                @Nullable
                                BigDecimal purchasingSourceQuota,
                                @Nullable
                                BigDecimal quotaBaseQuantity,
                                @Nullable
                                BigDecimal quotaAllocatedQuantity,
                                @Nullable
                                BigDecimal quotaMaximumQuantity,
                                @Nullable
                                String productionVersion,
                                @Nullable
                                BigDecimal materialMaxLotSizeQuantity,
                                @Nullable
                                BigDecimal materialMinLotSizeQuantity,
                                @Nullable
                                String materialRoundingProfile,
                                @Nullable
                                Boolean sourceOfSupplyIsAssignedOnce,
                                @Nullable
                                BigDecimal maximumReleaseQuantity,
                                @Nullable
                                String quotaReleasePeriodType,
                                @Nullable
                                String numberOfPeriodsPerRelQuantity,
                                @Nullable
                                String quotaDeterminationPriority,
                                @Nullable
                                String manufacturerMaterial,
                                @Nullable
                                BigDecimal plannedDeliveryDurationInDays,
                                @Nullable
                                ErpConfigContext erpConfigContext,
                                @Nullable
                                PurchasingQuotaArrangement toPurchasingQuotaArrangement)
```
- Method Detail
  - getType
```
public Class<PurgQuotaArrangementItem> getType()
```
    Specified by:
    
    getType in class VdmObject<PurgQuotaArrangementItem>
    
    Returns:
    
    The class of this object.
  - field
```
public static <T> PurgQuotaArrangementItemField<T> field(String fieldName,
                                                         Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Parameters:
    
    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.
    
    Returns:
    
    A representation of an extension field from this entity.
  - fetchPurchasingQuotaArrangement
```
public PurchasingQuotaArrangement fetchPurchasingQuotaArrangement()
                                                           throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the PurchasingQuotaArrangement entity (one to one) associated with this entity. This corresponds to the OData navigation property to_PurchasingQuotaArrangement.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated PurchasingQuotaArrangement entity, or null if an entity is not associated.
    
    Throws:
    
    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.
  - getPurchasingQuotaArrangementOrFetch
```
public PurchasingQuotaArrangement getPurchasingQuotaArrangementOrFetch()
                                                                throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated PurchasingQuotaArrangement entity (one to one).
    If the navigation property to_PurchasingQuotaArrangement of a queried PurgQuotaArrangementItem 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.
    
    Returns:
    
    List of associated PurchasingQuotaArrangement entity.
    
    Throws:
    
    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.
  - getPurchasingQuotaArrangementOrNull
```
public com.google.common.base.Optional<PurchasingQuotaArrangement> getPurchasingQuotaArrangementOrNull()
```
    Retrieval of associated PurchasingQuotaArrangement entity (one to one).
    If the navigation property to_PurchasingQuotaArrangement for an entity PurgQuotaArrangementItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_PurchasingQuotaArrangement is already loaded, the result will contain the PurchasingQuotaArrangement entity. If not, a null value state is returned.
  - setPurchasingQuotaArrangement
```
public void setPurchasingQuotaArrangement(PurchasingQuotaArrangement value)
```
    Overwrites the associated PurchasingQuotaArrangement entity for the loaded navigation property to_PurchasingQuotaArrangement.
    
    Parameters:
    
    value - New PurchasingQuotaArrangement entity.
  - builder
```
public static PurgQuotaArrangementItem.PurgQuotaArrangementItemBuilder builder()
```
  - getQuotaArrangement
```
@Nullable
public String getQuotaArrangement()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Uniquely identifies the quota arrangement.
  - getQuotaArrangementItem
```
@Nullable
public String getQuotaArrangementItem()
```
    (Key Field) Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Uniquely identifies the quota arrangement item within a quota arrangement period.
  - getMaterialProcurementCategory
```
@Nullable
public String getMaterialProcurementCategory()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Indicates the type of procurement (that is, in-house manufacture, i.e. "making in", or external procurement, i.e. "buying out") for the quota arrangement item.
  - getMaterialProcurementType
```
@Nullable
public String getMaterialProcurementType()
```
    Constraints: Not nullable, Maximum length: 1
    A material which is procured externally can be acquired via a delivery schedule or a consignment order
    
    Returns:
    
    Indicator that determines the procurement type of the material and, consequently, how the material is procured.
  - getSupplier
```
@Nullable
public String getSupplier()
```
    Constraints: Not nullable, Maximum length: 10
    With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order). You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
    
    Returns:
    
    Alphanumeric key uniquely identifying the document.
  - getSupplyingPlant
```
@Nullable
public String getSupplyingPlant()
```
    Constraints: Not nullable, Maximum length: 4
    You can only enter one supplier number or one plant per quota arrangement item. In the case of process orders, this field should remain empty if the quota arrangement is being used to select a production version.
    
    Returns:
    
    Key for the factory or branch of a company (that is, a company code), from which the material is to be procured.
  - getPurchasingSourceQuota
```
@Nullable
public BigDecimal getPurchasingSourceQuota()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    If a certain material is to be procured alternately from different suppliers, you can create aquota arrangement item for each supplier and assign a quota to each such item. The system then selects the effective source of supply at any given time by means of the following formula: quota rating = quota base quantity + quota-allocated quantity ---------------------------------------------- quota This quota rating is calculated for all sources of supply included in the quota arrangement. The source then selected is the one with the lowest rating. Which supplier or item of an outline purchase agreement is valid at a certain point in time is determined via the source list. Enter the portion of the material requirement that is to be procured from the source. The value is automatically converted into a percentage. If the quota is to be temporarily excluded from the quota arrangement, you can set the quota to '_'. The requirement of a material is to be evenly distributed among three suppliers. That is, the system is to allocate a third of the total requirement to each supplier. Enter 1 as quota for each supplier; the quota per supplier will then automatically be converted to 33%.
    
    Returns:
    
    Number specifying which portion of a requirement is to be procured from a given source of supply.
  - getQuotaBaseQuantity
```
@Nullable
public BigDecimal getQuotaBaseQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Using the quota base quantity, you can regulate the quota arrangement without having to change the quota if, for example, a new source is to be included in the arrangement. You can set the quota base quantity manually or have it determined by the system.
    
    Returns:
    
    Control quantity for a quota arrangement.
  - getQuotaAllocatedQuantity
```
@Nullable
public BigDecimal getQuotaAllocatedQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    This value is updated in planned orders, purchase requisitions, purchase orders, and scheduling agreement delivery schedule lines.
    
    Returns:
    
    Total quantity procured to date from the quota arrangement item source.
  - getQuotaMaximumQuantity
```
@Nullable
public BigDecimal getQuotaMaximumQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    
    Returns:
    
    A quota arrangement item is no longer suggested as the source if the quota-allocated quantity is equal to or exceeds the maximum quantity.
  - getProductionVersion
```
@Nullable
public String getProductionVersion()
```
    Constraints: Not nullable, Maximum length: 4
    The production version determines the following: the BOM alternative for a BOM explosion the task list type, the task list group and the task list group counter for allocation to task lists lot-size restrictions for repetitive manufacturing
    
    Returns:
    
    Key which determines the various production techniques according to which a material can be manufactured.
  - getMaterialMaxLotSizeQuantity
```
@Nullable
public BigDecimal getMaterialMaxLotSizeQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    If the shortage (undercoverage) quantity exceeds the maximum lot size, the quota system is re-applied to the remaining quantity.
    
    Returns:
    
    Maximum PO quantity that may be allocated to a source of supply per order proposal in the planning run.
  - getMaterialMinLotSizeQuantity
```
@Nullable
public BigDecimal getMaterialMinLotSizeQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    If the shortage (undercoverage) quantity is less than the minimum lot size, the latter quantity will be allocated to the source instead of the former.
    
    Returns:
    
    Minimum order quantity that may be allocated to a source of supply per order proposal in the planning run.
  - getMaterialRoundingProfile
```
@Nullable
public String getMaterialRoundingProfile()
```
    Constraints: Not nullable, Maximum length: 4
    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 found If 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/subtracted With 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 -> 30 Requirement from 2 -> 5 requirement from 32 -> 40 Requirement from 6 -> 10 requirement from 74 -> 80 Requirement from 7 -> 10 If no rounding profile has been entered, the system uses the rounding value entered in the material master record for the planning run.
    
    Returns:
    
    Key that the system uses to adjust the order proposal quantity to deliverable units.
  - getSourceOfSupplyIsAssignedOnce
```
@Nullable
public Boolean getSourceOfSupplyIsAssignedOnce()
```
    Constraints: none
    If a maximum lot size is specified for a source of supply, and if this source has a much lower quota rating than other sources, the following happens: the lot is split up into several order proposals (each of which amounts to the maximum lot size) which are all assigned to the the source in question. To avoid this, you can set the "once-only" indicator. This will cause the source to be taken into account once only for an amount equal to the maximum lot size. The remaining quantity will be assigned to the next source.
    
    Returns:
    
    Specifies that a source may only be taken into account once in the apportionment of a lot.
  - getMaximumReleaseQuantity
```
@Nullable
public BigDecimal getMaximumReleaseQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    If a source with a maximum release quantity is next in line in a quota arrangement, in total no more than this maximum figure can be allocated to it within the specified period. If the lot in question exceeds this maximum, it will be split. The source in question will receive an order covering the difference between the quantity already released and the maximum release quantity. The balance of the lot will be allocated to the next source. The maximum release quantity is only taken into account in the planning run within MRP, not when purchase requisitions or planned orders are created manually.
    
    Returns:
    
    The "maximum release quantity" defines the maximum quantity that a source of supply can make available/supply within a specified timeframe.
  - getQuotaReleasePeriodType
```
@Nullable
public String getQuotaReleasePeriodType()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Period to Which the Release Quantity Relates
  - getNumberOfPeriodsPerRelQuantity
```
@Nullable
public String getNumberOfPeriodsPerRelQuantity()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    In this field, you determine the number of periods for which the maximum release quantity is valid.
  - getQuotaDeterminationPriority
```
@Nullable
public String getQuotaDeterminationPriority()
```
    Constraints: Not nullable, Maximum length: 2
    Example without splitting quota: If, for example, you enter priority one along with a maximum release quantity, then this source of supply is always selected until its maximum release quantity has been exhausted. Only then is the next source of supply selected. If no maximum release quantity was entered for the item with priority one, this item would always receive the complete requirement quantity. Example with splitting quota: In this procedure, the items are selected in the order of the quota. This sequence can be overridden using priorities. Please note that the splitting quantity is always based on the quota.
    
    Returns:
    
    The priority determines the sequence in which the individual sources of supply are used. Items with priority are always taken into consideration first, before the items for which no priority has been entered.
  - getManufacturerMaterial
```
@Nullable
public String getManufacturerMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    
    Returns:
    
    Uniquely identifies an MPN material.
  - getPlannedDeliveryDurationInDays
```
@Nullable
public BigDecimal getPlannedDeliveryDurationInDays()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    If you have different vendors for a material, you must specify an average value. The same applies if you order the material from a fixed vendor that has varying delivery times. If you use the SAP Retail System, the planned delivery time can be suggested from the vendor sub-range in the vendor master record.
    
    Returns:
    
    Number of calendar days needed to obtain the material or service if it is procured externally.
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setQuotaArrangement
```
public void setQuotaArrangement(@Nullable
                                String quotaArrangement)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    quotaArrangement -
  - setQuotaArrangementItem
```
public void setQuotaArrangementItem(@Nullable
                                    String quotaArrangementItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    quotaArrangementItem -
  - setMaterialProcurementCategory
```
public void setMaterialProcurementCategory(@Nullable
                                           String materialProcurementCategory)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    materialProcurementCategory -
  - setMaterialProcurementType
```
public void setMaterialProcurementType(@Nullable
                                       String materialProcurementType)
```
    Constraints: Not nullable, Maximum length: 1
    A material which is procured externally can be acquired via a delivery schedule or a consignment order
    
    Parameters:
    
    materialProcurementType -
  - setSupplier
```
public void setSupplier(@Nullable
                        String supplier)
```
    Constraints: Not nullable, Maximum length: 10
    With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order). You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
    
    Parameters:
    
    supplier -
  - setSupplyingPlant
```
public void setSupplyingPlant(@Nullable
                              String supplyingPlant)
```
    Constraints: Not nullable, Maximum length: 4
    You can only enter one supplier number or one plant per quota arrangement item. In the case of process orders, this field should remain empty if the quota arrangement is being used to select a production version.
    
    Parameters:
    
    supplyingPlant -
  - setPurchasingSourceQuota
```
public void setPurchasingSourceQuota(@Nullable
                                     BigDecimal purchasingSourceQuota)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    If a certain material is to be procured alternately from different suppliers, you can create aquota arrangement item for each supplier and assign a quota to each such item. The system then selects the effective source of supply at any given time by means of the following formula: quota rating = quota base quantity + quota-allocated quantity ---------------------------------------------- quota This quota rating is calculated for all sources of supply included in the quota arrangement. The source then selected is the one with the lowest rating. Which supplier or item of an outline purchase agreement is valid at a certain point in time is determined via the source list. Enter the portion of the material requirement that is to be procured from the source. The value is automatically converted into a percentage. If the quota is to be temporarily excluded from the quota arrangement, you can set the quota to '_'. The requirement of a material is to be evenly distributed among three suppliers. That is, the system is to allocate a third of the total requirement to each supplier. Enter 1 as quota for each supplier; the quota per supplier will then automatically be converted to 33%.
    
    Parameters:
    
    purchasingSourceQuota -
  - setQuotaBaseQuantity
```
public void setQuotaBaseQuantity(@Nullable
                                 BigDecimal quotaBaseQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Using the quota base quantity, you can regulate the quota arrangement without having to change the quota if, for example, a new source is to be included in the arrangement. You can set the quota base quantity manually or have it determined by the system.
    
    Parameters:
    
    quotaBaseQuantity -
  - setQuotaAllocatedQuantity
```
public void setQuotaAllocatedQuantity(@Nullable
                                      BigDecimal quotaAllocatedQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    This value is updated in planned orders, purchase requisitions, purchase orders, and scheduling agreement delivery schedule lines.
    
    Parameters:
    
    quotaAllocatedQuantity -
  - setQuotaMaximumQuantity
```
public void setQuotaMaximumQuantity(@Nullable
                                    BigDecimal quotaMaximumQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    
    Parameters:
    
    quotaMaximumQuantity -
  - setProductionVersion
```
public void setProductionVersion(@Nullable
                                 String productionVersion)
```
    Constraints: Not nullable, Maximum length: 4
    The production version determines the following: the BOM alternative for a BOM explosion the task list type, the task list group and the task list group counter for allocation to task lists lot-size restrictions for repetitive manufacturing
    
    Parameters:
    
    productionVersion -
  - setMaterialMaxLotSizeQuantity
```
public void setMaterialMaxLotSizeQuantity(@Nullable
                                          BigDecimal materialMaxLotSizeQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    If the shortage (undercoverage) quantity exceeds the maximum lot size, the quota system is re-applied to the remaining quantity.
    
    Parameters:
    
    materialMaxLotSizeQuantity -
  - setMaterialMinLotSizeQuantity
```
public void setMaterialMinLotSizeQuantity(@Nullable
                                          BigDecimal materialMinLotSizeQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    If the shortage (undercoverage) quantity is less than the minimum lot size, the latter quantity will be allocated to the source instead of the former.
    
    Parameters:
    
    materialMinLotSizeQuantity -
  - setMaterialRoundingProfile
```
public void setMaterialRoundingProfile(@Nullable
                                       String materialRoundingProfile)
```
    Constraints: Not nullable, Maximum length: 4
    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 found If 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/subtracted With 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 -> 30 Requirement from 2 -> 5 requirement from 32 -> 40 Requirement from 6 -> 10 requirement from 74 -> 80 Requirement from 7 -> 10 If no rounding profile has been entered, the system uses the rounding value entered in the material master record for the planning run.
    
    Parameters:
    
    materialRoundingProfile -
  - setSourceOfSupplyIsAssignedOnce
```
public void setSourceOfSupplyIsAssignedOnce(@Nullable
                                            Boolean sourceOfSupplyIsAssignedOnce)
```
    Constraints: none
    If a maximum lot size is specified for a source of supply, and if this source has a much lower quota rating than other sources, the following happens: the lot is split up into several order proposals (each of which amounts to the maximum lot size) which are all assigned to the the source in question. To avoid this, you can set the "once-only" indicator. This will cause the source to be taken into account once only for an amount equal to the maximum lot size. The remaining quantity will be assigned to the next source.
    
    Parameters:
    
    sourceOfSupplyIsAssignedOnce -
  - setMaximumReleaseQuantity
```
public void setMaximumReleaseQuantity(@Nullable
                                      BigDecimal maximumReleaseQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    If a source with a maximum release quantity is next in line in a quota arrangement, in total no more than this maximum figure can be allocated to it within the specified period. If the lot in question exceeds this maximum, it will be split. The source in question will receive an order covering the difference between the quantity already released and the maximum release quantity. The balance of the lot will be allocated to the next source. The maximum release quantity is only taken into account in the planning run within MRP, not when purchase requisitions or planned orders are created manually.
    
    Parameters:
    
    maximumReleaseQuantity -
  - setQuotaReleasePeriodType
```
public void setQuotaReleasePeriodType(@Nullable
                                      String quotaReleasePeriodType)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    quotaReleasePeriodType -
  - setNumberOfPeriodsPerRelQuantity
```
public void setNumberOfPeriodsPerRelQuantity(@Nullable
                                             String numberOfPeriodsPerRelQuantity)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    numberOfPeriodsPerRelQuantity -
  - setQuotaDeterminationPriority
```
public void setQuotaDeterminationPriority(@Nullable
                                          String quotaDeterminationPriority)
```
    Constraints: Not nullable, Maximum length: 2
    Example without splitting quota: If, for example, you enter priority one along with a maximum release quantity, then this source of supply is always selected until its maximum release quantity has been exhausted. Only then is the next source of supply selected. If no maximum release quantity was entered for the item with priority one, this item would always receive the complete requirement quantity. Example with splitting quota: In this procedure, the items are selected in the order of the quota. This sequence can be overridden using priorities. Please note that the splitting quantity is always based on the quota.
    
    Parameters:
    
    quotaDeterminationPriority -
  - setManufacturerMaterial
```
public void setManufacturerMaterial(@Nullable
                                    String manufacturerMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    
    Parameters:
    
    manufacturerMaterial -
  - setPlannedDeliveryDurationInDays
```
public void setPlannedDeliveryDurationInDays(@Nullable
                                             BigDecimal plannedDeliveryDurationInDays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    If you have different vendors for a material, you must specify an average value. The same applies if you order the material from a fixed vendor that has varying delivery times. If you use the SAP Retail System, the planned delivery time can be suggested from the vendor sub-range in the vendor master record.
    
    Parameters:
    
    plannedDeliveryDurationInDays -
  - setErpConfigContext
```
public void setErpConfigContext(@Nullable
                                ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Parameters:
    
    erpConfigContext -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<PurgQuotaArrangementItem>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<PurgQuotaArrangementItem>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<PurgQuotaArrangementItem>

Class PurgQuotaArrangementItem

Nested Class Summary

Field Summary

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmEntity

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

QUOTA_ARRANGEMENT

QUOTA_ARRANGEMENT_ITEM

MATERIAL_PROCUREMENT_CATEGORY

MATERIAL_PROCUREMENT_TYPE

SUPPLIER

SUPPLYING_PLANT

PURCHASING_SOURCE_QUOTA

QUOTA_BASE_QUANTITY

QUOTA_ALLOCATED_QUANTITY

QUOTA_MAXIMUM_QUANTITY

PRODUCTION_VERSION

MATERIAL_MAX_LOT_SIZE_QUANTITY

MATERIAL_MIN_LOT_SIZE_QUANTITY

MATERIAL_ROUNDING_PROFILE

SOURCE_OF_SUPPLY_IS_ASSIGNED_ONCE

MAXIMUM_RELEASE_QUANTITY

QUOTA_RELEASE_PERIOD_TYPE

NUMBER_OF_PERIODS_PER_REL_QUANTITY

QUOTA_DETERMINATION_PRIORITY

MANUFACTURER_MATERIAL

PLANNED_DELIVERY_DURATION_IN_DAYS

TO_PURCHASING_QUOTA_ARRANGEMENT

Constructor Detail

PurgQuotaArrangementItem

PurgQuotaArrangementItem

Method Detail

getType

field

fetchPurchasingQuotaArrangement

getPurchasingQuotaArrangementOrFetch

getPurchasingQuotaArrangementOrNull

setPurchasingQuotaArrangement

builder

getQuotaArrangement

getQuotaArrangementItem

getMaterialProcurementCategory

getMaterialProcurementType

getSupplier

getSupplyingPlant

getPurchasingSourceQuota

getQuotaBaseQuantity

getQuotaAllocatedQuantity

getQuotaMaximumQuantity

getProductionVersion

getMaterialMaxLotSizeQuantity

getMaterialMinLotSizeQuantity

getMaterialRoundingProfile

getSourceOfSupplyIsAssignedOnce

getMaximumReleaseQuantity

getQuotaReleasePeriodType

getNumberOfPeriodsPerRelQuantity

getQuotaDeterminationPriority

getManufacturerMaterial

getPlannedDeliveryDurationInDays

getErpConfigContext

setQuotaArrangement

setQuotaArrangementItem

setMaterialProcurementCategory

setMaterialProcurementType

setSupplier

setSupplyingPlant

setPurchasingSourceQuota

setQuotaBaseQuantity

setQuotaAllocatedQuantity

setQuotaMaximumQuantity

setProductionVersion

setMaterialMaxLotSizeQuantity

setMaterialMinLotSizeQuantity

setMaterialRoundingProfile

setSourceOfSupplyIsAssignedOnce