public class ProductSupplyPlanning extends VdmEntity<ProductSupplyPlanning>
Original entity name from the Odata EDM: A_ProductSupplyPlanningType
Modifier and Type | Class and Description |
---|---|
static class |
ProductSupplyPlanning.ProductSupplyPlanningBuilder |
Modifier and Type | Field and Description |
---|---|
static ProductSupplyPlanningField<String> |
ABC_INDICATOR
Use with available fluent helpers to apply the ABCIndicator field to query operations.
|
static ProductSupplyPlanningSelectable |
ALL_FIELDS
Selector for all available fields of ProductSupplyPlanning.
|
static ProductSupplyPlanningField<BigDecimal> |
ASSEMBLY_SCRAP_PERCENT
Use with available fluent helpers to apply the AssemblyScrapPercent field to query operations.
|
static ProductSupplyPlanningField<String> |
AVAILABILITY_CHECK_TYPE
Use with available fluent helpers to apply the AvailabilityCheckType field to query operations.
|
static ProductSupplyPlanningField<String> |
BACKWARD_CNSMPN_PERIOD_IN_WORK_DAYS
Use with available fluent helpers to apply the BackwardCnsmpnPeriodInWorkDays field to query operations.
|
static ProductSupplyPlanningField<String> |
BASE_UNIT
Use with available fluent helpers to apply the BaseUnit field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
COMPONENT_SCRAP_IN_PERCENT
Use with available fluent helpers to apply the ComponentScrapInPercent field to query operations.
|
static ProductSupplyPlanningField<String> |
CURRENCY
Use with available fluent helpers to apply the Currency field to query operations.
|
static ProductSupplyPlanningField<String> |
DEPENDENT_REQUIREMENTS_TYPE
Use with available fluent helpers to apply the DependentRequirementsType field to query operations.
|
static ProductSupplyPlanningField<String> |
DFLT_STORAGE_LOCATION_EXT_PROCMT
Use with available fluent helpers to apply the DfltStorageLocationExtProcmt field to query operations.
|
static ProductSupplyPlanningField<LocalDateTime> |
EFFECTIVE_OUT_DATE
Use with available fluent helpers to apply the EffectiveOutDate field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
FIXED_LOT_SIZE_QUANTITY
Use with available fluent helpers to apply the FixedLotSizeQuantity field to query operations.
|
static ProductSupplyPlanningField<String> |
FOLLOW_UP_PRODUCT
Use with available fluent helpers to apply the FollowUpProduct field to query operations.
|
static ProductSupplyPlanningField<String> |
FORECAST_REQUIREMENTS_ARE_SPLIT
Use with available fluent helpers to apply the ForecastRequirementsAreSplit field to query operations.
|
static ProductSupplyPlanningField<String> |
FWD_CONSUMPTION_PERIOD_IN_WORK_DAYS
Use with available fluent helpers to apply the FwdConsumptionPeriodInWorkDays field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
GOODS_RECEIPT_DURATION
Use with available fluent helpers to apply the GoodsReceiptDuration field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
IN_HOUSE_PRODUCTION_TIME
Use with available fluent helpers to apply the InHouseProductionTime field to query operations.
|
static ProductSupplyPlanningField<Boolean> |
IS_BULK_MATERIAL_COMPONENT
Use with available fluent helpers to apply the IsBulkMaterialComponent field to query operations.
|
static ProductSupplyPlanningField<String> |
IS_MRP_DEPENDENT_RQMT
Use with available fluent helpers to apply the IsMRPDependentRqmt field to query operations.
|
static ProductSupplyPlanningField<String> |
IS_SAFETY_TIME
Use with available fluent helpers to apply the IsSafetyTime field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
LOT_SIZE_INDEPENDENT_COSTS
Use with available fluent helpers to apply the LotSizeIndependentCosts field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
LOT_SIZE_ROUNDING_QUANTITY
Use with available fluent helpers to apply the LotSizeRoundingQuantity field to query operations.
|
static ProductSupplyPlanningField<String> |
LOT_SIZING_PROCEDURE
Use with available fluent helpers to apply the LotSizingProcedure field to query operations.
|
static ProductSupplyPlanningField<String> |
MATL_COMP_IS_MARKED_FOR_BACKFLUSH
Use with available fluent helpers to apply the MatlCompIsMarkedForBackflush field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
MAXIMUM_LOT_SIZE_QUANTITY
Use with available fluent helpers to apply the MaximumLotSizeQuantity field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
MAXIMUM_STOCK_QUANTITY
Use with available fluent helpers to apply the MaximumStockQuantity field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
MINIMUM_LOT_SIZE_QUANTITY
Use with available fluent helpers to apply the MinimumLotSizeQuantity field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
MINIMUM_SAFETY_STOCK_QUANTITY
Use with available fluent helpers to apply the MinimumSafetyStockQuantity field to query operations.
|
static ProductSupplyPlanningField<String> |
MRP_AVAILABILITY_TYPE
Use with available fluent helpers to apply the MRPAvailabilityType field to query operations.
|
static ProductSupplyPlanningField<String> |
MRP_GROUP
Use with available fluent helpers to apply the MRPGroup field to query operations.
|
static ProductSupplyPlanningField<String> |
MRP_PLANNING_CALENDAR
Use with available fluent helpers to apply the MRPPlanningCalendar field to query operations.
|
static ProductSupplyPlanningField<String> |
MRP_PROFILE
Use with available fluent helpers to apply the MRPProfile field to query operations.
|
static ProductSupplyPlanningField<String> |
MRP_RESPONSIBLE
Use with available fluent helpers to apply the MRPResponsible field to query operations.
|
static ProductSupplyPlanningField<String> |
MRP_TYPE
Use with available fluent helpers to apply the MRPType field to query operations.
|
static ProductSupplyPlanningField<String> |
PERD_PRFL_FOR_SFTY_TME
Use with available fluent helpers to apply the PerdPrflForSftyTme field to query operations.
|
static ProductSupplyPlanningField<String> |
PLAN_AND_ORDER_DAY_DETERMINATION
Use with available fluent helpers to apply the PlanAndOrderDayDetermination field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
PLANNED_DELIVERY_DURATION_IN_DAYS
Use with available fluent helpers to apply the PlannedDeliveryDurationInDays field to query operations.
|
static ProductSupplyPlanningField<String> |
PLANNED_ORDER_ACTION_CONTROL
Use with available fluent helpers to apply the PlannedOrderActionControl field to query operations.
|
static ProductSupplyPlanningField<String> |
PLANNING_STRATEGY_GROUP
Use with available fluent helpers to apply the PlanningStrategyGroup field to query operations.
|
static ProductSupplyPlanningField<String> |
PLANNING_TIME_FENCE
Use with available fluent helpers to apply the PlanningTimeFence field to query operations.
|
static ProductSupplyPlanningField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static ProductSupplyPlanningField<String> |
PROCUREMENT_SUB_TYPE
Use with available fluent helpers to apply the ProcurementSubType field to query operations.
|
static ProductSupplyPlanningField<String> |
PROCUREMENT_TYPE
Use with available fluent helpers to apply the ProcurementType field to query operations.
|
static ProductSupplyPlanningField<String> |
PROD_RQMTS_ARE_CONSOLIDATED
Use with available fluent helpers to apply the ProdRqmtsAreConsolidated field to query operations.
|
static ProductSupplyPlanningField<String> |
PROD_RQMTS_CONSUMPTION_MODE
Use with available fluent helpers to apply the ProdRqmtsConsumptionMode field to query operations.
|
static ProductSupplyPlanningField<String> |
PRODUCT
Use with available fluent helpers to apply the Product field to query operations.
|
static ProductSupplyPlanningField<String> |
PRODUCT_IS_FOR_CROSS_PROJECT
Use with available fluent helpers to apply the ProductIsForCrossProject field to query operations.
|
static ProductSupplyPlanningField<String> |
PRODUCT_IS_TO_BE_DISCONTINUED
Use with available fluent helpers to apply the ProductIsToBeDiscontinued field to query operations.
|
static ProductSupplyPlanningField<String> |
PROPOSED_PRODUCT_SUPPLY_AREA
Use with available fluent helpers to apply the ProposedProductSupplyArea field to query operations.
|
static ProductSupplyPlanningField<String> |
RANGE_OF_CVRG_PRFL_CODE
Use with available fluent helpers to apply the RangeOfCvrgPrflCode field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
REORDER_THRESHOLD_QUANTITY
Use with available fluent helpers to apply the ReorderThresholdQuantity field to query operations.
|
static ProductSupplyPlanningField<Boolean> |
REPETITIVE_MANUFACTURING_IS_ALLWD
Use with available fluent helpers to apply the RepetitiveManufacturingIsAllwd field to query operations.
|
static ProductSupplyPlanningField<String> |
REPETITIVE_MANUFACTURING_PROFILE
Use with available fluent helpers to apply the RepetitiveManufacturingProfile field to query operations.
|
static ProductSupplyPlanningField<String> |
ROUNDING_PROFILE
Use with available fluent helpers to apply the RoundingProfile field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
RQMT_QTY_RCPT_TAKT_TME_IN_WRKG_DAYS
Use with available fluent helpers to apply the RqmtQtyRcptTaktTmeInWrkgDays field to query operations.
|
static ProductSupplyPlanningField<String> |
SAFETY_DURATION
Use with available fluent helpers to apply the SafetyDuration field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
SAFETY_STOCK_QUANTITY
Use with available fluent helpers to apply the SafetyStockQuantity field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
SRVC_LVL
Use with available fluent helpers to apply the SrvcLvl field to query operations.
|
static ProductSupplyPlanningField<String> |
STORAGE_COSTS_PERCENTAGE_CODE
Use with available fluent helpers to apply the StorageCostsPercentageCode field to query operations.
|
static ProductSupplyPlanningField<BigDecimal> |
TOTAL_REPLENISHMENT_LEAD_TIME
Use with available fluent helpers to apply the TotalReplenishmentLeadTime field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
ProductSupplyPlanning() |
ProductSupplyPlanning(String product,
String plant,
BigDecimal fixedLotSizeQuantity,
BigDecimal maximumLotSizeQuantity,
BigDecimal minimumLotSizeQuantity,
BigDecimal lotSizeRoundingQuantity,
String lotSizingProcedure,
String mRPType,
String mRPResponsible,
BigDecimal safetyStockQuantity,
BigDecimal minimumSafetyStockQuantity,
String planningTimeFence,
String aBCIndicator,
BigDecimal maximumStockQuantity,
BigDecimal reorderThresholdQuantity,
BigDecimal plannedDeliveryDurationInDays,
String safetyDuration,
String planningStrategyGroup,
BigDecimal totalReplenishmentLeadTime,
String procurementType,
String procurementSubType,
BigDecimal assemblyScrapPercent,
String availabilityCheckType,
BigDecimal goodsReceiptDuration,
String mRPGroup,
String dfltStorageLocationExtProcmt,
String prodRqmtsConsumptionMode,
String backwardCnsmpnPeriodInWorkDays,
String fwdConsumptionPeriodInWorkDays,
String baseUnit,
String planAndOrderDayDetermination,
String roundingProfile,
BigDecimal lotSizeIndependentCosts,
String mRPPlanningCalendar,
String rangeOfCvrgPrflCode,
String isSafetyTime,
String perdPrflForSftyTme,
String isMRPDependentRqmt,
BigDecimal inHouseProductionTime,
String productIsForCrossProject,
String storageCostsPercentageCode,
BigDecimal srvcLvl,
String mRPAvailabilityType,
String followUpProduct,
Boolean repetitiveManufacturingIsAllwd,
String dependentRequirementsType,
Boolean isBulkMaterialComponent,
String repetitiveManufacturingProfile,
BigDecimal rqmtQtyRcptTaktTmeInWrkgDays,
String forecastRequirementsAreSplit,
LocalDateTime effectiveOutDate,
String mRPProfile,
BigDecimal componentScrapInPercent,
String productIsToBeDiscontinued,
String prodRqmtsAreConsolidated,
String matlCompIsMarkedForBackflush,
String proposedProductSupplyArea,
String currency,
String plannedOrderActionControl) |
Modifier and Type | Method and Description |
---|---|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static ProductSupplyPlanning.ProductSupplyPlanningBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> ProductSupplyPlanningField<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) |
String |
getABCIndicator()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getAssemblyScrapPercent()
Constraints: Not nullable, Precision: 5, Scale: 2
|
String |
getAvailabilityCheckType()
Constraints: Not nullable, Maximum length: 2
|
String |
getBackwardCnsmpnPeriodInWorkDays()
Constraints: Not nullable, Maximum length: 3
|
String |
getBaseUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getComponentScrapInPercent()
Constraints: Not nullable, Precision: 5, Scale: 2
|
String |
getCurrency()
Constraints: Not nullable, Maximum length: 5
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getDependentRequirementsType()
Constraints: Not nullable, Maximum length: 1
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
String |
getDfltStorageLocationExtProcmt()
Constraints: Not nullable, Maximum length: 4
|
LocalDateTime |
getEffectiveOutDate()
Constraints: Not nullable, Precision: 0
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
BigDecimal |
getFixedLotSizeQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getFollowUpProduct()
Constraints: Not nullable, Maximum length: 40
|
String |
getForecastRequirementsAreSplit()
Constraints: Not nullable, Maximum length: 1
|
String |
getFwdConsumptionPeriodInWorkDays()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getGoodsReceiptDuration()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getInHouseProductionTime()
Constraints: Not nullable, Precision: 3, Scale: 0
|
Boolean |
getIsBulkMaterialComponent()
Constraints: none
|
String |
getIsMRPDependentRqmt()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsSafetyTime()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
BigDecimal |
getLotSizeIndependentCosts()
Constraints: Not nullable, Precision: 12, Scale: 3
|
BigDecimal |
getLotSizeRoundingQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getLotSizingProcedure()
Constraints: Not nullable, Maximum length: 2
|
String |
getMatlCompIsMarkedForBackflush()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getMaximumLotSizeQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
BigDecimal |
getMaximumStockQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
BigDecimal |
getMinimumLotSizeQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
BigDecimal |
getMinimumSafetyStockQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getMRPAvailabilityType()
Constraints: Not nullable, Maximum length: 1
|
String |
getMRPGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getMRPPlanningCalendar()
Constraints: Not nullable, Maximum length: 3
|
String |
getMRPProfile()
Constraints: Not nullable, Maximum length: 4
|
String |
getMRPResponsible()
Constraints: Not nullable, Maximum length: 3
|
String |
getMRPType()
Constraints: Not nullable, Maximum length: 2
|
String |
getPerdPrflForSftyTme()
Constraints: Not nullable, Maximum length: 3
|
String |
getPlanAndOrderDayDetermination()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getPlannedDeliveryDurationInDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getPlannedOrderActionControl()
Constraints: Not nullable, Maximum length: 2
|
String |
getPlanningStrategyGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getPlanningTimeFence()
Constraints: Not nullable, Maximum length: 3
|
String |
getPlant()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getProcurementSubType()
Constraints: Not nullable, Maximum length: 2
|
String |
getProcurementType()
Constraints: Not nullable, Maximum length: 1
|
String |
getProdRqmtsAreConsolidated()
Constraints: Not nullable, Maximum length: 1
|
String |
getProdRqmtsConsumptionMode()
Constraints: Not nullable, Maximum length: 1
|
String |
getProduct()
(Key Field) Constraints: Not nullable, Maximum length: 40
|
String |
getProductIsForCrossProject()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductIsToBeDiscontinued()
Constraints: Not nullable, Maximum length: 1
|
String |
getProposedProductSupplyArea()
Constraints: Not nullable, Maximum length: 10
|
String |
getRangeOfCvrgPrflCode()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getReorderThresholdQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
Boolean |
getRepetitiveManufacturingIsAllwd()
Constraints: none
|
String |
getRepetitiveManufacturingProfile()
Constraints: Not nullable, Maximum length: 4
|
String |
getRoundingProfile()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getRqmtQtyRcptTaktTmeInWrkgDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getSafetyDuration()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getSafetyStockQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
BigDecimal |
getSrvcLvl()
Constraints: Not nullable, Precision: 3, Scale: 1
|
String |
getStorageCostsPercentageCode()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getTotalReplenishmentLeadTime()
Constraints: Not nullable, Precision: 3, Scale: 0
|
Class<ProductSupplyPlanning> |
getType() |
int |
hashCode() |
void |
setABCIndicator(String aBCIndicator)
Constraints: Not nullable, Maximum length: 1
|
void |
setAssemblyScrapPercent(BigDecimal assemblyScrapPercent)
Constraints: Not nullable, Precision: 5, Scale: 2
|
void |
setAvailabilityCheckType(String availabilityCheckType)
Constraints: Not nullable, Maximum length: 2
|
void |
setBackwardCnsmpnPeriodInWorkDays(String backwardCnsmpnPeriodInWorkDays)
Constraints: Not nullable, Maximum length: 3
|
void |
setBaseUnit(String baseUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setComponentScrapInPercent(BigDecimal componentScrapInPercent)
Constraints: Not nullable, Precision: 5, Scale: 2
|
void |
setCurrency(String currency)
Constraints: Not nullable, Maximum length: 5
|
void |
setDependentRequirementsType(String dependentRequirementsType)
Constraints: Not nullable, Maximum length: 1
|
void |
setDfltStorageLocationExtProcmt(String dfltStorageLocationExtProcmt)
Constraints: Not nullable, Maximum length: 4
|
void |
setEffectiveOutDate(LocalDateTime effectiveOutDate)
Constraints: Not nullable, Precision: 0
|
void |
setFixedLotSizeQuantity(BigDecimal fixedLotSizeQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setFollowUpProduct(String followUpProduct)
Constraints: Not nullable, Maximum length: 40
|
void |
setForecastRequirementsAreSplit(String forecastRequirementsAreSplit)
Constraints: Not nullable, Maximum length: 1
|
void |
setFwdConsumptionPeriodInWorkDays(String fwdConsumptionPeriodInWorkDays)
Constraints: Not nullable, Maximum length: 3
|
void |
setGoodsReceiptDuration(BigDecimal goodsReceiptDuration)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setInHouseProductionTime(BigDecimal inHouseProductionTime)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setIsBulkMaterialComponent(Boolean isBulkMaterialComponent)
Constraints: none
|
void |
setIsMRPDependentRqmt(String isMRPDependentRqmt)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsSafetyTime(String isSafetyTime)
Constraints: Not nullable, Maximum length: 1
|
void |
setLotSizeIndependentCosts(BigDecimal lotSizeIndependentCosts)
Constraints: Not nullable, Precision: 12, Scale: 3
|
void |
setLotSizeRoundingQuantity(BigDecimal lotSizeRoundingQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setLotSizingProcedure(String lotSizingProcedure)
Constraints: Not nullable, Maximum length: 2
|
void |
setMatlCompIsMarkedForBackflush(String matlCompIsMarkedForBackflush)
Constraints: Not nullable, Maximum length: 1
|
void |
setMaximumLotSizeQuantity(BigDecimal maximumLotSizeQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setMaximumStockQuantity(BigDecimal maximumStockQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setMinimumLotSizeQuantity(BigDecimal minimumLotSizeQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setMinimumSafetyStockQuantity(BigDecimal minimumSafetyStockQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setMRPAvailabilityType(String mRPAvailabilityType)
Constraints: Not nullable, Maximum length: 1
|
void |
setMRPGroup(String mRPGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setMRPPlanningCalendar(String mRPPlanningCalendar)
Constraints: Not nullable, Maximum length: 3
|
void |
setMRPProfile(String mRPProfile)
Constraints: Not nullable, Maximum length: 4
|
void |
setMRPResponsible(String mRPResponsible)
Constraints: Not nullable, Maximum length: 3
|
void |
setMRPType(String mRPType)
Constraints: Not nullable, Maximum length: 2
|
void |
setPerdPrflForSftyTme(String perdPrflForSftyTme)
Constraints: Not nullable, Maximum length: 3
|
void |
setPlanAndOrderDayDetermination(String planAndOrderDayDetermination)
Constraints: Not nullable, Maximum length: 3
|
void |
setPlannedDeliveryDurationInDays(BigDecimal plannedDeliveryDurationInDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setPlannedOrderActionControl(String plannedOrderActionControl)
Constraints: Not nullable, Maximum length: 2
|
void |
setPlanningStrategyGroup(String planningStrategyGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setPlanningTimeFence(String planningTimeFence)
Constraints: Not nullable, Maximum length: 3
|
void |
setPlant(String plant)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setProcurementSubType(String procurementSubType)
Constraints: Not nullable, Maximum length: 2
|
void |
setProcurementType(String procurementType)
Constraints: Not nullable, Maximum length: 1
|
void |
setProdRqmtsAreConsolidated(String prodRqmtsAreConsolidated)
Constraints: Not nullable, Maximum length: 1
|
void |
setProdRqmtsConsumptionMode(String prodRqmtsConsumptionMode)
Constraints: Not nullable, Maximum length: 1
|
void |
setProduct(String product)
(Key Field) Constraints: Not nullable, Maximum length: 40
|
void |
setProductIsForCrossProject(String productIsForCrossProject)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductIsToBeDiscontinued(String productIsToBeDiscontinued)
Constraints: Not nullable, Maximum length: 1
|
void |
setProposedProductSupplyArea(String proposedProductSupplyArea)
Constraints: Not nullable, Maximum length: 10
|
void |
setRangeOfCvrgPrflCode(String rangeOfCvrgPrflCode)
Constraints: Not nullable, Maximum length: 3
|
void |
setReorderThresholdQuantity(BigDecimal reorderThresholdQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setRepetitiveManufacturingIsAllwd(Boolean repetitiveManufacturingIsAllwd)
Constraints: none
|
void |
setRepetitiveManufacturingProfile(String repetitiveManufacturingProfile)
Constraints: Not nullable, Maximum length: 4
|
void |
setRoundingProfile(String roundingProfile)
Constraints: Not nullable, Maximum length: 4
|
void |
setRqmtQtyRcptTaktTmeInWrkgDays(BigDecimal rqmtQtyRcptTaktTmeInWrkgDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setSafetyDuration(String safetyDuration)
Constraints: Not nullable, Maximum length: 2
|
void |
setSafetyStockQuantity(BigDecimal safetyStockQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setSrvcLvl(BigDecimal srvcLvl)
Constraints: Not nullable, Precision: 3, Scale: 1
|
void |
setStorageCostsPercentageCode(String storageCostsPercentageCode)
Constraints: Not nullable, Maximum length: 1
|
void |
setTotalReplenishmentLeadTime(BigDecimal totalReplenishmentLeadTime)
Constraints: Not nullable, Precision: 3, Scale: 0
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final ProductSupplyPlanningSelectable ALL_FIELDS
public static final ProductSupplyPlanningField<String> PRODUCT
public static final ProductSupplyPlanningField<String> PLANT
public static final ProductSupplyPlanningField<BigDecimal> FIXED_LOT_SIZE_QUANTITY
public static final ProductSupplyPlanningField<BigDecimal> MAXIMUM_LOT_SIZE_QUANTITY
public static final ProductSupplyPlanningField<BigDecimal> MINIMUM_LOT_SIZE_QUANTITY
public static final ProductSupplyPlanningField<BigDecimal> LOT_SIZE_ROUNDING_QUANTITY
public static final ProductSupplyPlanningField<String> LOT_SIZING_PROCEDURE
public static final ProductSupplyPlanningField<String> MRP_TYPE
public static final ProductSupplyPlanningField<String> MRP_RESPONSIBLE
public static final ProductSupplyPlanningField<BigDecimal> SAFETY_STOCK_QUANTITY
public static final ProductSupplyPlanningField<BigDecimal> MINIMUM_SAFETY_STOCK_QUANTITY
public static final ProductSupplyPlanningField<String> PLANNING_TIME_FENCE
public static final ProductSupplyPlanningField<String> ABC_INDICATOR
public static final ProductSupplyPlanningField<BigDecimal> MAXIMUM_STOCK_QUANTITY
public static final ProductSupplyPlanningField<BigDecimal> REORDER_THRESHOLD_QUANTITY
public static final ProductSupplyPlanningField<BigDecimal> PLANNED_DELIVERY_DURATION_IN_DAYS
public static final ProductSupplyPlanningField<String> SAFETY_DURATION
public static final ProductSupplyPlanningField<String> PLANNING_STRATEGY_GROUP
public static final ProductSupplyPlanningField<BigDecimal> TOTAL_REPLENISHMENT_LEAD_TIME
public static final ProductSupplyPlanningField<String> PROCUREMENT_TYPE
public static final ProductSupplyPlanningField<String> PROCUREMENT_SUB_TYPE
public static final ProductSupplyPlanningField<BigDecimal> ASSEMBLY_SCRAP_PERCENT
public static final ProductSupplyPlanningField<String> AVAILABILITY_CHECK_TYPE
public static final ProductSupplyPlanningField<BigDecimal> GOODS_RECEIPT_DURATION
public static final ProductSupplyPlanningField<String> MRP_GROUP
public static final ProductSupplyPlanningField<String> DFLT_STORAGE_LOCATION_EXT_PROCMT
public static final ProductSupplyPlanningField<String> PROD_RQMTS_CONSUMPTION_MODE
public static final ProductSupplyPlanningField<String> BACKWARD_CNSMPN_PERIOD_IN_WORK_DAYS
public static final ProductSupplyPlanningField<String> FWD_CONSUMPTION_PERIOD_IN_WORK_DAYS
public static final ProductSupplyPlanningField<String> BASE_UNIT
public static final ProductSupplyPlanningField<String> PLAN_AND_ORDER_DAY_DETERMINATION
public static final ProductSupplyPlanningField<String> ROUNDING_PROFILE
public static final ProductSupplyPlanningField<BigDecimal> LOT_SIZE_INDEPENDENT_COSTS
public static final ProductSupplyPlanningField<String> MRP_PLANNING_CALENDAR
public static final ProductSupplyPlanningField<String> RANGE_OF_CVRG_PRFL_CODE
public static final ProductSupplyPlanningField<String> IS_SAFETY_TIME
public static final ProductSupplyPlanningField<String> PERD_PRFL_FOR_SFTY_TME
public static final ProductSupplyPlanningField<String> IS_MRP_DEPENDENT_RQMT
public static final ProductSupplyPlanningField<BigDecimal> IN_HOUSE_PRODUCTION_TIME
public static final ProductSupplyPlanningField<String> PRODUCT_IS_FOR_CROSS_PROJECT
public static final ProductSupplyPlanningField<String> STORAGE_COSTS_PERCENTAGE_CODE
public static final ProductSupplyPlanningField<BigDecimal> SRVC_LVL
public static final ProductSupplyPlanningField<String> MRP_AVAILABILITY_TYPE
public static final ProductSupplyPlanningField<String> FOLLOW_UP_PRODUCT
public static final ProductSupplyPlanningField<Boolean> REPETITIVE_MANUFACTURING_IS_ALLWD
public static final ProductSupplyPlanningField<String> DEPENDENT_REQUIREMENTS_TYPE
public static final ProductSupplyPlanningField<Boolean> IS_BULK_MATERIAL_COMPONENT
public static final ProductSupplyPlanningField<String> REPETITIVE_MANUFACTURING_PROFILE
public static final ProductSupplyPlanningField<BigDecimal> RQMT_QTY_RCPT_TAKT_TME_IN_WRKG_DAYS
public static final ProductSupplyPlanningField<String> FORECAST_REQUIREMENTS_ARE_SPLIT
public static final ProductSupplyPlanningField<LocalDateTime> EFFECTIVE_OUT_DATE
public static final ProductSupplyPlanningField<String> MRP_PROFILE
public static final ProductSupplyPlanningField<BigDecimal> COMPONENT_SCRAP_IN_PERCENT
public static final ProductSupplyPlanningField<String> PRODUCT_IS_TO_BE_DISCONTINUED
public static final ProductSupplyPlanningField<String> PROD_RQMTS_ARE_CONSOLIDATED
public static final ProductSupplyPlanningField<String> MATL_COMP_IS_MARKED_FOR_BACKFLUSH
public static final ProductSupplyPlanningField<String> PROPOSED_PRODUCT_SUPPLY_AREA
public static final ProductSupplyPlanningField<String> CURRENCY
public static final ProductSupplyPlanningField<String> PLANNED_ORDER_ACTION_CONTROL
public ProductSupplyPlanning()
public ProductSupplyPlanning(@Nullable String product, @Nullable String plant, @Nullable BigDecimal fixedLotSizeQuantity, @Nullable BigDecimal maximumLotSizeQuantity, @Nullable BigDecimal minimumLotSizeQuantity, @Nullable BigDecimal lotSizeRoundingQuantity, @Nullable String lotSizingProcedure, @Nullable String mRPType, @Nullable String mRPResponsible, @Nullable BigDecimal safetyStockQuantity, @Nullable BigDecimal minimumSafetyStockQuantity, @Nullable String planningTimeFence, @Nullable String aBCIndicator, @Nullable BigDecimal maximumStockQuantity, @Nullable BigDecimal reorderThresholdQuantity, @Nullable BigDecimal plannedDeliveryDurationInDays, @Nullable String safetyDuration, @Nullable String planningStrategyGroup, @Nullable BigDecimal totalReplenishmentLeadTime, @Nullable String procurementType, @Nullable String procurementSubType, @Nullable BigDecimal assemblyScrapPercent, @Nullable String availabilityCheckType, @Nullable BigDecimal goodsReceiptDuration, @Nullable String mRPGroup, @Nullable String dfltStorageLocationExtProcmt, @Nullable String prodRqmtsConsumptionMode, @Nullable String backwardCnsmpnPeriodInWorkDays, @Nullable String fwdConsumptionPeriodInWorkDays, @Nullable String baseUnit, @Nullable String planAndOrderDayDetermination, @Nullable String roundingProfile, @Nullable BigDecimal lotSizeIndependentCosts, @Nullable String mRPPlanningCalendar, @Nullable String rangeOfCvrgPrflCode, @Nullable String isSafetyTime, @Nullable String perdPrflForSftyTme, @Nullable String isMRPDependentRqmt, @Nullable BigDecimal inHouseProductionTime, @Nullable String productIsForCrossProject, @Nullable String storageCostsPercentageCode, @Nullable BigDecimal srvcLvl, @Nullable String mRPAvailabilityType, @Nullable String followUpProduct, @Nullable Boolean repetitiveManufacturingIsAllwd, @Nullable String dependentRequirementsType, @Nullable Boolean isBulkMaterialComponent, @Nullable String repetitiveManufacturingProfile, @Nullable BigDecimal rqmtQtyRcptTaktTmeInWrkgDays, @Nullable String forecastRequirementsAreSplit, @Nullable LocalDateTime effectiveOutDate, @Nullable String mRPProfile, @Nullable BigDecimal componentScrapInPercent, @Nullable String productIsToBeDiscontinued, @Nullable String prodRqmtsAreConsolidated, @Nullable String matlCompIsMarkedForBackflush, @Nullable String proposedProductSupplyArea, @Nullable String currency, @Nullable String plannedOrderActionControl)
@Nonnull public Class<ProductSupplyPlanning> getType()
getType
in class VdmObject<ProductSupplyPlanning>
public void setProduct(@Nullable String product)
Original property name from the Odata EDM: Product
product
- Alphanumeric key uniquely identifying the material.public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setFixedLotSizeQuantity(@Nullable BigDecimal fixedLotSizeQuantity)
Original property name from the Odata EDM: FixedLotSizeQuantity
If the amount of the shortage is less than the fixed lot size, it is the fixed lot size that is ordered or produced (and not the lesser quantity that is actually required).If the amount of the shortage is greater than the fixed lot size, a multiple of the fixed lot size is procured. The system creates several purchase order proposals for this purpose.
fixedLotSizeQuantity
- Quantity that will be ordered or produced in the event of a shortage.public void setMaximumLotSizeQuantity(@Nullable BigDecimal maximumLotSizeQuantity)
Original property name from the Odata EDM: MaximumLotSizeQuantity
The system takes this value into account during the automatic lot size calculation for planned orders and production orders. The lot size of the individual orders cannot exceed this value.
maximumLotSizeQuantity
- Quantity that is not allowed to be exceeded during procurement.public void setMinimumLotSizeQuantity(@Nullable BigDecimal minimumLotSizeQuantity)
Original property name from the Odata EDM: MinimumLotSizeQuantity
minimumLotSizeQuantity
- Minimum procurement quantitypublic void setLotSizeRoundingQuantity(@Nullable BigDecimal lotSizeRoundingQuantity)
Original property name from the Odata EDM: LotSizeRoundingQuantity
The rounding value is used in the planning run if no rounding profile has been specified in the material master record.
lotSizeRoundingQuantity
- Value to a multiple of which the system rounds up the procurement quantity.public void setLotSizingProcedure(@Nullable String lotSizingProcedure)
Original property name from the Odata EDM: LotSizingProcedure
lotSizingProcedure
- Key that determines which lot-sizing procedure the system uses within materials planning to calculate
the quantity to be procured or produced.public void setMRPType(@Nullable String mRPType)
Original property name from the Odata EDM: MRPType
Manual reorder point planningAutomatic reorder point planningForecast-based planningMaterial requirements planning with forecasts for unplanned consumptionMaster production scheduling (MPS)Demand-driven replenishment
mRPType
- Key that determines whether and how the material is planned. You have the following options:public void setMRPResponsible(@Nullable String mRPResponsible)
Original property name from the Odata EDM: MRPResponsible
mRPResponsible
- Specifies the number of the MRP controller or group of MRP controllers responsible for material
planning for the material.public void setSafetyStockQuantity(@Nullable BigDecimal safetyStockQuantity)
Original property name from the Odata EDM: SafetyStockQuantity
The risk of shortfalls is reduced by having a safety stock.
safetyStockQuantity
- Specifies the quantity whose purpose is to satisfy unexpectedly high demand in the coverage period.public void setMinimumSafetyStockQuantity(@Nullable BigDecimal minimumSafetyStockQuantity)
Original property name from the Odata EDM: MinimumSafetyStockQuantity
Defining a lower limit can influence the following:material master data maintenanceThe safety is checked to see if it is greater or equal to this lower limit.forecastingThe lower limit is checked if you use an availability indicator which shows if the safety stock is to be calculated again in a forecast.If the safety stock is lower than this level in forecasting, the safety stock is automatically increased to the value of the lower level.The safety stock must always be greater or equal to this lower level.
minimumSafetyStockQuantity
- The quantity that defines the lower limit for safety stock. This value cannot be exceeded.public void setPlanningTimeFence(@Nullable String planningTimeFence)
Original property name from the Odata EDM: PlanningTimeFence
The planning time fence is maintained in workdays.It is only used for materials that are planned using an MRP type which includes a firming type.The firming type determines how order proposlas are to be created or scheduled within the planning time fence.
planningTimeFence
- The planning time fence specifies a period within which no automatic changes are to be made to the
master plan.public void setABCIndicator(@Nullable String aBCIndicator)
Original property name from the Odata EDM: ABCIndicator
The three indicators have the following meanings:A - important part, high consumption valueB - less important part, medium consumption valueC - relatively unimportant part, low consumption value
aBCIndicator
- Indicator that classifies a material as an A, B, or C part according to its consumption value. This
classification process is known as the ABC analysis.public void setMaximumStockQuantity(@Nullable BigDecimal maximumStockQuantity)
Original property name from the Odata EDM: MaximumStockQuantity
In materials planning, the maximum stock level is used only if you have chosen Replenish to maximum stock level as the lot-sizing procedure; that is, you have entered HB as the lot size key.Enter a value if you have chosen Replenish to maximum stock level as the lot-sizing procedure.
maximumStockQuantity
- Quantity of the material in this plant that may not be exceeded.public void setReorderThresholdQuantity(@Nullable BigDecimal reorderThresholdQuantity)
Original property name from the Odata EDM: ReorderThresholdQuantity
reorderThresholdQuantity
- If the stock falls below this quantity, the system flags the material for requirements planning by
creating a planning file entry.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.public void setSafetyDuration(@Nullable String safetyDuration)
Original property name from the Odata EDM: SafetyDuration
If you define a safety time, the requirements in MRP are brought forward on the time axis by the number of workdays you define here.This does not change the actual requirements dates. However, as the requirements have technically been brought forward, receipts are created for the earlier dates in MRP.Time-phased materials planning is based on the interval between the MRP date and the availabilty date of the next MRP date. By using the safety time/ actual range of coverage, the number of days to the interval are included in the calculation.
safetyDuration
- In this field, you define the number of workdays for the safety time/actual range of coverage.public void setPlanningStrategyGroup(@Nullable String planningStrategyGroup)
Original property name from the Odata EDM: PlanningStrategyGroup
planningStrategyGroup
- The strategy group groups all the planning strategies that can be used for a particular material. The
planning strategy represents the procedure used for planning a material and is (technically speaking)
controlled by the MRP types.public void setTotalReplenishmentLeadTime(@Nullable BigDecimal totalReplenishmentLeadTime)
Original property name from the Odata EDM: TotalReplenishmentLeadTime
This time is necessary if, for materials produced in-house, the replenishment lead time is to be taken into consideration in the availability check.In an availability check where the system takes the replenishment lead time into consideration, it only checks whether there are sufficient incoming quantities and stocks available to cover the requirements within the replenishment lead time. Outside the replenishment lead time,the system assumes that the material is available in sufficient quantity.Therefore, in this situation, it is usually necessary to depict the product's total replenishment lead time with all BOM levels as the replenishment lead time.The following options exist for materials produced in-house if the replenishment lead time is included in the availability check:The Total replenishment lead time field is maintained.In this case, the time maintained in this field is used for the availability check.The Total replenishment lead time field is not maintained.In this case, the system reads the in-house production time and, if available, the goods receipt processing time, and interprets the total of these two times as the replenishment lead time for the availability check.There is no point in maintaining the Total replenishment lead time field for materials procured externally. In external procurement, the system adds the processing time from purchasing, the planned delivery time, and the goods receipt processing time and uses this total as the replenishment lead time for an availability check with replenishment lead time.
totalReplenishmentLeadTime
- The total replenishment lead time is the time needed before the product is completely available again,
that is, after all BOM levels have been procured or produced. It is not calculated by the system, but
defined in this field as the total of the in-house production time(s) and/or the planned delivery
time(s) of the longest production path.public void setProcurementType(@Nullable String procurementType)
Original property name from the Odata EDM: ProcurementType
The material is produced in-house.The material is procured externally.The material can be both produced in-house and procured externally.
procurementType
- Indicator that defines how the material is procured. The following procurements types are possible:public void setProcurementSubType(@Nullable String procurementSubType)
Original property name from the Odata EDM: ProcurementSubType
You use special procurement when you want to be able to override the procurement type in the material master or define the procurement type more precisely.If the procurement type is in-house, you can nevertheless force the system to ignore the BOM and routing, and process the material as if it were externally procured, by specifying the special procurement as external.Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce the material in-house, it may be appropriate to choose Production in other plant.If a material has a routing but no BOM, it is treated as an externally procured material even if the procurement type is in-house. Both the BOM and the routing are ignored.However, if you specify the special procurement type as in-house, the routing is included even if the material has no BOM.
procurementSubType
- Allows you to define the procurement type more exactly. The system determines the procurement type
from the material type.public void setAssemblyScrapPercent(@Nullable BigDecimal assemblyScrapPercent)
Original property name from the Odata EDM: AssemblyScrapPercent
The assembly scrap is used in materials planning to calculate the lot size of the assembly. The system increases the quantity to be produced by the scrap quantity calculated.If the material is an assembly, specify the percentage scrap as required.If the quantity to be produced is 200 pieces and you specify an assembly scrap of 10%, you are reckoning with a scrap quantity of 20 pieces. As a result, 220 pieces are produced.The system increases the quantity to be produced for all of the assembly's components accordingly.
assemblyScrapPercent
- Percentage scrap that occurs during production of the material if the material is an assembly.public void setAvailabilityCheckType(@Nullable String availabilityCheckType)
Original property name from the Odata EDM: AvailabilityCheckType
Specifies whether and how the system checks availability and generates requirements for materials planning.In Flexible Planning, defines - together with the checking rule - the different MRP elements that make up this key figure. The sum of these elements gives the key figure.Use 1: Availability Checking and Materials PlanningThe value you enter for use 1 (see above) is a default value which defines:Which MRP elements (for example, purchase orders, reservations) the system includes in the availability checkWhether the system checks availability only until the end of the replenishment lead time or whether it checks availability over the entire period for which MRP elements existWhether the system generates individual requirements or summarized requirements if you enter sales orders or deliveries for the materialUse 2: Flexible PlanningIf you use this field to define the MRP elements of a key figure for Flexible Planning, you must also select Document KF in the Customizing parameters of the information structure.
availabilityCheckType
- This field has two uses:public void setGoodsReceiptDuration(@Nullable BigDecimal goodsReceiptDuration)
Original property name from the Odata EDM: GoodsReceiptDuration
goodsReceiptDuration
- Number of workdays required after receiving the material for inspection and placement into storage.public void setMRPGroup(@Nullable String mRPGroup)
Original property name from the Odata EDM: MRPGroup
mRPGroup
- The MRP group contains all the materials from the point of view of MRP for assigning special control
parameters for the total planning run. These control parameters include, for example, the strategy
group, the consumption mode, and the planning horizon.public void setDfltStorageLocationExtProcmt(@Nullable String dfltStorageLocationExtProcmt)
Original property name from the Odata EDM: DfltStorageLocationExtProcmt
dfltStorageLocationExtProcmt
- Key of the storage location that is proposed in the purchase requisition in materials planning for
subsequent storage of the material. In the case of a material procured externally, this storage
location is proposed in the planned order in materials planning.public void setProdRqmtsConsumptionMode(@Nullable String prodRqmtsConsumptionMode)
Original property name from the Odata EDM: ProdRqmtsConsumptionMode
In backward consumption, sales orders, dependent requirements, or material reservations consume planned independent requirements that lie before the requirements date.In forward consumption, sales orders, dependent requirements, or material reservations consume planned independent requirements that lie after the requirements date.In period-based consumption, sales orders, dependent requirements, or material reservations consume planned independent requirements that lie within the consumption period of the planned independent requirement.
prodRqmtsConsumptionMode
- The consumption mode controls the direction on the time axis in which requirements are consumed.public void setBackwardCnsmpnPeriodInWorkDays(@Nullable String backwardCnsmpnPeriodInWorkDays)
Original property name from the Odata EDM: BackwardCnsmpnPeriodInWorkDays
Using backward consumption, sales orders, dependent requirements, or Product reservations are assigned to and consume planned independent requirement quantities which lie within the consumption period and before the requirements date.
backwardCnsmpnPeriodInWorkDays
- Determines the consumption period (in workdays) for backward consumption.public void setFwdConsumptionPeriodInWorkDays(@Nullable String fwdConsumptionPeriodInWorkDays)
Original property name from the Odata EDM: FwdConsumptionPeriodInWorkDays
In forward consumption, sales orders, dependent requirements or product reservations consume planned independent requirements that lie within the consumption period after the requirements date.For the planning strategy, "make-to-stock production", this field controls the reduction of the planned independent requirements by the goods issue. In this strategy, the system first reduces the planned independent requirements that lie in the past. If you specify a period in this field, the system also reduces the planned independent requirements that lie within this period in the future.
fwdConsumptionPeriodInWorkDays
- Determines the consumption period (in workdays) for forward consumption.public void setBaseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: BaseUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
baseUnit
- Unit of measure in which stocks of the material are managed. The system converts all the quantities
you enter in other units of measure (alternative units of measure) to the base unit of measure.public void setPlanAndOrderDayDetermination(@Nullable String planAndOrderDayDetermination)
Original property name from the Odata EDM: PlanAndOrderDayDetermination
In addition to the planning cycle, you can enter a delivery cycle which is defined in the planning calendar field.It makes sense to enter a delivery cycle for the following situation:You carry out the planning run and place orders every Monday and Tuesday. The materials that are ordered on Monday are delivered on Wednesday and the materials that are ordered on Tuesday are not delivered until Friday.The system interprets an additionally specified planned delivery time as the minimum delivery time, which means that at least this number of days pass between the planning run or the order and delivery.Before a material can be planned with the time-phased planning procedure, it must be assigned the MRP type that allows time-phased planning.
planAndOrderDayDetermination
- Key that determines the day on which the material is planned and ordered.public void setRoundingProfile(@Nullable String roundingProfile)
Original property name from the Odata EDM: RoundingProfile
In Customizing, enter a threshold value from which the system should round up to the next value per deliverable unit:If the requirements value exceeds the first threshold value, the system always rounds up to the next multiple of the level foundIf the requirements value falls below the first threshold value, the system copies the original requirements value.Two other types of rounding exist:Dynamic rounding profile:These profiles are used to round up quantities to logistical units of measure (for example, layers). The contents of a logistical unit of measure does not have to be know when creating the rounding profile. It is determined by the master data from the material master.Rounding profile with quantity to be added/subtractedWith these profiles, the given quantity is changed either by adding a percentage or subtracting a percentage.Only static rounding profiles are taken into account in requirements planning. Neither dynamic rounding profiles not quantity addition/ subtraction are taken into account.A material's base unit of measure is 1 unit; the purchase order is to be delivered in layers (1 layer corresponds to 5 units) or in pallets (1 pallet corresponds to 8 layers which contains 40 units).You maintain the profile as follows:From a requirements of 2 units, the system is to round up to 5; from a requirement of 32 units, the system is to round up to 40.This results in the following order proposal quantities:Requirement from 1 -> 1 requirement from 31 -> 30Requirement from 2 -> 5 requirement from 32 -> 40Requirement from 6 -> 10 requirement from 74 -> 80Requirement from 7 -> 10If no rounding profile has been entered, the system uses the rounding value entered in the material master record for the planning run.
roundingProfile
- Key that the system uses to adjust the order proposal quantity to deliverable units.public void setLotSizeIndependentCosts(@Nullable BigDecimal lotSizeIndependentCosts)
Original property name from the Odata EDM: LotSizeIndependentCosts
The ordering costs are used only for calculating the lot size in optimum lot-sizing procedures. You must specify the ordering costs in the currency of the company code belonging to the plant.
lotSizeIndependentCosts
- Costs that are incurred, irrespective of lot size, for each purchase order or production order over
and above the purchase order price or production costs.public void setMRPPlanningCalendar(@Nullable String mRPPlanningCalendar)
Original property name from the Odata EDM: MRPPlanningCalendar
mRPPlanningCalendar
- Three character number (numeric or using letters) that specifically identifies a PPS-planning
calendar.public void setRangeOfCvrgPrflCode(@Nullable String rangeOfCvrgPrflCode)
Original property name from the Odata EDM: RangeOfCvrgPrflCode
rangeOfCvrgPrflCode
- The range of coverage profile contains the parameters for calculating the dynamic safety stock. This
is a statistical calculation on the basis of average daily requirements.public void setIsSafetyTime(@Nullable String isSafetyTime)
Original property name from the Odata EDM: IsSafetyTime
If you define a safety time, the requirements in MRP are brought forward on the time axis by the number of workdays you define here. The actual range of coverage corresponds to the number of days, by which the requirements are brought forward.Using this indicator you can activate the safety time and you can set whether all requirements or only independent requirements (sales order, planned independent requirements, and so on) are to be brought forward.The actual requirements dates are not changed.
isSafetyTime
- You use this indicator to switch on the safety time actual range of coverage for a material in MRP.public void setPerdPrflForSftyTme(@Nullable String perdPrflForSftyTme)
Original property name from the Odata EDM: PerdPrflForSftyTme
In order to smooth out seasonal fluctuations, for any definable period you can define a safety time/actual range of coverage that varies from what you have maintained in the material master in the field safety time/actual range of coverage. If, for example, a higher actual range of coverage than usual is required due to higher demand during the Christmas period, you can define the period with the desired actual range of coverage in the period profile.You can also use the period profile to represent a safety time of less than one day. You do this by entering a safety time % in addition to the safety time.
perdPrflForSftyTme
- The period profile for the safety time / actual range of coverage contains the periods (stating
to/from date) with the safety time/actual range of coverage that is valid for each period.public void setIsMRPDependentRqmt(@Nullable String isMRPDependentRqmt)
Original property name from the Odata EDM: IsMRPDependentRqmt
You only use this indicator in connection with planning strategies for make-to-stock production, assembly planning. Note that the indicator Dependent requirements not relevant to MRP should only be used when, for example, planned independent requirements exist for an assembly. In this case, no receipt elements for the dependent requirements in MRP should be created as receipts have already been created for the planned independent requirements.
isMRPDependentRqmt
- This indicator controls whether dependent requirements are relevant to MRP or not. Dependent
requirements include dependent reservations and stock transfer requirements.public void setInHouseProductionTime(@Nullable BigDecimal inHouseProductionTime)
Original property name from the Odata EDM: InHouseProductionTime
In-house production time is independent of the order quantity.
inHouseProductionTime
- Specifies the time in workdays needed to produce the material in-house.public void setProductIsForCrossProject(@Nullable String productIsForCrossProject)
Original property name from the Odata EDM: ProductIsForCrossProject
productIsForCrossProject
- The indicator determines if the system takes all stock and MRP-relevant units (inward/outward
movement) in the project stock segments for all documents without account assignment into
consideration.public void setStorageCostsPercentageCode(@Nullable String storageCostsPercentageCode)
Original property name from the Odata EDM: StorageCostsPercentageCode
The storage costs percentage is based on the quantity stored and the unit price, and refers to the average value of the materials stored.The percentage is considered constant for the stocking-up period. It normally lies between 15 and 35%.The storage costs percentage is used by optimizing lot-sizing procedures to calculate the lot size, but not for any other purpose.
storageCostsPercentageCode
- Indicator that specifies the storage costs percentage the system uses when calculating the lot size to
determine storage costs.public void setSrvcLvl(@Nullable BigDecimal srvcLvl)
Original property name from the Odata EDM: SrvcLvl
The system uses the service level to calculate the safety stock.The higher the service level, the higher will be the safety stock calculated by the system to compensate for additional consumption or delays in delivery.
srvcLvl
- Percentage specifying what proportion of the requirement is to be covered by the warehouse stock.public void setMRPAvailabilityType(@Nullable String mRPAvailabilityType)
Original property name from the Odata EDM: MRPAvailabilityType
Subassembly planning with final assemblyGross requirements planningSubassembly planning without final assembly
mRPAvailabilityType
- Defines whether the material is available for:public void setFollowUpProduct(@Nullable String followUpProduct)
Original property name from the Odata EDM: FollowUpProduct
In the material master record and also in the bill of material (BOM), you can define a follow-up material for a material to be discontinued. The follow-up material defined in the BOM has a higher priority than that in the material master record.You must always specify a follow-up material in the material master record for the system to know a follow-up material if none has been specified in the BOM.Simple discontinuationA component to be discontinued is replaced with a follow-up component at a particular date.In the material master record of the component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date.Dependent parallel discontinuationA group of materials is replaced with a group of materials; that is, if one component is to be discontinued (the main component), another component must also be discontinued (the subordinate component).In the material master record of the main component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date. In the material master record of the subordinate component, you must set discontinuation indicator 3.
followUpProduct
- Number of the material that the system uses in materials planning to replace the material to be
discontinued once its warehouse stock is depleted.public void setRepetitiveManufacturingIsAllwd(@Nullable Boolean repetitiveManufacturingIsAllwd)
Original property name from the Odata EDM: RepetitiveManufacturingIsAllwd
You can only backflush in repetitive manufacturing if you have set this indicator.If you set this indicator, you must also specify a repetitive manufacturing profile for this material.
repetitiveManufacturingIsAllwd
- Authorizes the material for repetitive manufacturing.public void setDependentRequirementsType(@Nullable String dependentRequirementsType)
Original property name from the Odata EDM: DependentRequirementsType
Individual requirementsRequirement quantities of the dependent material are stated individually.Collective requirementsRequirement quantities of the dependent material are grouped together.You can maintain this indicator in the following places:In the material master recordFor the explosion type of the BOM item (in Customizing for Basic Data in Define Explosion Types)The setting for the explosion type overrides that in the material master record.If the material is assigned to a material type that does not allow quantity-based inventory management in this plant, you can set the indicator to individual requirements only.If the stock is to be managed in sales order stock or project stock, the indicator must be set to one of the following options:Individual and collective requirementsIndividual requirements onlyIf a material managed in project stock is to be procured from another plant using a cross-company-code stock transport order, the indicator must be set to 2 (collective requirements) in the issuing plant because, in this specific context, individual project stock management is not possible in both plants.
dependentRequirementsType
- Indicator determining whether the following requirements are allowed for the dependent requirements of
the material:public void setIsBulkMaterialComponent(@Nullable Boolean isBulkMaterialComponent)
Original property name from the Odata EDM: IsBulkMaterialComponent
The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
isBulkMaterialComponent
- This indicator defines a BOM item as a bulk material, which is available directly at the work center
(for example, washers or grease).public void setRepetitiveManufacturingProfile(@Nullable String repetitiveManufacturingProfile)
Original property name from the Odata EDM: RepetitiveManufacturingProfile
The repetitive manufacturing profile also determines;how the system deals with activities when backflushingwhich movement type is used to post goods receipts and goods issueshow planned order and run schedule quantities are reduced in the backflush transactionhow BOM corrections are made - if errors should occur when posting quantities to be backflushed
repetitiveManufacturingProfile
- Controls, via order type, whether you are working with make-to-order repetitive manufacturing, based
on sales orders, or with make-to-stock repetitive manufacturing, based on no specific orders.public void setRqmtQtyRcptTaktTmeInWrkgDays(@Nullable BigDecimal rqmtQtyRcptTaktTmeInWrkgDays)
Original property name from the Odata EDM: RqmtQtyRcptTaktTmeInWrkgDays
You enter the takt time in workdays.The system uses the takt time if a requirement is covered by several receipt elements due to restrictions on lot size such as maximum lot size (with all lot-sizing procedures) or rounding value (with fixed lot size with splitting).
rqmtQtyRcptTaktTmeInWrkgDays
- If a requirement quantity (for example, for capacity reasons) cannot be procured in a single lot, you
have to schedule several receipts. In conjunction with the overlap indicator in the lot size, you can
use the takt time to specify that these receipts are offset, that is, that they are delayed by the
takt time.public void setForecastRequirementsAreSplit(@Nullable String forecastRequirementsAreSplit)
Original property name from the Odata EDM: ForecastRequirementsAreSplit
If you enter a splitting indicator, the system will take only a limited number of periods into account when planning the material and split them into smaller time intervals.If you choose "day" as your splitting indicator, the system will spread forecast requirements minus actual consumption values over the remaining workdays in the month.
forecastRequirementsAreSplit
- Indicator that defines how the system splits forecast requirements into smaller time intervals where
the MRP type is forecast-based planning and the period indicator is not "day".public void setEffectiveOutDate(@Nullable LocalDateTime effectiveOutDate)
Original property name from the Odata EDM: EffectiveOutDate
From this date, the system reassigns the dependent requirements that are no longer covered by warehouse stock of the discontinued material to the follow-up material. This is done as part of material requirements planning.Enter a date if you want to plan the discontinuation of a material for the long term.
effectiveOutDate
- Date from which the stocks of the material are to be used up. As soon as no more stock exists for this
material, it is to be replaced by the follow-up material.public void setMRPProfile(@Nullable String mRPProfile)
Original property name from the Odata EDM: MRPProfile
In an MRP profile, you definewhich fields are filled with values when MRP data is entered in the material master record,which values these fields have,which of these values can be overwritten and which not.The information stored in a profile is standard information that is needed again and again in similar constellations when material master records are maintained. Thus the MRP profile is a useful entry aid and makes it easier to manage MRP data.
mRPProfile
- Key that you can use to store MRP parameters that are independent of the material master record.public void setComponentScrapInPercent(@Nullable BigDecimal componentScrapInPercent)
Original property name from the Odata EDM: ComponentScrapInPercent
Component scrap is used in material requirements planning (MRP) to determine the quantities of components required. When exploding the bill of material (BOM), the system increases the required quantities of the components by the calculated scrap quantity.ExampleRequired quantity 200 piecesComponent scrap 10%Scrap quantity 20 piecesTherefore, 220 pieces are required.For examples of calculation in connection with the indicator for net scrap, see the documentation for this indicator.If there is also assembly scrap for a higher-level assembly, the system adds together the two types of scrap.If component scrap has been entered in the BOM, this value applies. Otherwise, the value specified in the material master record is used.
componentScrapInPercent
- Percentage of scrap that occurs during production of the material if the material is a component.public void setProductIsToBeDiscontinued(@Nullable String productIsToBeDiscontinued)
Original property name from the Odata EDM: ProductIsToBeDiscontinued
If this indicator is set, the system transfers the dependent requirements in materials planning to the follow-up material if they are no longer covered by warehouse stocks. However, this requires:The part to be discontinued and the follow-up material to be planned using material requirements planning (MRP)The base unit of measure of the follow-up material to be the same as that of the part to be discontinuedNoteIn subcontracting, uncovered requirements are not switched to the follow-up material after the effective-out date. This is indicated by a corresponding exception message (58) in the MRP list.
productIsToBeDiscontinued
- Identifies the material as a part to be discontinued and includes it in the discontinued parts
procedure in materials planning.public void setProdRqmtsAreConsolidated(@Nullable String prodRqmtsAreConsolidated)
Original property name from the Odata EDM: ProdRqmtsAreConsolidated
If you set this indicator, the display in the MRP list and stock/requirements list is preset as follows:If several dependent requirements are scheduled on one day, they are grouped together in a single line showing how many dependent requirements have been grouped together.You can also expand the grouping in the MRP list and in the stock/requirements list.Defines whether additional individual/dependent requirements are written for components whose assembly is set such that total dependent requirements are created.
prodRqmtsAreConsolidated
- Defines whether the system groups together dependent requirements for the material on a daily basis
when analyzing requirements planning.public void setMatlCompIsMarkedForBackflush(@Nullable String matlCompIsMarkedForBackflush)
Original property name from the Odata EDM: MatlCompIsMarkedForBackflush
In the routing, the backflush indicator is set in the component assignment.In the material master record, the backflush indicator is set to "Always Backflush".In the material master record, the backflush indicator is set to "Work Center Decides", and the indicator is set in the work center.Each material component is assigned to an operation in the production order. If a material component is backflushed, the system posts the withdrawal only upon confirmation of the operation. The withdrawal is then posted automatically.
matlCompIsMarkedForBackflush
- Determines whether the backflush indicator is set in the production order. Here, a 3-level hierarchy
logic is applied:public void setProposedProductSupplyArea(@Nullable String proposedProductSupplyArea)
Original property name from the Odata EDM: ProposedProductSupplyArea
The proposed supply area is mainly used for KANBAN materials that are only or usually provided at one supply area in a plant. Here, this supply area can be easily saved in the system.The proposed supply area is used, for example, to determine the supply area for the dependent requirements of a material.The supply area in the dependent requirements of a material is required:to enable the system to calculate the KANBAN control cycles automaticallyto enable you to select requirements in the pull list with reference to a supply area
proposedProductSupplyArea
- The supply area is used as an interim storage area on the shop floor which is used to provide
materials directly at the production line.public void setCurrency(@Nullable String currency)
Original property name from the Odata EDM: Currency
currency
- Currency key for amounts in the system.public void setPlannedOrderActionControl(@Nullable String plannedOrderActionControl)
Original property name from the Odata EDM: PlannedOrderActionControl
Using the function, "actions in the planned order", an interface is provided to external assembly control systems. Thus, work progress on the assembly line as well as activities independent of the assembly line can be transferred to the SAP System via a standard interface or a customized interface.Using this function, one or more actions can be carried out for a large number of planned orders in one step that, if carried out online, could only be carried out individually per planned order. Moreover, it is possible to carry out customer-specific actions.An action may be, for example;explode BOMcheck material availabilityschedule planned order, and so on...
plannedOrderActionControl
- This key is used for the function "Actions in the planned order" and defines the sequence of the
actions that can be carried out for the planned order.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<ProductSupplyPlanning>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<ProductSupplyPlanning>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<ProductSupplyPlanning>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<ProductSupplyPlanning>
@Nonnull public static <T> ProductSupplyPlanningField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.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> ProductSupplyPlanningField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<ProductSupplyPlanning>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<ProductSupplyPlanning>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<ProductSupplyPlanning>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntity
getDefaultServicePath
in class VdmEntity<ProductSupplyPlanning>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull public static ProductSupplyPlanning.ProductSupplyPlanningBuilder builder()
@Nullable public String getProduct()
Original property name from the Odata EDM: Product
@Nullable public String getPlant()
Original property name from the Odata EDM: Plant
@Nullable public BigDecimal getFixedLotSizeQuantity()
Original property name from the Odata EDM: FixedLotSizeQuantity
If the amount of the shortage is less than the fixed lot size, it is the fixed lot size that is ordered or produced (and not the lesser quantity that is actually required).If the amount of the shortage is greater than the fixed lot size, a multiple of the fixed lot size is procured. The system creates several purchase order proposals for this purpose.
@Nullable public BigDecimal getMaximumLotSizeQuantity()
Original property name from the Odata EDM: MaximumLotSizeQuantity
The system takes this value into account during the automatic lot size calculation for planned orders and production orders. The lot size of the individual orders cannot exceed this value.
@Nullable public BigDecimal getMinimumLotSizeQuantity()
Original property name from the Odata EDM: MinimumLotSizeQuantity
@Nullable public BigDecimal getLotSizeRoundingQuantity()
Original property name from the Odata EDM: LotSizeRoundingQuantity
The rounding value is used in the planning run if no rounding profile has been specified in the material master record.
@Nullable public String getLotSizingProcedure()
Original property name from the Odata EDM: LotSizingProcedure
@Nullable public String getMRPType()
Original property name from the Odata EDM: MRPType
Manual reorder point planningAutomatic reorder point planningForecast-based planningMaterial requirements planning with forecasts for unplanned consumptionMaster production scheduling (MPS)Demand-driven replenishment
@Nullable public String getMRPResponsible()
Original property name from the Odata EDM: MRPResponsible
@Nullable public BigDecimal getSafetyStockQuantity()
Original property name from the Odata EDM: SafetyStockQuantity
The risk of shortfalls is reduced by having a safety stock.
@Nullable public BigDecimal getMinimumSafetyStockQuantity()
Original property name from the Odata EDM: MinimumSafetyStockQuantity
Defining a lower limit can influence the following:material master data maintenanceThe safety is checked to see if it is greater or equal to this lower limit.forecastingThe lower limit is checked if you use an availability indicator which shows if the safety stock is to be calculated again in a forecast.If the safety stock is lower than this level in forecasting, the safety stock is automatically increased to the value of the lower level.The safety stock must always be greater or equal to this lower level.
@Nullable public String getPlanningTimeFence()
Original property name from the Odata EDM: PlanningTimeFence
The planning time fence is maintained in workdays.It is only used for materials that are planned using an MRP type which includes a firming type.The firming type determines how order proposlas are to be created or scheduled within the planning time fence.
@Nullable public String getABCIndicator()
Original property name from the Odata EDM: ABCIndicator
The three indicators have the following meanings:A - important part, high consumption valueB - less important part, medium consumption valueC - relatively unimportant part, low consumption value
@Nullable public BigDecimal getMaximumStockQuantity()
Original property name from the Odata EDM: MaximumStockQuantity
In materials planning, the maximum stock level is used only if you have chosen Replenish to maximum stock level as the lot-sizing procedure; that is, you have entered HB as the lot size key.Enter a value if you have chosen Replenish to maximum stock level as the lot-sizing procedure.
@Nullable public BigDecimal getReorderThresholdQuantity()
Original property name from the Odata EDM: ReorderThresholdQuantity
@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 String getSafetyDuration()
Original property name from the Odata EDM: SafetyDuration
If you define a safety time, the requirements in MRP are brought forward on the time axis by the number of workdays you define here.This does not change the actual requirements dates. However, as the requirements have technically been brought forward, receipts are created for the earlier dates in MRP.Time-phased materials planning is based on the interval between the MRP date and the availabilty date of the next MRP date. By using the safety time/ actual range of coverage, the number of days to the interval are included in the calculation.
@Nullable public String getPlanningStrategyGroup()
Original property name from the Odata EDM: PlanningStrategyGroup
@Nullable public BigDecimal getTotalReplenishmentLeadTime()
Original property name from the Odata EDM: TotalReplenishmentLeadTime
This time is necessary if, for materials produced in-house, the replenishment lead time is to be taken into consideration in the availability check.In an availability check where the system takes the replenishment lead time into consideration, it only checks whether there are sufficient incoming quantities and stocks available to cover the requirements within the replenishment lead time. Outside the replenishment lead time,the system assumes that the material is available in sufficient quantity.Therefore, in this situation, it is usually necessary to depict the product's total replenishment lead time with all BOM levels as the replenishment lead time.The following options exist for materials produced in-house if the replenishment lead time is included in the availability check:The Total replenishment lead time field is maintained.In this case, the time maintained in this field is used for the availability check.The Total replenishment lead time field is not maintained.In this case, the system reads the in-house production time and, if available, the goods receipt processing time, and interprets the total of these two times as the replenishment lead time for the availability check.There is no point in maintaining the Total replenishment lead time field for materials procured externally. In external procurement, the system adds the processing time from purchasing, the planned delivery time, and the goods receipt processing time and uses this total as the replenishment lead time for an availability check with replenishment lead time.
@Nullable public String getProcurementType()
Original property name from the Odata EDM: ProcurementType
The material is produced in-house.The material is procured externally.The material can be both produced in-house and procured externally.
@Nullable public String getProcurementSubType()
Original property name from the Odata EDM: ProcurementSubType
You use special procurement when you want to be able to override the procurement type in the material master or define the procurement type more precisely.If the procurement type is in-house, you can nevertheless force the system to ignore the BOM and routing, and process the material as if it were externally procured, by specifying the special procurement as external.Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce the material in-house, it may be appropriate to choose Production in other plant.If a material has a routing but no BOM, it is treated as an externally procured material even if the procurement type is in-house. Both the BOM and the routing are ignored.However, if you specify the special procurement type as in-house, the routing is included even if the material has no BOM.
@Nullable public BigDecimal getAssemblyScrapPercent()
Original property name from the Odata EDM: AssemblyScrapPercent
The assembly scrap is used in materials planning to calculate the lot size of the assembly. The system increases the quantity to be produced by the scrap quantity calculated.If the material is an assembly, specify the percentage scrap as required.If the quantity to be produced is 200 pieces and you specify an assembly scrap of 10%, you are reckoning with a scrap quantity of 20 pieces. As a result, 220 pieces are produced.The system increases the quantity to be produced for all of the assembly's components accordingly.
@Nullable public String getAvailabilityCheckType()
Original property name from the Odata EDM: AvailabilityCheckType
Specifies whether and how the system checks availability and generates requirements for materials planning.In Flexible Planning, defines - together with the checking rule - the different MRP elements that make up this key figure. The sum of these elements gives the key figure.Use 1: Availability Checking and Materials PlanningThe value you enter for use 1 (see above) is a default value which defines:Which MRP elements (for example, purchase orders, reservations) the system includes in the availability checkWhether the system checks availability only until the end of the replenishment lead time or whether it checks availability over the entire period for which MRP elements existWhether the system generates individual requirements or summarized requirements if you enter sales orders or deliveries for the materialUse 2: Flexible PlanningIf you use this field to define the MRP elements of a key figure for Flexible Planning, you must also select Document KF in the Customizing parameters of the information structure.
@Nullable public BigDecimal getGoodsReceiptDuration()
Original property name from the Odata EDM: GoodsReceiptDuration
@Nullable public String getMRPGroup()
Original property name from the Odata EDM: MRPGroup
@Nullable public String getDfltStorageLocationExtProcmt()
Original property name from the Odata EDM: DfltStorageLocationExtProcmt
@Nullable public String getProdRqmtsConsumptionMode()
Original property name from the Odata EDM: ProdRqmtsConsumptionMode
In backward consumption, sales orders, dependent requirements, or material reservations consume planned independent requirements that lie before the requirements date.In forward consumption, sales orders, dependent requirements, or material reservations consume planned independent requirements that lie after the requirements date.In period-based consumption, sales orders, dependent requirements, or material reservations consume planned independent requirements that lie within the consumption period of the planned independent requirement.
@Nullable public String getBackwardCnsmpnPeriodInWorkDays()
Original property name from the Odata EDM: BackwardCnsmpnPeriodInWorkDays
Using backward consumption, sales orders, dependent requirements, or Product reservations are assigned to and consume planned independent requirement quantities which lie within the consumption period and before the requirements date.
@Nullable public String getFwdConsumptionPeriodInWorkDays()
Original property name from the Odata EDM: FwdConsumptionPeriodInWorkDays
In forward consumption, sales orders, dependent requirements or product reservations consume planned independent requirements that lie within the consumption period after the requirements date.For the planning strategy, "make-to-stock production", this field controls the reduction of the planned independent requirements by the goods issue. In this strategy, the system first reduces the planned independent requirements that lie in the past. If you specify a period in this field, the system also reduces the planned independent requirements that lie within this period in the future.
@Nullable public String getBaseUnit()
Original property name from the Odata EDM: BaseUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
@Nullable public String getPlanAndOrderDayDetermination()
Original property name from the Odata EDM: PlanAndOrderDayDetermination
In addition to the planning cycle, you can enter a delivery cycle which is defined in the planning calendar field.It makes sense to enter a delivery cycle for the following situation:You carry out the planning run and place orders every Monday and Tuesday. The materials that are ordered on Monday are delivered on Wednesday and the materials that are ordered on Tuesday are not delivered until Friday.The system interprets an additionally specified planned delivery time as the minimum delivery time, which means that at least this number of days pass between the planning run or the order and delivery.Before a material can be planned with the time-phased planning procedure, it must be assigned the MRP type that allows time-phased planning.
@Nullable public String getRoundingProfile()
Original property name from the Odata EDM: RoundingProfile
In Customizing, enter a threshold value from which the system should round up to the next value per deliverable unit:If the requirements value exceeds the first threshold value, the system always rounds up to the next multiple of the level foundIf the requirements value falls below the first threshold value, the system copies the original requirements value.Two other types of rounding exist:Dynamic rounding profile:These profiles are used to round up quantities to logistical units of measure (for example, layers). The contents of a logistical unit of measure does not have to be know when creating the rounding profile. It is determined by the master data from the material master.Rounding profile with quantity to be added/subtractedWith these profiles, the given quantity is changed either by adding a percentage or subtracting a percentage.Only static rounding profiles are taken into account in requirements planning. Neither dynamic rounding profiles not quantity addition/ subtraction are taken into account.A material's base unit of measure is 1 unit; the purchase order is to be delivered in layers (1 layer corresponds to 5 units) or in pallets (1 pallet corresponds to 8 layers which contains 40 units).You maintain the profile as follows:From a requirements of 2 units, the system is to round up to 5; from a requirement of 32 units, the system is to round up to 40.This results in the following order proposal quantities:Requirement from 1 -> 1 requirement from 31 -> 30Requirement from 2 -> 5 requirement from 32 -> 40Requirement from 6 -> 10 requirement from 74 -> 80Requirement from 7 -> 10If no rounding profile has been entered, the system uses the rounding value entered in the material master record for the planning run.
@Nullable public BigDecimal getLotSizeIndependentCosts()
Original property name from the Odata EDM: LotSizeIndependentCosts
The ordering costs are used only for calculating the lot size in optimum lot-sizing procedures. You must specify the ordering costs in the currency of the company code belonging to the plant.
@Nullable public String getMRPPlanningCalendar()
Original property name from the Odata EDM: MRPPlanningCalendar
@Nullable public String getRangeOfCvrgPrflCode()
Original property name from the Odata EDM: RangeOfCvrgPrflCode
@Nullable public String getIsSafetyTime()
Original property name from the Odata EDM: IsSafetyTime
If you define a safety time, the requirements in MRP are brought forward on the time axis by the number of workdays you define here. The actual range of coverage corresponds to the number of days, by which the requirements are brought forward.Using this indicator you can activate the safety time and you can set whether all requirements or only independent requirements (sales order, planned independent requirements, and so on) are to be brought forward.The actual requirements dates are not changed.
@Nullable public String getPerdPrflForSftyTme()
Original property name from the Odata EDM: PerdPrflForSftyTme
In order to smooth out seasonal fluctuations, for any definable period you can define a safety time/actual range of coverage that varies from what you have maintained in the material master in the field safety time/actual range of coverage. If, for example, a higher actual range of coverage than usual is required due to higher demand during the Christmas period, you can define the period with the desired actual range of coverage in the period profile.You can also use the period profile to represent a safety time of less than one day. You do this by entering a safety time % in addition to the safety time.
@Nullable public String getIsMRPDependentRqmt()
Original property name from the Odata EDM: IsMRPDependentRqmt
You only use this indicator in connection with planning strategies for make-to-stock production, assembly planning. Note that the indicator Dependent requirements not relevant to MRP should only be used when, for example, planned independent requirements exist for an assembly. In this case, no receipt elements for the dependent requirements in MRP should be created as receipts have already been created for the planned independent requirements.
@Nullable public BigDecimal getInHouseProductionTime()
Original property name from the Odata EDM: InHouseProductionTime
In-house production time is independent of the order quantity.
@Nullable public String getProductIsForCrossProject()
Original property name from the Odata EDM: ProductIsForCrossProject
@Nullable public String getStorageCostsPercentageCode()
Original property name from the Odata EDM: StorageCostsPercentageCode
The storage costs percentage is based on the quantity stored and the unit price, and refers to the average value of the materials stored.The percentage is considered constant for the stocking-up period. It normally lies between 15 and 35%.The storage costs percentage is used by optimizing lot-sizing procedures to calculate the lot size, but not for any other purpose.
@Nullable public BigDecimal getSrvcLvl()
Original property name from the Odata EDM: SrvcLvl
The system uses the service level to calculate the safety stock.The higher the service level, the higher will be the safety stock calculated by the system to compensate for additional consumption or delays in delivery.
@Nullable public String getMRPAvailabilityType()
Original property name from the Odata EDM: MRPAvailabilityType
Subassembly planning with final assemblyGross requirements planningSubassembly planning without final assembly
@Nullable public String getFollowUpProduct()
Original property name from the Odata EDM: FollowUpProduct
In the material master record and also in the bill of material (BOM), you can define a follow-up material for a material to be discontinued. The follow-up material defined in the BOM has a higher priority than that in the material master record.You must always specify a follow-up material in the material master record for the system to know a follow-up material if none has been specified in the BOM.Simple discontinuationA component to be discontinued is replaced with a follow-up component at a particular date.In the material master record of the component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date.Dependent parallel discontinuationA group of materials is replaced with a group of materials; that is, if one component is to be discontinued (the main component), another component must also be discontinued (the subordinate component).In the material master record of the main component to be discontinued, you must set discontinuation indicator 1, enter a follow-up component, and specify an effective-out date. In the material master record of the subordinate component, you must set discontinuation indicator 3.
@Nullable public Boolean getRepetitiveManufacturingIsAllwd()
Original property name from the Odata EDM: RepetitiveManufacturingIsAllwd
You can only backflush in repetitive manufacturing if you have set this indicator.If you set this indicator, you must also specify a repetitive manufacturing profile for this material.
@Nullable public String getDependentRequirementsType()
Original property name from the Odata EDM: DependentRequirementsType
Individual requirementsRequirement quantities of the dependent material are stated individually.Collective requirementsRequirement quantities of the dependent material are grouped together.You can maintain this indicator in the following places:In the material master recordFor the explosion type of the BOM item (in Customizing for Basic Data in Define Explosion Types)The setting for the explosion type overrides that in the material master record.If the material is assigned to a material type that does not allow quantity-based inventory management in this plant, you can set the indicator to individual requirements only.If the stock is to be managed in sales order stock or project stock, the indicator must be set to one of the following options:Individual and collective requirementsIndividual requirements onlyIf a material managed in project stock is to be procured from another plant using a cross-company-code stock transport order, the indicator must be set to 2 (collective requirements) in the issuing plant because, in this specific context, individual project stock management is not possible in both plants.
@Nullable public Boolean getIsBulkMaterialComponent()
Original property name from the Odata EDM: IsBulkMaterialComponent
The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
@Nullable public String getRepetitiveManufacturingProfile()
Original property name from the Odata EDM: RepetitiveManufacturingProfile
The repetitive manufacturing profile also determines;how the system deals with activities when backflushingwhich movement type is used to post goods receipts and goods issueshow planned order and run schedule quantities are reduced in the backflush transactionhow BOM corrections are made - if errors should occur when posting quantities to be backflushed
@Nullable public BigDecimal getRqmtQtyRcptTaktTmeInWrkgDays()
Original property name from the Odata EDM: RqmtQtyRcptTaktTmeInWrkgDays
You enter the takt time in workdays.The system uses the takt time if a requirement is covered by several receipt elements due to restrictions on lot size such as maximum lot size (with all lot-sizing procedures) or rounding value (with fixed lot size with splitting).
@Nullable public String getForecastRequirementsAreSplit()
Original property name from the Odata EDM: ForecastRequirementsAreSplit
If you enter a splitting indicator, the system will take only a limited number of periods into account when planning the material and split them into smaller time intervals.If you choose "day" as your splitting indicator, the system will spread forecast requirements minus actual consumption values over the remaining workdays in the month.
@Nullable public LocalDateTime getEffectiveOutDate()
Original property name from the Odata EDM: EffectiveOutDate
From this date, the system reassigns the dependent requirements that are no longer covered by warehouse stock of the discontinued material to the follow-up material. This is done as part of material requirements planning.Enter a date if you want to plan the discontinuation of a material for the long term.
@Nullable public String getMRPProfile()
Original property name from the Odata EDM: MRPProfile
In an MRP profile, you definewhich fields are filled with values when MRP data is entered in the material master record,which values these fields have,which of these values can be overwritten and which not.The information stored in a profile is standard information that is needed again and again in similar constellations when material master records are maintained. Thus the MRP profile is a useful entry aid and makes it easier to manage MRP data.
@Nullable public BigDecimal getComponentScrapInPercent()
Original property name from the Odata EDM: ComponentScrapInPercent
Component scrap is used in material requirements planning (MRP) to determine the quantities of components required. When exploding the bill of material (BOM), the system increases the required quantities of the components by the calculated scrap quantity.ExampleRequired quantity 200 piecesComponent scrap 10%Scrap quantity 20 piecesTherefore, 220 pieces are required.For examples of calculation in connection with the indicator for net scrap, see the documentation for this indicator.If there is also assembly scrap for a higher-level assembly, the system adds together the two types of scrap.If component scrap has been entered in the BOM, this value applies. Otherwise, the value specified in the material master record is used.
@Nullable public String getProductIsToBeDiscontinued()
Original property name from the Odata EDM: ProductIsToBeDiscontinued
If this indicator is set, the system transfers the dependent requirements in materials planning to the follow-up material if they are no longer covered by warehouse stocks. However, this requires:The part to be discontinued and the follow-up material to be planned using material requirements planning (MRP)The base unit of measure of the follow-up material to be the same as that of the part to be discontinuedNoteIn subcontracting, uncovered requirements are not switched to the follow-up material after the effective-out date. This is indicated by a corresponding exception message (58) in the MRP list.
@Nullable public String getProdRqmtsAreConsolidated()
Original property name from the Odata EDM: ProdRqmtsAreConsolidated
If you set this indicator, the display in the MRP list and stock/requirements list is preset as follows:If several dependent requirements are scheduled on one day, they are grouped together in a single line showing how many dependent requirements have been grouped together.You can also expand the grouping in the MRP list and in the stock/requirements list.Defines whether additional individual/dependent requirements are written for components whose assembly is set such that total dependent requirements are created.
@Nullable public String getMatlCompIsMarkedForBackflush()
Original property name from the Odata EDM: MatlCompIsMarkedForBackflush
In the routing, the backflush indicator is set in the component assignment.In the material master record, the backflush indicator is set to "Always Backflush".In the material master record, the backflush indicator is set to "Work Center Decides", and the indicator is set in the work center.Each material component is assigned to an operation in the production order. If a material component is backflushed, the system posts the withdrawal only upon confirmation of the operation. The withdrawal is then posted automatically.
@Nullable public String getProposedProductSupplyArea()
Original property name from the Odata EDM: ProposedProductSupplyArea
The proposed supply area is mainly used for KANBAN materials that are only or usually provided at one supply area in a plant. Here, this supply area can be easily saved in the system.The proposed supply area is used, for example, to determine the supply area for the dependent requirements of a material.The supply area in the dependent requirements of a material is required:to enable the system to calculate the KANBAN control cycles automaticallyto enable you to select requirements in the pull list with reference to a supply area
@Nullable public String getCurrency()
Original property name from the Odata EDM: Currency
@Nullable public String getPlannedOrderActionControl()
Original property name from the Odata EDM: PlannedOrderActionControl
Using the function, "actions in the planned order", an interface is provided to external assembly control systems. Thus, work progress on the assembly line as well as activities independent of the assembly line can be transferred to the SAP System via a standard interface or a customized interface.Using this function, one or more actions can be carried out for a large number of planned orders in one step that, if carried out online, could only be carried out individually per planned order. Moreover, it is possible to carry out customer-specific actions.An action may be, for example;explode BOMcheck material availabilityschedule planned order, and so on...
@Nonnull public String toString()
toString
in class VdmObject<ProductSupplyPlanning>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<ProductSupplyPlanning>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<ProductSupplyPlanning>
public int hashCode()
hashCode
in class VdmObject<ProductSupplyPlanning>
Copyright © 2021 SAP SE. All rights reserved.