public static class ProductSupplyPlanning.ProductSupplyPlanningBuilder extends Object
@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder product(@Nullable String product)
Original property name from the Odata EDM: Product
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder fixedLotSizeQuantity(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder maximumLotSizeQuantity(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder minimumLotSizeQuantity(@Nullable BigDecimal minimumLotSizeQuantity)
Original property name from the Odata EDM: MinimumLotSizeQuantity
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder lotSizeRoundingQuantity(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder lotSizingProcedure(@Nullable String lotSizingProcedure)
Original property name from the Odata EDM: LotSizingProcedure
quantity to be procured or produced.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder mRPType(@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
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder mRPResponsible(@Nullable String mRPResponsible)
Original property name from the Odata EDM: MRPResponsible
for the material.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder safetyStockQuantity(@Nullable BigDecimal safetyStockQuantity)
Original property name from the Odata EDM: SafetyStockQuantity
The risk of shortfalls is reduced by having a safety stock.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder minimumSafetyStockQuantity(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder planningTimeFence(@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.
plan.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder aBCIndicator(@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
classification process is known as the ABC analysis.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder maximumStockQuantity(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder reorderThresholdQuantity(@Nullable BigDecimal reorderThresholdQuantity)
Original property name from the Odata EDM: ReorderThresholdQuantity
creating a planning file entry.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder plannedDeliveryDurationInDays(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder safetyDuration(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder planningStrategyGroup(@Nullable String planningStrategyGroup)
Original property name from the Odata EDM: PlanningStrategyGroup
planning strategy represents the procedure used for planning a material and is (technically speaking) controlled by the MRP types.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder totalReplenishmentLeadTime(@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.
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.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder procurementType(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder procurementSubType(@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.
the material type.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder assemblyScrapPercent(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder availabilityCheckType(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder goodsReceiptDuration(@Nullable BigDecimal goodsReceiptDuration)
Original property name from the Odata EDM: GoodsReceiptDuration
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder mRPGroup(@Nullable String mRPGroup)
Original property name from the Odata EDM: MRPGroup
parameters for the total planning run. These control parameters include, for example, the strategy group, the consumption mode, and the planning horizon.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder dfltStorageLocationExtProcmt(@Nullable String dfltStorageLocationExtProcmt)
Original property name from the Odata EDM: DfltStorageLocationExtProcmt
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.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder prodRqmtsConsumptionMode(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder backwardCnsmpnPeriodInWorkDays(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder fwdConsumptionPeriodInWorkDays(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder baseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: BaseUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
enter in other units of measure (alternative units of measure) to the base unit of measure.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder planAndOrderDayDetermination(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder roundingProfile(@Nullable String roundingProfile)
Original property name from the Odata EDM: RoundingProfile
In Customizing, enter a threshold value from which the system should round up to the next value per deliverable unit:If the requirements value exceeds the first threshold value, the system always rounds up to the next multiple of the level foundIf the requirements value falls below the first threshold value, the system copies the original requirements value.Two other types of rounding exist:Dynamic rounding profile:These profiles are used to round up quantities to logistical units of measure (for example, layers). The contents of a logistical unit of measure does not have to be know when creating the rounding profile. It is determined by the master data from the material master.Rounding profile with quantity to be added/subtractedWith these profiles, the given quantity is changed either by adding a percentage or subtracting a percentage.Only static rounding profiles are taken into account in requirements planning. Neither dynamic rounding profiles not quantity addition/ subtraction are taken into account.A material's base unit of measure is 1 unit; the purchase order is to be delivered in layers (1 layer corresponds to 5 units) or in pallets (1 pallet corresponds to 8 layers which contains 40 units).You maintain the profile as follows:From a requirements of 2 units, the system is to round up to 5; from a requirement of 32 units, the system is to round up to 40.This results in the following order proposal quantities:Requirement from 1 -> 1 requirement from 31 -> 30Requirement from 2 -> 5 requirement from 32 -> 40Requirement from 6 -> 10 requirement from 74 -> 80Requirement from 7 -> 10If no rounding profile has been entered, the system uses the rounding value entered in the material master record for the planning run.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder lotSizeIndependentCosts(@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.
above the purchase order price or production costs.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder mRPPlanningCalendar(@Nullable String mRPPlanningCalendar)
Original property name from the Odata EDM: MRPPlanningCalendar
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder rangeOfCvrgPrflCode(@Nullable String rangeOfCvrgPrflCode)
Original property name from the Odata EDM: RangeOfCvrgPrflCode
statistical calculation on the basis of average daily requirements.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder isSafetyTime(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder perdPrflForSftyTme(@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.
date) with the safety time/actual range of coverage that is valid for each period.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder isMRPDependentRqmt(@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.
include dependent reservations and stock transfer requirements.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder inHouseProductionTime(@Nullable BigDecimal inHouseProductionTime)
Original property name from the Odata EDM: InHouseProductionTime
In-house production time is independent of the order quantity.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder productIsForCrossProject(@Nullable String productIsForCrossProject)
Original property name from the Odata EDM: ProductIsForCrossProject
in the project stock segments for all documents without account assignment into consideration.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder storageCostsPercentageCode(@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.
determine storage costs.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder srvcLvl(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder mRPAvailabilityType(@Nullable String mRPAvailabilityType)
Original property name from the Odata EDM: MRPAvailabilityType
Subassembly planning with final assemblyGross requirements planningSubassembly planning without final assembly
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder followUpProduct(@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.
discontinued once its warehouse stock is depleted.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder repetitiveManufacturingIsAllwd(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder dependentRequirementsType(@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.
the material:this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder isBulkMaterialComponent(@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.
example, washers or grease).this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder repetitiveManufacturingProfile(@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
sales orders, or with make-to-stock repetitive manufacturing, based on no specific orders.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder rqmtQtyRcptTaktTmeInWrkgDays(@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).
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.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder forecastRequirementsAreSplit(@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.
MRP type is forecast-based planning and the period indicator is not "day".this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder effectiveOutDate(@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.
material, it is to be replaced by the follow-up material.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder mRPProfile(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder componentScrapInPercent(@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.
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder productIsToBeDiscontinued(@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.
in materials planning.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder prodRqmtsAreConsolidated(@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.
analyzing requirements planning.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder matlCompIsMarkedForBackflush(@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.
logic is applied:this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder proposedProductSupplyArea(@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
directly at the production line.this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder currency(@Nullable String currency)
Original property name from the Odata EDM: Currency
this.@Nonnull public ProductSupplyPlanning.ProductSupplyPlanningBuilder plannedOrderActionControl(@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...
that can be carried out for the planned order.this.@Nonnull public ProductSupplyPlanning build()
Copyright © 2021 SAP SE. All rights reserved.