public class PurgQuotaArrangementItem extends VdmEntity<PurgQuotaArrangementItem>
Original entity name from the Odata EDM: A_PurgQuotaArrangementItemType
Modifier and Type | Class and Description |
---|---|
static class |
PurgQuotaArrangementItem.PurgQuotaArrangementItemBuilder |
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.
|
changedOriginalFields
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) |
Modifier and Type | Method and Description |
---|---|
static PurgQuotaArrangementItem.PurgQuotaArrangementItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
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.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
protected Map<String,Object> |
getKey() |
String |
getManufacturerMaterial()
Constraints: Not nullable, Maximum length: 40
|
BigDecimal |
getMaterialMaxLotSizeQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
BigDecimal |
getMaterialMinLotSizeQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getMaterialProcurementCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getMaterialProcurementType()
Constraints: Not nullable, Maximum length: 1
|
String |
getMaterialRoundingProfile()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getMaximumReleaseQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getNumberOfPeriodsPerRelQuantity()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getPlannedDeliveryDurationInDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getProductionVersion()
Constraints: Not nullable, Maximum length: 4
|
Optional<PurchasingQuotaArrangement> |
getPurchasingQuotaArrangementIfPresent()
Retrieval of associated PurchasingQuotaArrangement entity (one to one).
|
PurchasingQuotaArrangement |
getPurchasingQuotaArrangementOrFetch()
Retrieval of associated PurchasingQuotaArrangement entity (one to one).
|
BigDecimal |
getPurchasingSourceQuota()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getQuotaAllocatedQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
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
|
String |
getQuotaDeterminationPriority()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getQuotaMaximumQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getQuotaReleasePeriodType()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getSourceOfSupplyIsAssignedOnce()
Constraints: none
|
String |
getSupplier()
Constraints: Not nullable, Maximum length: 10
|
String |
getSupplyingPlant()
Constraints: Not nullable, Maximum length: 4
|
Class<PurgQuotaArrangementItem> |
getType() |
int |
hashCode() |
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setManufacturerMaterial(String manufacturerMaterial)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterialMaxLotSizeQuantity(BigDecimal materialMaxLotSizeQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setMaterialMinLotSizeQuantity(BigDecimal materialMinLotSizeQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setMaterialProcurementCategory(String materialProcurementCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setMaterialProcurementType(String materialProcurementType)
Constraints: Not nullable, Maximum length: 1
|
void |
setMaterialRoundingProfile(String materialRoundingProfile)
Constraints: Not nullable, Maximum length: 4
|
void |
setMaximumReleaseQuantity(BigDecimal maximumReleaseQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setNumberOfPeriodsPerRelQuantity(String numberOfPeriodsPerRelQuantity)
Constraints: Not nullable, Maximum length: 2
|
void |
setPlannedDeliveryDurationInDays(BigDecimal plannedDeliveryDurationInDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setProductionVersion(String productionVersion)
Constraints: Not nullable, Maximum length: 4
|
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
|
void |
setQuotaAllocatedQuantity(BigDecimal quotaAllocatedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
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
|
void |
setQuotaDeterminationPriority(String quotaDeterminationPriority)
Constraints: Not nullable, Maximum length: 2
|
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: none
|
void |
setSupplier(String supplier)
Constraints: Not nullable, Maximum length: 10
|
void |
setSupplyingPlant(String supplyingPlant)
Constraints: Not nullable, Maximum length: 4
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setServicePathForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final PurgQuotaArrangementItemSelectable ALL_FIELDS
public static final PurgQuotaArrangementItemField<String> QUOTA_ARRANGEMENT
public static final PurgQuotaArrangementItemField<String> QUOTA_ARRANGEMENT_ITEM
public static final PurgQuotaArrangementItemField<String> MATERIAL_PROCUREMENT_CATEGORY
public static final PurgQuotaArrangementItemField<String> MATERIAL_PROCUREMENT_TYPE
public static final PurgQuotaArrangementItemField<String> SUPPLIER
public static final PurgQuotaArrangementItemField<String> SUPPLYING_PLANT
public static final PurgQuotaArrangementItemField<BigDecimal> PURCHASING_SOURCE_QUOTA
public static final PurgQuotaArrangementItemField<BigDecimal> QUOTA_BASE_QUANTITY
public static final PurgQuotaArrangementItemField<BigDecimal> QUOTA_ALLOCATED_QUANTITY
public static final PurgQuotaArrangementItemField<BigDecimal> QUOTA_MAXIMUM_QUANTITY
public static final PurgQuotaArrangementItemField<String> PRODUCTION_VERSION
public static final PurgQuotaArrangementItemField<BigDecimal> MATERIAL_MAX_LOT_SIZE_QUANTITY
public static final PurgQuotaArrangementItemField<BigDecimal> MATERIAL_MIN_LOT_SIZE_QUANTITY
public static final PurgQuotaArrangementItemField<String> MATERIAL_ROUNDING_PROFILE
public static final PurgQuotaArrangementItemField<Boolean> SOURCE_OF_SUPPLY_IS_ASSIGNED_ONCE
public static final PurgQuotaArrangementItemField<BigDecimal> MAXIMUM_RELEASE_QUANTITY
public static final PurgQuotaArrangementItemField<String> QUOTA_RELEASE_PERIOD_TYPE
public static final PurgQuotaArrangementItemField<String> NUMBER_OF_PERIODS_PER_REL_QUANTITY
public static final PurgQuotaArrangementItemField<String> QUOTA_DETERMINATION_PRIORITY
public static final PurgQuotaArrangementItemField<String> MANUFACTURER_MATERIAL
public static final PurgQuotaArrangementItemField<BigDecimal> PLANNED_DELIVERY_DURATION_IN_DAYS
public static final PurgQuotaArrangementItemLink<PurchasingQuotaArrangement> TO_PURCHASING_QUOTA_ARRANGEMENT
public 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)
public Class<PurgQuotaArrangementItem> getType()
getType
in class VdmObject<PurgQuotaArrangementItem>
public void setQuotaArrangement(@Nullable String quotaArrangement)
Original property name from the Odata EDM: QuotaArrangement
quotaArrangement
- Uniquely identifies the quota arrangement.public void setQuotaArrangementItem(@Nullable String quotaArrangementItem)
Original property name from the Odata EDM: QuotaArrangementItem
quotaArrangementItem
- Uniquely identifies the quota arrangement item within a quota arrangement period.public void setMaterialProcurementCategory(@Nullable String materialProcurementCategory)
Original property name from the Odata EDM: MaterialProcurementCategory
materialProcurementCategory
- 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.public void setMaterialProcurementType(@Nullable String materialProcurementType)
Original property name from the Odata EDM: MaterialProcurementType
A material which is procured externally can be acquired via a delivery schedule or a consignment order
materialProcurementType
- Indicator that determines the procurement type of the material and, consequently, how the material is procured.public void setSupplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
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.
supplier
- Alphanumeric key uniquely identifying the document.public void setSupplyingPlant(@Nullable String supplyingPlant)
Original property name from the Odata EDM: SupplyingPlant
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.
supplyingPlant
- Key for the factory or branch of a company (that is, a company code), from which the material is to be procured.public void setPurchasingSourceQuota(@Nullable BigDecimal purchasingSourceQuota)
Original property name from the Odata EDM: PurchasingSourceQuota
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%.
purchasingSourceQuota
- Number specifying which portion of a requirement is to be procured from a given source of supply.public void setQuotaBaseQuantity(@Nullable BigDecimal quotaBaseQuantity)
Original property name from the Odata EDM: QuotaBaseQuantity
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.
quotaBaseQuantity
- Control quantity for a quota arrangement.public void setQuotaAllocatedQuantity(@Nullable BigDecimal quotaAllocatedQuantity)
Original property name from the Odata EDM: QuotaAllocatedQuantity
This value is updated in planned orders, purchase requisitions, purchase orders, and scheduling agreement delivery schedule lines.
quotaAllocatedQuantity
- Total quantity procured to date from the quota arrangement item source.public void setQuotaMaximumQuantity(@Nullable BigDecimal quotaMaximumQuantity)
Original property name from the Odata EDM: QuotaMaximumQuantity
quotaMaximumQuantity
- A quota arrangement item is no longer suggested as the source if the quota-allocated quantity is equal to or exceeds the maximum quantity.public void setProductionVersion(@Nullable String productionVersion)
Original property name from the Odata EDM: ProductionVersion
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
productionVersion
- Key which determines the various production techniques according to which a material can be manufactured.public void setMaterialMaxLotSizeQuantity(@Nullable BigDecimal materialMaxLotSizeQuantity)
Original property name from the Odata EDM: MaterialMaxLotSizeQuantity
If the shortage (undercoverage) quantity exceeds the maximum lot size, the quota system is re-applied to the remaining quantity.
materialMaxLotSizeQuantity
- Maximum PO quantity that may be allocated to a source of supply per order proposal in the planning run.public void setMaterialMinLotSizeQuantity(@Nullable BigDecimal materialMinLotSizeQuantity)
Original property name from the Odata EDM: MaterialMinLotSizeQuantity
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.
materialMinLotSizeQuantity
- Minimum order quantity that may be allocated to a source of supply per order proposal in the planning run.public void setMaterialRoundingProfile(@Nullable String materialRoundingProfile)
Original property name from the Odata EDM: MaterialRoundingProfile
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.
materialRoundingProfile
- Key that the system uses to adjust the order proposal quantity to deliverable units.public void setSourceOfSupplyIsAssignedOnce(@Nullable Boolean sourceOfSupplyIsAssignedOnce)
Original property name from the Odata EDM: SourceOfSupplyIsAssignedOnce
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.
sourceOfSupplyIsAssignedOnce
- Specifies that a source may only be taken into account once in the apportionment of a lot.public void setMaximumReleaseQuantity(@Nullable BigDecimal maximumReleaseQuantity)
Original property name from the Odata EDM: MaximumReleaseQuantity
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.
maximumReleaseQuantity
- The "maximum release quantity" defines the maximum quantity that a source of supply can make available/supply within a specified timeframe.public void setQuotaReleasePeriodType(@Nullable String quotaReleasePeriodType)
Original property name from the Odata EDM: QuotaReleasePeriodType
quotaReleasePeriodType
- Period to Which the Release Quantity Relatespublic void setNumberOfPeriodsPerRelQuantity(@Nullable String numberOfPeriodsPerRelQuantity)
Original property name from the Odata EDM: NumberOfPeriodsPerRelQuantity
numberOfPeriodsPerRelQuantity
- In this field, you determine the number of periods for which the maximum release quantity is valid.public void setQuotaDeterminationPriority(@Nullable String quotaDeterminationPriority)
Original property name from the Odata EDM: QuotaDeterminationPriority
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.
quotaDeterminationPriority
- 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.public void setManufacturerMaterial(@Nullable String manufacturerMaterial)
Original property name from the Odata EDM: ManufacturerMaterial
manufacturerMaterial
- Uniquely identifies an MPN material.public void setPlannedDeliveryDurationInDays(@Nullable BigDecimal plannedDeliveryDurationInDays)
Original property name from the Odata EDM: PlannedDeliveryDurationInDays
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.
plannedDeliveryDurationInDays
- Number of calendar days needed to obtain the material or service if it is procured externally.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<PurgQuotaArrangementItem>
protected Map<String,Object> getKey()
getKey
in class VdmObject<PurgQuotaArrangementItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<PurgQuotaArrangementItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<PurgQuotaArrangementItem>
@Nonnull public static <T> PurgQuotaArrangementItemField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
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.@Nonnull public static <T,DomainT> PurgQuotaArrangementItemField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<PurgQuotaArrangementItem>
public PurchasingQuotaArrangement fetchPurchasingQuotaArrangement() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
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.public PurchasingQuotaArrangement getPurchasingQuotaArrangementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
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.
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.public Optional<PurchasingQuotaArrangement> getPurchasingQuotaArrangementIfPresent()
If the navigation property for an entity PurgQuotaArrangementItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setPurchasingQuotaArrangement(PurchasingQuotaArrangement value)
value
- New PurchasingQuotaArrangement entity.public static PurgQuotaArrangementItem.PurgQuotaArrangementItemBuilder builder()
@Nullable public String getQuotaArrangement()
Original property name from the Odata EDM: QuotaArrangement
@Nullable public String getQuotaArrangementItem()
Original property name from the Odata EDM: QuotaArrangementItem
@Nullable public String getMaterialProcurementCategory()
Original property name from the Odata EDM: MaterialProcurementCategory
@Nullable public String getMaterialProcurementType()
Original property name from the Odata EDM: MaterialProcurementType
A material which is procured externally can be acquired via a delivery schedule or a consignment order
@Nullable public String getSupplier()
Original property name from the Odata EDM: Supplier
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.
@Nullable public String getSupplyingPlant()
Original property name from the Odata EDM: SupplyingPlant
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.
@Nullable public BigDecimal getPurchasingSourceQuota()
Original property name from the Odata EDM: PurchasingSourceQuota
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%.
@Nullable public BigDecimal getQuotaBaseQuantity()
Original property name from the Odata EDM: QuotaBaseQuantity
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.
@Nullable public BigDecimal getQuotaAllocatedQuantity()
Original property name from the Odata EDM: QuotaAllocatedQuantity
This value is updated in planned orders, purchase requisitions, purchase orders, and scheduling agreement delivery schedule lines.
@Nullable public BigDecimal getQuotaMaximumQuantity()
Original property name from the Odata EDM: QuotaMaximumQuantity
@Nullable public String getProductionVersion()
Original property name from the Odata EDM: ProductionVersion
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
@Nullable public BigDecimal getMaterialMaxLotSizeQuantity()
Original property name from the Odata EDM: MaterialMaxLotSizeQuantity
If the shortage (undercoverage) quantity exceeds the maximum lot size, the quota system is re-applied to the remaining quantity.
@Nullable public BigDecimal getMaterialMinLotSizeQuantity()
Original property name from the Odata EDM: MaterialMinLotSizeQuantity
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.
@Nullable public String getMaterialRoundingProfile()
Original property name from the Odata EDM: MaterialRoundingProfile
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.
@Nullable public Boolean getSourceOfSupplyIsAssignedOnce()
Original property name from the Odata EDM: SourceOfSupplyIsAssignedOnce
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.
@Nullable public BigDecimal getMaximumReleaseQuantity()
Original property name from the Odata EDM: MaximumReleaseQuantity
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.
@Nullable public String getQuotaReleasePeriodType()
Original property name from the Odata EDM: QuotaReleasePeriodType
@Nullable public String getNumberOfPeriodsPerRelQuantity()
Original property name from the Odata EDM: NumberOfPeriodsPerRelQuantity
@Nullable public String getQuotaDeterminationPriority()
Original property name from the Odata EDM: QuotaDeterminationPriority
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.
@Nullable public String getManufacturerMaterial()
Original property name from the Odata EDM: ManufacturerMaterial
@Nullable public BigDecimal getPlannedDeliveryDurationInDays()
Original property name from the Odata EDM: PlannedDeliveryDurationInDays
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.
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<PurgQuotaArrangementItem>
erpConfigContext
- public String toString()
toString
in class VdmObject<PurgQuotaArrangementItem>
public boolean equals(Object o)
equals
in class VdmObject<PurgQuotaArrangementItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<PurgQuotaArrangementItem>
public int hashCode()
hashCode
in class VdmObject<PurgQuotaArrangementItem>
Copyright © 2018 SAP SE. All rights reserved.