public static final class ProductionSupplyArea.ProductionSupplyAreaBuilder extends Object
Modifier and Type | Method and Description |
---|---|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
automotiveLoadingPoint(String automotiveLoadingPoint)
Constraints: Not nullable, Maximum length: 20
|
ProductionSupplyArea |
build() |
ProductionSupplyArea.ProductionSupplyAreaBuilder |
factoryCalendar(String factoryCalendar)
Constraints: Not nullable, Maximum length: 2
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
lastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
plant(String plant)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
productionSupplyArea(String productionSupplyArea)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
productionSupplyAreaAddress(ProductionSupplyAreaAddress value)
Navigation property to_ProductionSupplyAreaAddress for ProductionSupplyArea to single
ProductionSupplyAreaAddress.
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
productionSupplyAreaAddressID(String productionSupplyAreaAddressID)
Constraints: Not nullable, Maximum length: 10
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
productionSupplyAreaRespPerson(String productionSupplyAreaRespPerson)
Constraints: Not nullable, Maximum length: 3
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
productionSupplyAreaText(ProductionSupplyAreaText... value)
Navigation property to_ProductionSupplyAreaText for ProductionSupplyArea to multiple
ProductionSupplyAreaText.
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
pullIntervalInMinutes(BigDecimal pullIntervalInMinutes)
Constraints: Not nullable, Precision: 8, Scale: 0
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
pullIntervalInWorkdays(BigDecimal pullIntervalInWorkdays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
shiftGrouping(String shiftGrouping)
Constraints: Not nullable, Maximum length: 2
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
shiftSequence(String shiftSequence)
Constraints: Not nullable, Maximum length: 4
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
storageLocation(String storageLocation)
Constraints: Not nullable, Maximum length: 4
|
String |
toString() |
ProductionSupplyArea.ProductionSupplyAreaBuilder |
unloadingPointName(String unloadingPointName)
Constraints: Not nullable, Maximum length: 25
|
ProductionSupplyArea.ProductionSupplyAreaBuilder |
unloadingWarehouseStagingArea(String unloadingWarehouseStagingArea)
Constraints: Not nullable, Maximum length: 10
|
@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder productionSupplyAreaAddress(ProductionSupplyAreaAddress value)
value
- The ProductionSupplyAreaAddress to build this ProductionSupplyArea with.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder productionSupplyAreaText(ProductionSupplyAreaText... value)
value
- The ProductionSupplyAreaTexts to build this ProductionSupplyArea with.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder productionSupplyArea(@Nullable String productionSupplyArea)
Original property name from the Odata EDM: ProductionSupplyArea
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder productionSupplyAreaRespPerson(@Nullable String productionSupplyAreaRespPerson)
Original property name from the Odata EDM: ProductionSupplyAreaRespPerson
You define the key for the person responsible in Customizing for MRP, under, Master data -> Define MRP controllers.
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder unloadingPointName(@Nullable String unloadingPointName)
Original property name from the Odata EDM: UnloadingPointName
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder factoryCalendar(@Nullable String factoryCalendar)
Original property name from the Odata EDM: FactoryCalendar
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder shiftGrouping(@Nullable String shiftGrouping)
Original property name from the Odata EDM: ShiftGrouping
You use the shift grouping and the shift sequence to specify the working times of the consuming work center in detail. The system calculates the calendar buffer from this information.You can specify the shift grouping in the calculation profile and in the PSA. The shift grouping you specify in the PSA overrides the shift grouping you may have entered in the calculation profile.If you do not specify any data for the working time for the consuming work center, the system uses the data that you have maintained for the supplier (supply source). In this case, the calendar buffer calculated by the system is 0.
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder shiftSequence(@Nullable String shiftSequence)
Original property name from the Odata EDM: ShiftSequence
You use the shift grouping and the shift sequence to specify the working times of the consuming work center in detail. The system calculates the calendar buffer from this information.You can specify the shift sequence in the calculation profile and in the PSA. The shift sequence you specify in the PVB overrides one that you may have entered in the calculation profile.If you do not specify any data for the working time for the consuming work center, the system uses the data that you have maintained for the supplier (supply source). In this case, the calendar buffer calculated by the system is 0.
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder pullIntervalInWorkdays(@Nullable BigDecimal pullIntervalInWorkdays)
Original property name from the Odata EDM: PullIntervalInWorkdays
The pull interval is used as a buffer in the control cycle calculation. It increases the number of kanban containers in the control cycle.The pull interval in hours/minutes takes priority over the pull interval in days, i.e. the system uses the pull interval in hours/minutes as soon as you specify this value, irrespective of what you have specified for the pull interval in days.You can specify the pull interval in the calculation profile, in the PSA, and in control cycle maintenance. If you have specified the pull interval more than once, at different points, the system takes this interval into account with the following priorities:1: Control cycle maintenance2: PSA3: Calculation profileThe person who replenishes the PSA arrives at 8 a.m. every day to pick up empty kanbans (kanban cards) and leave behind full ones. In this case, the pull interval amounts to 1 day.
or the interval between the times of delivery by the supply source to the consumer.this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder pullIntervalInMinutes(@Nullable BigDecimal pullIntervalInMinutes)
Original property name from the Odata EDM: PullIntervalInMinutes
The pull interval is used as a buffer in the control cycle calculation. It increases the number of kanban containers in the control cycle.The pull interval in minutes takes priority over the pull interval in days, i.e. the system uses the pull interval in minutes as soon as you specify this value, irrespective of what you have specified for the pull interval in days.To enable the pull interval in minutes to be used in the kanban calculation, it is necessary to define a factory calendar and shift sequences for the control cycle calculation.You can specify the pull interval in the calculation profile, in the PSA, and in control cycle maintenance. If you have specified the pull interval more than once, at different points, the system takes this interval into account with the following priorities:1: Control cycle maintenance2: PSA3: Calculation profileYour production works on a single-shift basis from 8.00 hrs to 16.00 hrs. This information in stored in the shift sequence.The person who replenishes the PSA arrives at 8 hrs and 12 hrs every day to pick up empty kanbans (kanban cards) and leave behind full ones. In this case, the pull interval amounts to 4 hours.
or the interval between the times of delivery by the supply source to the consumer. You can enter the minutes up to the maximum value 59999999.this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder unloadingWarehouseStagingArea(@Nullable String unloadingWarehouseStagingArea)
Original property name from the Odata EDM: UnloadingWarehouseStagingArea
Unloading points in the goods receipt process are understood to be the place where delivered goods are physically unloaded.The unloading point entered is transmitted to the vendor in the forecast delivery schedule, the JIT delivery schedule, or the kanban summarized JIT call.The unloading point is copied from the referenced scheduling agreement or summarized JIT call for the (Automotive) goods receipt process. You can use it as a selection criterion.You must enter the plant and the storage location before you can enter the Automotive unloading point in an MM scheduling agreement item.The permissible (Automotive) unloading points are determined from the staging areas, which you can maintain in Customizing for Logistics Execution.Staging areas were originally organizational units for Logistics Execution. They are now used - described as (Automotive) unloading point - to represent unloading points in the Automotive environment.NoteThe following terms are used synonymously:Unloading point (Automotive) <-> Staging area (Logistics Execution)Unloading zone (Automotive) <-> Door (WM/Logistics Execution)For further information on the use of (Automotive) unloading zones, see the SAP Library under SAP Automotive -> MM Scheduling Agreement Enhancements.The following example describes how you can use (Automotive) unloading points in MM scheduling agreement items:Warehouse number 001 is assigned to the combination plant 0001/storage location 0001 in Customizing for the Enterprise Structure, under Assignment -> Logistics Execution -> Assign warehouse number to plant/storage location.The staging areas (or Automotive unloading points) A1, A2, and A3 have been created in Customizing for Logistics Execution, under Warehouse Management -> Master Data -> Define material staging areas.Plant 0001 and storage location 0001 have been entered in the MM scheduling agreement item.ResultThe system determines the warehouse number and then the corresponding staging areas (or Automotive unloading points) from the plant/storage location combination.Unloading points A1, A2, and A3 are proposed when you use the input help when editing scheduling agreements.The unloading point selected is transmitted to the vendor in the delivery schedule.
(forecast delivery schedule, JIT delivery schedule, or kanban summarized JIT call).this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder productionSupplyAreaAddressID(@Nullable String productionSupplyAreaAddressID)
Original property name from the Odata EDM: ProductionSupplyAreaAddressID
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder lastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
this
.@Nonnull public ProductionSupplyArea.ProductionSupplyAreaBuilder automotiveLoadingPoint(@Nullable String automotiveLoadingPoint)
Original property name from the Odata EDM: AutomotiveLoadingPoint
There may be one or more loading or unloading points assigned to a stop as substops in the hierarchy.The loading or unloading points can be defined in the following ways:From the predecessor documents: The system gets the loading or unloading point information from the predecessor documents, such as a sales order or scheduling agreement. You can find this information for a freight order in the item details on the Advanced SR tab page.In the capacity document: You can also manually define the loading or unloading point in the capacity document. You can do this in the Overview section in the freight order under the Loading Details or Unloading Details tab page.You can use the master data transaction Assign STRM Doors to EWM Doors or Loading Points to assign Stock Room Management (STRM) doors and warehouses to loading or unloading points. For more information, in the SAP Easy Access menu, choose Logistics > Transportation Management > Master Data > Transportation Network > Location > Assign STRM Doors to EWM Doors or Loading Points.
Shipping and Receiving (Advanced SR) process.this
.@Nonnull public ProductionSupplyArea build()
Copyright © 2021 SAP SE. All rights reserved.