KanbanControlCycle (SAP S/4HANA Cloud SDK

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

```
public class KanbanControlCycle
extends VdmEntity<KanbanControlCycle>
```
Kanban Control Cycle
Original entity name from the Odata EDM: A_KanbanControlCycleType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class KanbanControlCycle.KanbanControlCycleBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`KanbanControlCycle.KanbanControlCycleBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static KanbanControlCycleSelectable`	`ALL_FIELDS` Selector for all available fields of KanbanControlCycle.
`static KanbanControlCycleField<String>`	`BACKFLUSH_REPORTING_POINT` Use with available fluent helpers to apply the BackflushReportingPoint field to query operations.
`static KanbanControlCycleField<String>`	`BASE_UNIT` Use with available fluent helpers to apply the BaseUnit field to query operations.
`static KanbanControlCycleField<String>`	`COST_CENTER` Use with available fluent helpers to apply the CostCenter field to query operations.
`static KanbanControlCycleField<LocalDateTime>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static KanbanControlCycleField<Boolean>`	`DESTINATION_BIN_IS_DYNAMIC` Use with available fluent helpers to apply the DestinationBinIsDynamic field to query operations.
`static KanbanControlCycleField<String>`	`EXT_PROCUREMENT_REPLNMT_STRGY` Use with available fluent helpers to apply the ExtProcurementReplnmtStrgy field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`FIXED_KANBAN_CONTAINER_QTY_IN_BS_UNT` Use with available fluent helpers to apply the FixedKanbanContainerQtyInBsUnt field to query operations.
`static KanbanControlCycleField<String>`	`IN_HOUSE_PRODUCTION_REPLNMT_STRGY` Use with available fluent helpers to apply the InHouseProductionReplnmtStrgy field to query operations.
`static KanbanControlCycleField<String>`	`JIT_CALL_PROFILE` Use with available fluent helpers to apply the JITCallProfile field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CONTAINER_CALC_PROFILE` Use with available fluent helpers to apply the KanbanContainerCalcProfile field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CONTAINER_CALCULATION_TYPE` Use with available fluent helpers to apply the KanbanContainerCalculationType field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CONTAINER_DELIVERY_ADDRESS` Use with available fluent helpers to apply the KanbanContainerDeliveryAddress field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CONTAINER_PACKGG_PRODUCT` Use with available fluent helpers to apply the KanbanContainerPackggProduct field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CONTAINER_QUANTITY_IN_BS_UNT` Use with available fluent helpers to apply the KanbanContainerQuantityInBsUnt field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CONTAINER_STATUS_SEQUENCE` Use with available fluent helpers to apply the KanbanContainerStatusSequence field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CONTROL_CYCLE` Use with available fluent helpers to apply the KanbanControlCycle field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CONTROL_CYCLE_CATEGORY` Use with available fluent helpers to apply the KanbanControlCycleCategory field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_CALC_SAFETY_FACTOR` Use with available fluent helpers to apply the KanbanCtnCalcSafetyFactor field to query operations.
`static KanbanControlCycleField<Short>`	`KANBAN_CTN_CALCULATION_CONSTANT` Use with available fluent helpers to apply the KanbanCtnCalculationConstant field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_REFILL_TIME_IN_DAYS` Use with available fluent helpers to apply the KanbanCtnRefillTimeInDays field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_REFILL_TME_IN_MINUTES` Use with available fluent helpers to apply the KanbanCtnRefillTmeInMinutes field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CTN_REPLNMT_TRIGGER_LOGIC` Use with available fluent helpers to apply the KanbanCtnReplnmtTriggerLogic field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_ROUNDING_QTY_IN_BS_UNT` Use with available fluent helpers to apply the KanbanCtnRoundingQtyInBsUnt field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_TRANSPORT_TIME_IN_DAYS` Use with available fluent helpers to apply the KanbanCtnTransportTimeInDays field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_TRANSPORT_TME_IN_MINUTES` Use with available fluent helpers to apply the KanbanCtnTransportTmeInMinutes field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_WAIT_TIME_IN_DAYS` Use with available fluent helpers to apply the KanbanCtnWaitTimeInDays field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KANBAN_CTN_WAIT_TIME_IN_MINUTES` Use with available fluent helpers to apply the KanbanCtnWaitTimeInMinutes field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CTRL_CYC_REPLNMT_TRIGGER_GRP` Use with available fluent helpers to apply the KanbanCtrlCycReplnmtTriggerGrp field to query operations.
`static KanbanControlCycleField<String>`	`KANBAN_CTRL_CYCLE_LIFE_CYCLE_STATUS` Use with available fluent helpers to apply the KanbanCtrlCycleLifeCycleStatus field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KNBN_CTN_CALC_RQMT_BUFFER_IN_PERCENT` Use with available fluent helpers to apply the KnbnCtnCalcRqmtBufferInPercent field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KNBN_CTN_CALC_SUPPLY_SRCE_BUF_IN_PCT` Use with available fluent helpers to apply the KnbnCtnCalcSupplySrceBufInPct field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`KNBN_CTN_REPLNMT_TRGGR_QTY_IN_BS_UNT` Use with available fluent helpers to apply the KnbnCtnReplnmtTrggrQtyInBsUnt field to query operations.
`static KanbanControlCycleField<ZonedDateTime>`	`LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
`static KanbanControlCycleField<LocalDateTime>`	`LOCK_DATE` Use with available fluent helpers to apply the LockDate field to query operations.
`static KanbanControlCycleField<String>`	`MATERIAL_STAGING` Use with available fluent helpers to apply the MaterialStaging field to query operations.
`static KanbanControlCycleField<String>`	`MAX_NR_OF_EMPTY_KANBAN_CONTAINERS` Use with available fluent helpers to apply the MaxNrOfEmptyKanbanContainers field to query operations.
`static KanbanControlCycleField<String>`	`NR_OF_KANBAN_CTNS_FLAGGED_TO_UNLOCK` Use with available fluent helpers to apply the NrOfKanbanCtnsFlaggedToUnlock field to query operations.
`static KanbanControlCycleField<String>`	`NR_OF_WAITING_KNBN_CTNS_BFR_REPLNMT` Use with available fluent helpers to apply the NrOfWaitingKnbnCtnsBfrReplnmt field to query operations.
`static KanbanControlCycleField<String>`	`NUMBER_OF_KANBAN_CONTAINERS` Use with available fluent helpers to apply the NumberOfKanbanContainers field to query operations.
`static KanbanControlCycleField<String>`	`NUMBER_OF_LOAD_CARRIERS` Use with available fluent helpers to apply the NumberOfLoadCarriers field to query operations.
`static KanbanControlCycleField<UUID>`	`PACKING_INSTRUCTION` Use with available fluent helpers to apply the PackingInstruction field to query operations.
`static KanbanControlCycleField<String>`	`PLANNING_WORK_CENTER` Use with available fluent helpers to apply the PlanningWorkCenter field to query operations.
`static KanbanControlCycleField<String>`	`PLANT` Use with available fluent helpers to apply the Plant field to query operations.
`static KanbanControlCycleField<String>`	`PRODUCT` Use with available fluent helpers to apply the Product field to query operations.
`static KanbanControlCycleField<String>`	`PRODUCT_COST_COLLECTOR` Use with available fluent helpers to apply the ProductCostCollector field to query operations.
`static KanbanControlCycleField<Boolean>`	`PRODUCTION_ORDERS_ARE_COMBINED` Use with available fluent helpers to apply the ProductionOrdersAreCombined field to query operations.
`static KanbanControlCycleField<String>`	`PRODUCTION_SUPPLY_AREA` Use with available fluent helpers to apply the ProductionSupplyArea field to query operations.
`static KanbanControlCycleField<String>`	`PRODUCTION_VERSION` Use with available fluent helpers to apply the ProductionVersion field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`PULL_INTERVAL_IN_MINUTES` Use with available fluent helpers to apply the PullIntervalInMinutes field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`PULL_INTERVAL_IN_WORKDAYS` Use with available fluent helpers to apply the PullIntervalInWorkdays field to query operations.
`static KanbanControlCycleField<String>`	`PURCHASE_OUTLINE_AGREEMENT` Use with available fluent helpers to apply the PurchaseOutlineAgreement field to query operations.
`static KanbanControlCycleField<String>`	`PURCHASE_OUTLINE_AGREEMENT_ITEM` Use with available fluent helpers to apply the PurchaseOutlineAgreementItem field to query operations.
`static KanbanControlCycleField<String>`	`PURCHASING_ORGANIZATION` Use with available fluent helpers to apply the PurchasingOrganization field to query operations.
`static KanbanControlCycleField<LocalDateTime>`	`RELEASE_DATE` Use with available fluent helpers to apply the ReleaseDate field to query operations.
`static KanbanControlCycleField<Boolean>`	`REPLNMT_IS_CTRLD_BY_SUPPLY_SOURCE` Use with available fluent helpers to apply the ReplnmtIsCtrldBySupplySource field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`REPLNMT_LEAD_TIME_IN_MINUTES` Use with available fluent helpers to apply the ReplnmtLeadTimeInMinutes field to query operations.
`static KanbanControlCycleField<BigDecimal>`	`REPLNMT_LEAD_TIME_IN_WORKDAYS` Use with available fluent helpers to apply the ReplnmtLeadTimeInWorkdays field to query operations.
`static KanbanControlCycleField<String>`	`SALES_SCHEDULING_AGREEMENT` Use with available fluent helpers to apply the SalesSchedulingAgreement field to query operations.
`static KanbanControlCycleField<String>`	`SALES_SCHEDULING_AGREEMENT_ITEM` Use with available fluent helpers to apply the SalesSchedulingAgreementItem field to query operations.
`static KanbanControlCycleField<Boolean>`	`SEPARATE_GR_IS_NEEDED_IF_SET_TO_FULL` Use with available fluent helpers to apply the SeparateGRIsNeededIfSetToFull field to query operations.
`static KanbanControlCycleField<String>`	`SOURCE_PRODUCTION_SUPPLY_AREA` Use with available fluent helpers to apply the SourceProductionSupplyArea field to query operations.
`static KanbanControlCycleField<String>`	`STOCK_TRANSFER_REPLNMT_STRATEGY` Use with available fluent helpers to apply the StockTransferReplnmtStrategy field to query operations.
`static KanbanControlCycleField<String>`	`STORAGE_BIN` Use with available fluent helpers to apply the StorageBin field to query operations.
`static KanbanControlCycleField<String>`	`STORAGE_LOCATION` Use with available fluent helpers to apply the StorageLocation field to query operations.
`static KanbanControlCycleField<String>`	`STORAGE_TYPE` Use with available fluent helpers to apply the StorageType field to query operations.
`static KanbanControlCycleField<String>`	`STORING_POSITION_NAME` Use with available fluent helpers to apply the StoringPositionName field to query operations.
`static KanbanControlCycleField<String>`	`SUPPLIER` Use with available fluent helpers to apply the Supplier field to query operations.
`static KanbanControlCycleField<String>`	`SUPPLY_SOURCE_PLANT` Use with available fluent helpers to apply the SupplySourcePlant field to query operations.
`static KanbanControlCycleField<String>`	`SUPPLY_SOURCE_RESPONSIBLE_PERSON` Use with available fluent helpers to apply the SupplySourceResponsiblePerson field to query operations.
`static KanbanControlCycleLink<KanbanContainer>`	`TO_KANBAN_CONTAINER` Use with available fluent helpers to apply the to_KanbanContainer navigation property to query operations.
`static KanbanControlCycleField<String>`	`WAREHOUSE` Use with available fluent helpers to apply the Warehouse field to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`KanbanControlCycle()`
KanbanControlCycle(String kanbanControlCycle, String kanbanControlCycleCategory, String product, String plant, String productionVersion, String productionSupplyArea, String supplySourceResponsiblePerson, String storageLocation, String storingPositionName, String kanbanContainerDeliveryAddress, String productCostCollector, String supplier, String purchasingOrganization, String purchaseOutlineAgreement, String purchaseOutlineAgreementItem, String warehouse, String storageType, String storageBin, String baseUnit, BigDecimal kanbanContainerQuantityInBsUnt, String numberOfKanbanContainers, String maxNrOfEmptyKanbanContainers, String inHouseProductionReplnmtStrgy, String materialStaging, Boolean destinationBinIsDynamic, String extProcurementReplnmtStrgy, String stockTransferReplnmtStrategy, Boolean replnmtIsCtrldBySupplySource, String kanbanContainerPackggProduct, Boolean separateGRIsNeededIfSetToFull, String costCenter, String supplySourcePlant, String kanbanContainerStatusSequence, String kanbanCtnReplnmtTriggerLogic, BigDecimal knbnCtnReplnmtTrggrQtyInBsUnt, String kanbanContainerCalculationType, BigDecimal kanbanCtnCalcSafetyFactor, Short kanbanCtnCalculationConstant, BigDecimal kanbanCtnRoundingQtyInBsUnt, BigDecimal fixedKanbanContainerQtyInBsUnt, String kanbanContainerCalcProfile, BigDecimal replnmtLeadTimeInWorkdays, BigDecimal replnmtLeadTimeInMinutes, String salesSchedulingAgreement, String salesSchedulingAgreementItem, String sourceProductionSupplyArea, String jITCallProfile, UUID packingInstruction, String numberOfLoadCarriers, String backflushReportingPoint, String kanbanCtrlCycleLifeCycleStatus, LocalDateTime creationDate, LocalDateTime releaseDate, LocalDateTime lockDate, BigDecimal pullIntervalInWorkdays, BigDecimal pullIntervalInMinutes, BigDecimal kanbanCtnRefillTimeInDays, BigDecimal kanbanCtnRefillTmeInMinutes, BigDecimal kanbanCtnWaitTimeInDays, BigDecimal kanbanCtnWaitTimeInMinutes, BigDecimal kanbanCtnTransportTimeInDays, BigDecimal kanbanCtnTransportTmeInMinutes, BigDecimal knbnCtnCalcRqmtBufferInPercent, BigDecimal knbnCtnCalcSupplySrceBufInPct, String nrOfKanbanCtnsFlaggedToUnlock, String nrOfWaitingKnbnCtnsBfrReplnmt, String kanbanCtrlCycReplnmtTriggerGrp, String planningWorkCenter, Boolean productionOrdersAreCombined, ZonedDateTime lastChangeDateTime, ErpConfigContext erpConfigContext, List<KanbanContainer> toKanbanContainer)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addKanbanContainer(KanbanContainer... entity)` Adds elements to the list of associated KanbanContainer entities.
`static KanbanControlCycle.KanbanControlCycleBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`List<KanbanContainer>`	`fetchKanbanContainer()` Fetches the KanbanContainer entities (one to many) associated with this entity.
`static <T> KanbanControlCycleField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> KanbanControlCycleField<T>`	`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`	`getBackflushReportingPoint()` Constraints: Not nullable, Maximum length: 4
`String`	`getBaseUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getCostCenter()` Constraints: Not nullable, Maximum length: 10
`LocalDateTime`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`Boolean`	`getDestinationBinIsDynamic()` Constraints: none
`protected String`	`getEntityCollection()`
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g.
`String`	`getExtProcurementReplnmtStrgy()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getFixedKanbanContainerQtyInBsUnt()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getInHouseProductionReplnmtStrgy()` Constraints: Not nullable, Maximum length: 4
`String`	`getJITCallProfile()` Constraints: Not nullable, Maximum length: 4
`String`	`getKanbanContainerCalcProfile()` Constraints: Not nullable, Maximum length: 4
`String`	`getKanbanContainerCalculationType()` Constraints: Not nullable, Maximum length: 1
`String`	`getKanbanContainerDeliveryAddress()` Constraints: Not nullable, Maximum length: 10
`Optional<List<KanbanContainer>>`	`getKanbanContainerIfPresent()` Retrieval of associated KanbanContainer entities (one to many).
`List<KanbanContainer>`	`getKanbanContainerOrFetch()` Retrieval of associated KanbanContainer entities (one to many).
`String`	`getKanbanContainerPackggProduct()` Constraints: Not nullable, Maximum length: 40
`BigDecimal`	`getKanbanContainerQuantityInBsUnt()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getKanbanContainerStatusSequence()` Constraints: Not nullable, Maximum length: 4
`String`	`getKanbanControlCycle()` (Key Field) Constraints: Not nullable, Maximum length: 7
`String`	`getKanbanControlCycleCategory()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getKanbanCtnCalcSafetyFactor()` Constraints: Not nullable, Precision: 5, Scale: 3
`Short`	`getKanbanCtnCalculationConstant()` Constraints: none
`BigDecimal`	`getKanbanCtnRefillTimeInDays()` Constraints: Not nullable, Precision: 5, Scale: 2
`BigDecimal`	`getKanbanCtnRefillTmeInMinutes()` Constraints: Not nullable, Precision: 8, Scale: 0
`String`	`getKanbanCtnReplnmtTriggerLogic()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getKanbanCtnRoundingQtyInBsUnt()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getKanbanCtnTransportTimeInDays()` Constraints: Not nullable, Precision: 5, Scale: 2
`BigDecimal`	`getKanbanCtnTransportTmeInMinutes()` Constraints: Not nullable, Precision: 8, Scale: 0
`BigDecimal`	`getKanbanCtnWaitTimeInDays()` Constraints: Not nullable, Precision: 5, Scale: 2
`BigDecimal`	`getKanbanCtnWaitTimeInMinutes()` Constraints: Not nullable, Precision: 8, Scale: 0
`String`	`getKanbanCtrlCycleLifeCycleStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getKanbanCtrlCycReplnmtTriggerGrp()` Constraints: Not nullable, Maximum length: 10
`protected Map<String,Object>`	`getKey()`
`BigDecimal`	`getKnbnCtnCalcRqmtBufferInPercent()` Constraints: Not nullable, Precision: 3, Scale: 0
`BigDecimal`	`getKnbnCtnCalcSupplySrceBufInPct()` Constraints: Not nullable, Precision: 3, Scale: 0
`BigDecimal`	`getKnbnCtnReplnmtTrggrQtyInBsUnt()` Constraints: Not nullable, Precision: 13, Scale: 3
`ZonedDateTime`	`getLastChangeDateTime()` Constraints: Not nullable, Precision: 7
`LocalDateTime`	`getLockDate()` Constraints: Not nullable, Precision: 0
`String`	`getMaterialStaging()` Constraints: Not nullable, Maximum length: 1
`String`	`getMaxNrOfEmptyKanbanContainers()` Constraints: Not nullable, Maximum length: 3
`String`	`getNrOfKanbanCtnsFlaggedToUnlock()` Constraints: Not nullable, Maximum length: 3
`String`	`getNrOfWaitingKnbnCtnsBfrReplnmt()` Constraints: Not nullable, Maximum length: 3
`String`	`getNumberOfKanbanContainers()` Constraints: Not nullable, Maximum length: 3
`String`	`getNumberOfLoadCarriers()` Constraints: Not nullable, Maximum length: 3
`UUID`	`getPackingInstruction()` Constraints: none
`String`	`getPlanningWorkCenter()` Constraints: Not nullable, Maximum length: 8
`String`	`getPlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getProduct()` Constraints: Not nullable, Maximum length: 40
`String`	`getProductCostCollector()` Constraints: Not nullable, Maximum length: 12
`Boolean`	`getProductionOrdersAreCombined()` Constraints: none
`String`	`getProductionSupplyArea()` Constraints: Not nullable, Maximum length: 10
`String`	`getProductionVersion()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getPullIntervalInMinutes()` Constraints: Not nullable, Precision: 8, Scale: 0
`BigDecimal`	`getPullIntervalInWorkdays()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getPurchaseOutlineAgreement()` Constraints: Not nullable, Maximum length: 10
`String`	`getPurchaseOutlineAgreementItem()` Constraints: Not nullable, Maximum length: 5
`String`	`getPurchasingOrganization()` Constraints: Not nullable, Maximum length: 4
`LocalDateTime`	`getReleaseDate()` Constraints: Not nullable, Precision: 0
`Boolean`	`getReplnmtIsCtrldBySupplySource()` Constraints: none
`BigDecimal`	`getReplnmtLeadTimeInMinutes()` Constraints: Not nullable, Precision: 8, Scale: 0
`BigDecimal`	`getReplnmtLeadTimeInWorkdays()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getSalesSchedulingAgreement()` Constraints: Not nullable, Maximum length: 10
`String`	`getSalesSchedulingAgreementItem()` Constraints: Not nullable, Maximum length: 6
`Boolean`	`getSeparateGRIsNeededIfSetToFull()` Constraints: none
`String`	`getSourceProductionSupplyArea()` Constraints: Not nullable, Maximum length: 10
`String`	`getStockTransferReplnmtStrategy()` Constraints: Not nullable, Maximum length: 4
`String`	`getStorageBin()` Constraints: Not nullable, Maximum length: 10
`String`	`getStorageLocation()` Constraints: Not nullable, Maximum length: 4
`String`	`getStorageType()` Constraints: Not nullable, Maximum length: 3
`String`	`getStoringPositionName()` Constraints: Not nullable, Maximum length: 25
`String`	`getSupplier()` Constraints: Not nullable, Maximum length: 10
`String`	`getSupplySourcePlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getSupplySourceResponsiblePerson()` Constraints: Not nullable, Maximum length: 3
`Class<KanbanControlCycle>`	`getType()`
`String`	`getWarehouse()` Constraints: Not nullable, Maximum length: 3
`int`	`hashCode()`
`void`	`setBackflushReportingPoint(String backflushReportingPoint)` Constraints: Not nullable, Maximum length: 4
`void`	`setBaseUnit(String baseUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setCostCenter(String costCenter)` Constraints: Not nullable, Maximum length: 10
`void`	`setCreationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setDestinationBinIsDynamic(Boolean destinationBinIsDynamic)` Constraints: none
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g.
`void`	`setExtProcurementReplnmtStrgy(String extProcurementReplnmtStrgy)` Constraints: Not nullable, Maximum length: 4
`void`	`setFixedKanbanContainerQtyInBsUnt(BigDecimal fixedKanbanContainerQtyInBsUnt)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setInHouseProductionReplnmtStrgy(String inHouseProductionReplnmtStrgy)` Constraints: Not nullable, Maximum length: 4
`void`	`setJITCallProfile(String jITCallProfile)` Constraints: Not nullable, Maximum length: 4
`void`	`setKanbanContainer(List<KanbanContainer> value)` Overwrites the list of associated KanbanContainer entities for the loaded navigation property to_KanbanContainer.
`void`	`setKanbanContainerCalcProfile(String kanbanContainerCalcProfile)` Constraints: Not nullable, Maximum length: 4
`void`	`setKanbanContainerCalculationType(String kanbanContainerCalculationType)` Constraints: Not nullable, Maximum length: 1
`void`	`setKanbanContainerDeliveryAddress(String kanbanContainerDeliveryAddress)` Constraints: Not nullable, Maximum length: 10
`void`	`setKanbanContainerPackggProduct(String kanbanContainerPackggProduct)` Constraints: Not nullable, Maximum length: 40
`void`	`setKanbanContainerQuantityInBsUnt(BigDecimal kanbanContainerQuantityInBsUnt)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setKanbanContainerStatusSequence(String kanbanContainerStatusSequence)` Constraints: Not nullable, Maximum length: 4
`void`	`setKanbanControlCycle(String kanbanControlCycle)` (Key Field) Constraints: Not nullable, Maximum length: 7
`void`	`setKanbanControlCycleCategory(String kanbanControlCycleCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setKanbanCtnCalcSafetyFactor(BigDecimal kanbanCtnCalcSafetyFactor)` Constraints: Not nullable, Precision: 5, Scale: 3
`void`	`setKanbanCtnCalculationConstant(Short kanbanCtnCalculationConstant)` Constraints: none
`void`	`setKanbanCtnRefillTimeInDays(BigDecimal kanbanCtnRefillTimeInDays)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setKanbanCtnRefillTmeInMinutes(BigDecimal kanbanCtnRefillTmeInMinutes)` Constraints: Not nullable, Precision: 8, Scale: 0
`void`	`setKanbanCtnReplnmtTriggerLogic(String kanbanCtnReplnmtTriggerLogic)` Constraints: Not nullable, Maximum length: 1
`void`	`setKanbanCtnRoundingQtyInBsUnt(BigDecimal kanbanCtnRoundingQtyInBsUnt)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setKanbanCtnTransportTimeInDays(BigDecimal kanbanCtnTransportTimeInDays)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setKanbanCtnTransportTmeInMinutes(BigDecimal kanbanCtnTransportTmeInMinutes)` Constraints: Not nullable, Precision: 8, Scale: 0
`void`	`setKanbanCtnWaitTimeInDays(BigDecimal kanbanCtnWaitTimeInDays)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setKanbanCtnWaitTimeInMinutes(BigDecimal kanbanCtnWaitTimeInMinutes)` Constraints: Not nullable, Precision: 8, Scale: 0
`void`	`setKanbanCtrlCycleLifeCycleStatus(String kanbanCtrlCycleLifeCycleStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setKanbanCtrlCycReplnmtTriggerGrp(String kanbanCtrlCycReplnmtTriggerGrp)` Constraints: Not nullable, Maximum length: 10
`void`	`setKnbnCtnCalcRqmtBufferInPercent(BigDecimal knbnCtnCalcRqmtBufferInPercent)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setKnbnCtnCalcSupplySrceBufInPct(BigDecimal knbnCtnCalcSupplySrceBufInPct)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setKnbnCtnReplnmtTrggrQtyInBsUnt(BigDecimal knbnCtnReplnmtTrggrQtyInBsUnt)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setLastChangeDateTime(ZonedDateTime lastChangeDateTime)` Constraints: Not nullable, Precision: 7
`void`	`setLockDate(LocalDateTime lockDate)` Constraints: Not nullable, Precision: 0
`void`	`setMaterialStaging(String materialStaging)` Constraints: Not nullable, Maximum length: 1
`void`	`setMaxNrOfEmptyKanbanContainers(String maxNrOfEmptyKanbanContainers)` Constraints: Not nullable, Maximum length: 3
`void`	`setNrOfKanbanCtnsFlaggedToUnlock(String nrOfKanbanCtnsFlaggedToUnlock)` Constraints: Not nullable, Maximum length: 3
`void`	`setNrOfWaitingKnbnCtnsBfrReplnmt(String nrOfWaitingKnbnCtnsBfrReplnmt)` Constraints: Not nullable, Maximum length: 3
`void`	`setNumberOfKanbanContainers(String numberOfKanbanContainers)` Constraints: Not nullable, Maximum length: 3
`void`	`setNumberOfLoadCarriers(String numberOfLoadCarriers)` Constraints: Not nullable, Maximum length: 3
`void`	`setPackingInstruction(UUID packingInstruction)` Constraints: none
`void`	`setPlanningWorkCenter(String planningWorkCenter)` Constraints: Not nullable, Maximum length: 8
`void`	`setPlant(String plant)` Constraints: Not nullable, Maximum length: 4
`void`	`setProduct(String product)` Constraints: Not nullable, Maximum length: 40
`void`	`setProductCostCollector(String productCostCollector)` Constraints: Not nullable, Maximum length: 12
`void`	`setProductionOrdersAreCombined(Boolean productionOrdersAreCombined)` Constraints: none
`void`	`setProductionSupplyArea(String productionSupplyArea)` Constraints: Not nullable, Maximum length: 10
`void`	`setProductionVersion(String productionVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setPullIntervalInMinutes(BigDecimal pullIntervalInMinutes)` Constraints: Not nullable, Precision: 8, Scale: 0
`void`	`setPullIntervalInWorkdays(BigDecimal pullIntervalInWorkdays)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setPurchaseOutlineAgreement(String purchaseOutlineAgreement)` Constraints: Not nullable, Maximum length: 10
`void`	`setPurchaseOutlineAgreementItem(String purchaseOutlineAgreementItem)` Constraints: Not nullable, Maximum length: 5
`void`	`setPurchasingOrganization(String purchasingOrganization)` Constraints: Not nullable, Maximum length: 4
`void`	`setReleaseDate(LocalDateTime releaseDate)` Constraints: Not nullable, Precision: 0
`void`	`setReplnmtIsCtrldBySupplySource(Boolean replnmtIsCtrldBySupplySource)` Constraints: none
`void`	`setReplnmtLeadTimeInMinutes(BigDecimal replnmtLeadTimeInMinutes)` Constraints: Not nullable, Precision: 8, Scale: 0
`void`	`setReplnmtLeadTimeInWorkdays(BigDecimal replnmtLeadTimeInWorkdays)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setSalesSchedulingAgreement(String salesSchedulingAgreement)` Constraints: Not nullable, Maximum length: 10
`void`	`setSalesSchedulingAgreementItem(String salesSchedulingAgreementItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setSeparateGRIsNeededIfSetToFull(Boolean separateGRIsNeededIfSetToFull)` Constraints: none
`void`	`setSourceProductionSupplyArea(String sourceProductionSupplyArea)` Constraints: Not nullable, Maximum length: 10
`void`	`setStockTransferReplnmtStrategy(String stockTransferReplnmtStrategy)` Constraints: Not nullable, Maximum length: 4
`void`	`setStorageBin(String storageBin)` Constraints: Not nullable, Maximum length: 10
`void`	`setStorageLocation(String storageLocation)` Constraints: Not nullable, Maximum length: 4
`void`	`setStorageType(String storageType)` Constraints: Not nullable, Maximum length: 3
`void`	`setStoringPositionName(String storingPositionName)` Constraints: Not nullable, Maximum length: 25
`void`	`setSupplier(String supplier)` Constraints: Not nullable, Maximum length: 10
`void`	`setSupplySourcePlant(String supplySourcePlant)` Constraints: Not nullable, Maximum length: 4
`void`	`setSupplySourceResponsiblePerson(String supplySourceResponsiblePerson)` Constraints: Not nullable, Maximum length: 3
`void`	`setWarehouse(String warehouse)` Constraints: Not nullable, Maximum length: 3
`protected Map<String,Object>`	`toMapOfFields()`
`protected Map<String,Object>`	`toMapOfNavigationProperties()`
`String`	`toString()`

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

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields

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

- Field Detail
  - ALL_FIELDS
```
public static final KanbanControlCycleSelectable ALL_FIELDS
```
    Selector for all available fields of KanbanControlCycle.
  - KANBAN_CONTROL_CYCLE
```
public static final KanbanControlCycleField<String> KANBAN_CONTROL_CYCLE
```
    Use with available fluent helpers to apply the KanbanControlCycle field to query operations.
  - KANBAN_CONTROL_CYCLE_CATEGORY
```
public static final KanbanControlCycleField<String> KANBAN_CONTROL_CYCLE_CATEGORY
```
    Use with available fluent helpers to apply the KanbanControlCycleCategory field to query operations.
  - PRODUCT
```
public static final KanbanControlCycleField<String> PRODUCT
```
    Use with available fluent helpers to apply the Product field to query operations.
  - PLANT
```
public static final KanbanControlCycleField<String> PLANT
```
    Use with available fluent helpers to apply the Plant field to query operations.
  - PRODUCTION_VERSION
```
public static final KanbanControlCycleField<String> PRODUCTION_VERSION
```
    Use with available fluent helpers to apply the ProductionVersion field to query operations.
  - PRODUCTION_SUPPLY_AREA
```
public static final KanbanControlCycleField<String> PRODUCTION_SUPPLY_AREA
```
    Use with available fluent helpers to apply the ProductionSupplyArea field to query operations.
  - SUPPLY_SOURCE_RESPONSIBLE_PERSON
```
public static final KanbanControlCycleField<String> SUPPLY_SOURCE_RESPONSIBLE_PERSON
```
    Use with available fluent helpers to apply the SupplySourceResponsiblePerson field to query operations.
  - STORAGE_LOCATION
```
public static final KanbanControlCycleField<String> STORAGE_LOCATION
```
    Use with available fluent helpers to apply the StorageLocation field to query operations.
  - STORING_POSITION_NAME
```
public static final KanbanControlCycleField<String> STORING_POSITION_NAME
```
    Use with available fluent helpers to apply the StoringPositionName field to query operations.
  - KANBAN_CONTAINER_DELIVERY_ADDRESS
```
public static final KanbanControlCycleField<String> KANBAN_CONTAINER_DELIVERY_ADDRESS
```
    Use with available fluent helpers to apply the KanbanContainerDeliveryAddress field to query operations.
  - PRODUCT_COST_COLLECTOR
```
public static final KanbanControlCycleField<String> PRODUCT_COST_COLLECTOR
```
    Use with available fluent helpers to apply the ProductCostCollector field to query operations.
  - SUPPLIER
```
public static final KanbanControlCycleField<String> SUPPLIER
```
    Use with available fluent helpers to apply the Supplier field to query operations.
  - PURCHASING_ORGANIZATION
```
public static final KanbanControlCycleField<String> PURCHASING_ORGANIZATION
```
    Use with available fluent helpers to apply the PurchasingOrganization field to query operations.
  - PURCHASE_OUTLINE_AGREEMENT
```
public static final KanbanControlCycleField<String> PURCHASE_OUTLINE_AGREEMENT
```
    Use with available fluent helpers to apply the PurchaseOutlineAgreement field to query operations.
  - PURCHASE_OUTLINE_AGREEMENT_ITEM
```
public static final KanbanControlCycleField<String> PURCHASE_OUTLINE_AGREEMENT_ITEM
```
    Use with available fluent helpers to apply the PurchaseOutlineAgreementItem field to query operations.
  - WAREHOUSE
```
public static final KanbanControlCycleField<String> WAREHOUSE
```
    Use with available fluent helpers to apply the Warehouse field to query operations.
  - STORAGE_TYPE
```
public static final KanbanControlCycleField<String> STORAGE_TYPE
```
    Use with available fluent helpers to apply the StorageType field to query operations.
  - STORAGE_BIN
```
public static final KanbanControlCycleField<String> STORAGE_BIN
```
    Use with available fluent helpers to apply the StorageBin field to query operations.
  - BASE_UNIT
```
public static final KanbanControlCycleField<String> BASE_UNIT
```
    Use with available fluent helpers to apply the BaseUnit field to query operations.
  - KANBAN_CONTAINER_QUANTITY_IN_BS_UNT
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CONTAINER_QUANTITY_IN_BS_UNT
```
    Use with available fluent helpers to apply the KanbanContainerQuantityInBsUnt field to query operations.
  - NUMBER_OF_KANBAN_CONTAINERS
```
public static final KanbanControlCycleField<String> NUMBER_OF_KANBAN_CONTAINERS
```
    Use with available fluent helpers to apply the NumberOfKanbanContainers field to query operations.
  - MAX_NR_OF_EMPTY_KANBAN_CONTAINERS
```
public static final KanbanControlCycleField<String> MAX_NR_OF_EMPTY_KANBAN_CONTAINERS
```
    Use with available fluent helpers to apply the MaxNrOfEmptyKanbanContainers field to query operations.
  - IN_HOUSE_PRODUCTION_REPLNMT_STRGY
```
public static final KanbanControlCycleField<String> IN_HOUSE_PRODUCTION_REPLNMT_STRGY
```
    Use with available fluent helpers to apply the InHouseProductionReplnmtStrgy field to query operations.
  - MATERIAL_STAGING
```
public static final KanbanControlCycleField<String> MATERIAL_STAGING
```
    Use with available fluent helpers to apply the MaterialStaging field to query operations.
  - DESTINATION_BIN_IS_DYNAMIC
```
public static final KanbanControlCycleField<Boolean> DESTINATION_BIN_IS_DYNAMIC
```
    Use with available fluent helpers to apply the DestinationBinIsDynamic field to query operations.
  - EXT_PROCUREMENT_REPLNMT_STRGY
```
public static final KanbanControlCycleField<String> EXT_PROCUREMENT_REPLNMT_STRGY
```
    Use with available fluent helpers to apply the ExtProcurementReplnmtStrgy field to query operations.
  - STOCK_TRANSFER_REPLNMT_STRATEGY
```
public static final KanbanControlCycleField<String> STOCK_TRANSFER_REPLNMT_STRATEGY
```
    Use with available fluent helpers to apply the StockTransferReplnmtStrategy field to query operations.
  - REPLNMT_IS_CTRLD_BY_SUPPLY_SOURCE
```
public static final KanbanControlCycleField<Boolean> REPLNMT_IS_CTRLD_BY_SUPPLY_SOURCE
```
    Use with available fluent helpers to apply the ReplnmtIsCtrldBySupplySource field to query operations.
  - KANBAN_CONTAINER_PACKGG_PRODUCT
```
public static final KanbanControlCycleField<String> KANBAN_CONTAINER_PACKGG_PRODUCT
```
    Use with available fluent helpers to apply the KanbanContainerPackggProduct field to query operations.
  - SEPARATE_GR_IS_NEEDED_IF_SET_TO_FULL
```
public static final KanbanControlCycleField<Boolean> SEPARATE_GR_IS_NEEDED_IF_SET_TO_FULL
```
    Use with available fluent helpers to apply the SeparateGRIsNeededIfSetToFull field to query operations.
  - COST_CENTER
```
public static final KanbanControlCycleField<String> COST_CENTER
```
    Use with available fluent helpers to apply the CostCenter field to query operations.
  - SUPPLY_SOURCE_PLANT
```
public static final KanbanControlCycleField<String> SUPPLY_SOURCE_PLANT
```
    Use with available fluent helpers to apply the SupplySourcePlant field to query operations.
  - KANBAN_CONTAINER_STATUS_SEQUENCE
```
public static final KanbanControlCycleField<String> KANBAN_CONTAINER_STATUS_SEQUENCE
```
    Use with available fluent helpers to apply the KanbanContainerStatusSequence field to query operations.
  - KANBAN_CTN_REPLNMT_TRIGGER_LOGIC
```
public static final KanbanControlCycleField<String> KANBAN_CTN_REPLNMT_TRIGGER_LOGIC
```
    Use with available fluent helpers to apply the KanbanCtnReplnmtTriggerLogic field to query operations.
  - KNBN_CTN_REPLNMT_TRGGR_QTY_IN_BS_UNT
```
public static final KanbanControlCycleField<BigDecimal> KNBN_CTN_REPLNMT_TRGGR_QTY_IN_BS_UNT
```
    Use with available fluent helpers to apply the KnbnCtnReplnmtTrggrQtyInBsUnt field to query operations.
  - KANBAN_CONTAINER_CALCULATION_TYPE
```
public static final KanbanControlCycleField<String> KANBAN_CONTAINER_CALCULATION_TYPE
```
    Use with available fluent helpers to apply the KanbanContainerCalculationType field to query operations.
  - KANBAN_CTN_CALC_SAFETY_FACTOR
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_CALC_SAFETY_FACTOR
```
    Use with available fluent helpers to apply the KanbanCtnCalcSafetyFactor field to query operations.
  - KANBAN_CTN_CALCULATION_CONSTANT
```
public static final KanbanControlCycleField<Short> KANBAN_CTN_CALCULATION_CONSTANT
```
    Use with available fluent helpers to apply the KanbanCtnCalculationConstant field to query operations.
  - KANBAN_CTN_ROUNDING_QTY_IN_BS_UNT
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_ROUNDING_QTY_IN_BS_UNT
```
    Use with available fluent helpers to apply the KanbanCtnRoundingQtyInBsUnt field to query operations.
  - FIXED_KANBAN_CONTAINER_QTY_IN_BS_UNT
```
public static final KanbanControlCycleField<BigDecimal> FIXED_KANBAN_CONTAINER_QTY_IN_BS_UNT
```
    Use with available fluent helpers to apply the FixedKanbanContainerQtyInBsUnt field to query operations.
  - KANBAN_CONTAINER_CALC_PROFILE
```
public static final KanbanControlCycleField<String> KANBAN_CONTAINER_CALC_PROFILE
```
    Use with available fluent helpers to apply the KanbanContainerCalcProfile field to query operations.
  - REPLNMT_LEAD_TIME_IN_WORKDAYS
```
public static final KanbanControlCycleField<BigDecimal> REPLNMT_LEAD_TIME_IN_WORKDAYS
```
    Use with available fluent helpers to apply the ReplnmtLeadTimeInWorkdays field to query operations.
  - REPLNMT_LEAD_TIME_IN_MINUTES
```
public static final KanbanControlCycleField<BigDecimal> REPLNMT_LEAD_TIME_IN_MINUTES
```
    Use with available fluent helpers to apply the ReplnmtLeadTimeInMinutes field to query operations.
  - SALES_SCHEDULING_AGREEMENT
```
public static final KanbanControlCycleField<String> SALES_SCHEDULING_AGREEMENT
```
    Use with available fluent helpers to apply the SalesSchedulingAgreement field to query operations.
  - SALES_SCHEDULING_AGREEMENT_ITEM
```
public static final KanbanControlCycleField<String> SALES_SCHEDULING_AGREEMENT_ITEM
```
    Use with available fluent helpers to apply the SalesSchedulingAgreementItem field to query operations.
  - SOURCE_PRODUCTION_SUPPLY_AREA
```
public static final KanbanControlCycleField<String> SOURCE_PRODUCTION_SUPPLY_AREA
```
    Use with available fluent helpers to apply the SourceProductionSupplyArea field to query operations.
  - JIT_CALL_PROFILE
```
public static final KanbanControlCycleField<String> JIT_CALL_PROFILE
```
    Use with available fluent helpers to apply the JITCallProfile field to query operations.
  - PACKING_INSTRUCTION
```
public static final KanbanControlCycleField<UUID> PACKING_INSTRUCTION
```
    Use with available fluent helpers to apply the PackingInstruction field to query operations.
  - NUMBER_OF_LOAD_CARRIERS
```
public static final KanbanControlCycleField<String> NUMBER_OF_LOAD_CARRIERS
```
    Use with available fluent helpers to apply the NumberOfLoadCarriers field to query operations.
  - BACKFLUSH_REPORTING_POINT
```
public static final KanbanControlCycleField<String> BACKFLUSH_REPORTING_POINT
```
    Use with available fluent helpers to apply the BackflushReportingPoint field to query operations.
  - KANBAN_CTRL_CYCLE_LIFE_CYCLE_STATUS
```
public static final KanbanControlCycleField<String> KANBAN_CTRL_CYCLE_LIFE_CYCLE_STATUS
```
    Use with available fluent helpers to apply the KanbanCtrlCycleLifeCycleStatus field to query operations.
  - CREATION_DATE
```
public static final KanbanControlCycleField<LocalDateTime> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - RELEASE_DATE
```
public static final KanbanControlCycleField<LocalDateTime> RELEASE_DATE
```
    Use with available fluent helpers to apply the ReleaseDate field to query operations.
  - LOCK_DATE
```
public static final KanbanControlCycleField<LocalDateTime> LOCK_DATE
```
    Use with available fluent helpers to apply the LockDate field to query operations.
  - PULL_INTERVAL_IN_WORKDAYS
```
public static final KanbanControlCycleField<BigDecimal> PULL_INTERVAL_IN_WORKDAYS
```
    Use with available fluent helpers to apply the PullIntervalInWorkdays field to query operations.
  - PULL_INTERVAL_IN_MINUTES
```
public static final KanbanControlCycleField<BigDecimal> PULL_INTERVAL_IN_MINUTES
```
    Use with available fluent helpers to apply the PullIntervalInMinutes field to query operations.
  - KANBAN_CTN_REFILL_TIME_IN_DAYS
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_REFILL_TIME_IN_DAYS
```
    Use with available fluent helpers to apply the KanbanCtnRefillTimeInDays field to query operations.
  - KANBAN_CTN_REFILL_TME_IN_MINUTES
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_REFILL_TME_IN_MINUTES
```
    Use with available fluent helpers to apply the KanbanCtnRefillTmeInMinutes field to query operations.
  - KANBAN_CTN_WAIT_TIME_IN_DAYS
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_WAIT_TIME_IN_DAYS
```
    Use with available fluent helpers to apply the KanbanCtnWaitTimeInDays field to query operations.
  - KANBAN_CTN_WAIT_TIME_IN_MINUTES
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_WAIT_TIME_IN_MINUTES
```
    Use with available fluent helpers to apply the KanbanCtnWaitTimeInMinutes field to query operations.
  - KANBAN_CTN_TRANSPORT_TIME_IN_DAYS
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_TRANSPORT_TIME_IN_DAYS
```
    Use with available fluent helpers to apply the KanbanCtnTransportTimeInDays field to query operations.
  - KANBAN_CTN_TRANSPORT_TME_IN_MINUTES
```
public static final KanbanControlCycleField<BigDecimal> KANBAN_CTN_TRANSPORT_TME_IN_MINUTES
```
    Use with available fluent helpers to apply the KanbanCtnTransportTmeInMinutes field to query operations.
  - KNBN_CTN_CALC_RQMT_BUFFER_IN_PERCENT
```
public static final KanbanControlCycleField<BigDecimal> KNBN_CTN_CALC_RQMT_BUFFER_IN_PERCENT
```
    Use with available fluent helpers to apply the KnbnCtnCalcRqmtBufferInPercent field to query operations.
  - KNBN_CTN_CALC_SUPPLY_SRCE_BUF_IN_PCT
```
public static final KanbanControlCycleField<BigDecimal> KNBN_CTN_CALC_SUPPLY_SRCE_BUF_IN_PCT
```
    Use with available fluent helpers to apply the KnbnCtnCalcSupplySrceBufInPct field to query operations.
  - NR_OF_KANBAN_CTNS_FLAGGED_TO_UNLOCK
```
public static final KanbanControlCycleField<String> NR_OF_KANBAN_CTNS_FLAGGED_TO_UNLOCK
```
    Use with available fluent helpers to apply the NrOfKanbanCtnsFlaggedToUnlock field to query operations.
  - NR_OF_WAITING_KNBN_CTNS_BFR_REPLNMT
```
public static final KanbanControlCycleField<String> NR_OF_WAITING_KNBN_CTNS_BFR_REPLNMT
```
    Use with available fluent helpers to apply the NrOfWaitingKnbnCtnsBfrReplnmt field to query operations.
  - KANBAN_CTRL_CYC_REPLNMT_TRIGGER_GRP
```
public static final KanbanControlCycleField<String> KANBAN_CTRL_CYC_REPLNMT_TRIGGER_GRP
```
    Use with available fluent helpers to apply the KanbanCtrlCycReplnmtTriggerGrp field to query operations.
  - PLANNING_WORK_CENTER
```
public static final KanbanControlCycleField<String> PLANNING_WORK_CENTER
```
    Use with available fluent helpers to apply the PlanningWorkCenter field to query operations.
  - PRODUCTION_ORDERS_ARE_COMBINED
```
public static final KanbanControlCycleField<Boolean> PRODUCTION_ORDERS_ARE_COMBINED
```
    Use with available fluent helpers to apply the ProductionOrdersAreCombined field to query operations.
  - LAST_CHANGE_DATE_TIME
```
public static final KanbanControlCycleField<ZonedDateTime> LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
  - TO_KANBAN_CONTAINER
```
public static final KanbanControlCycleLink<KanbanContainer> TO_KANBAN_CONTAINER
```
    Use with available fluent helpers to apply the to_KanbanContainer navigation property to query operations.
- Constructor Detail
  - KanbanControlCycle
```
public KanbanControlCycle()
```
  - KanbanControlCycle
```
public KanbanControlCycle(@Nullable
                          String kanbanControlCycle,
                          @Nullable
                          String kanbanControlCycleCategory,
                          @Nullable
                          String product,
                          @Nullable
                          String plant,
                          @Nullable
                          String productionVersion,
                          @Nullable
                          String productionSupplyArea,
                          @Nullable
                          String supplySourceResponsiblePerson,
                          @Nullable
                          String storageLocation,
                          @Nullable
                          String storingPositionName,
                          @Nullable
                          String kanbanContainerDeliveryAddress,
                          @Nullable
                          String productCostCollector,
                          @Nullable
                          String supplier,
                          @Nullable
                          String purchasingOrganization,
                          @Nullable
                          String purchaseOutlineAgreement,
                          @Nullable
                          String purchaseOutlineAgreementItem,
                          @Nullable
                          String warehouse,
                          @Nullable
                          String storageType,
                          @Nullable
                          String storageBin,
                          @Nullable
                          String baseUnit,
                          @Nullable
                          BigDecimal kanbanContainerQuantityInBsUnt,
                          @Nullable
                          String numberOfKanbanContainers,
                          @Nullable
                          String maxNrOfEmptyKanbanContainers,
                          @Nullable
                          String inHouseProductionReplnmtStrgy,
                          @Nullable
                          String materialStaging,
                          @Nullable
                          Boolean destinationBinIsDynamic,
                          @Nullable
                          String extProcurementReplnmtStrgy,
                          @Nullable
                          String stockTransferReplnmtStrategy,
                          @Nullable
                          Boolean replnmtIsCtrldBySupplySource,
                          @Nullable
                          String kanbanContainerPackggProduct,
                          @Nullable
                          Boolean separateGRIsNeededIfSetToFull,
                          @Nullable
                          String costCenter,
                          @Nullable
                          String supplySourcePlant,
                          @Nullable
                          String kanbanContainerStatusSequence,
                          @Nullable
                          String kanbanCtnReplnmtTriggerLogic,
                          @Nullable
                          BigDecimal knbnCtnReplnmtTrggrQtyInBsUnt,
                          @Nullable
                          String kanbanContainerCalculationType,
                          @Nullable
                          BigDecimal kanbanCtnCalcSafetyFactor,
                          @Nullable
                          Short kanbanCtnCalculationConstant,
                          @Nullable
                          BigDecimal kanbanCtnRoundingQtyInBsUnt,
                          @Nullable
                          BigDecimal fixedKanbanContainerQtyInBsUnt,
                          @Nullable
                          String kanbanContainerCalcProfile,
                          @Nullable
                          BigDecimal replnmtLeadTimeInWorkdays,
                          @Nullable
                          BigDecimal replnmtLeadTimeInMinutes,
                          @Nullable
                          String salesSchedulingAgreement,
                          @Nullable
                          String salesSchedulingAgreementItem,
                          @Nullable
                          String sourceProductionSupplyArea,
                          @Nullable
                          String jITCallProfile,
                          @Nullable
                          UUID packingInstruction,
                          @Nullable
                          String numberOfLoadCarriers,
                          @Nullable
                          String backflushReportingPoint,
                          @Nullable
                          String kanbanCtrlCycleLifeCycleStatus,
                          @Nullable
                          LocalDateTime creationDate,
                          @Nullable
                          LocalDateTime releaseDate,
                          @Nullable
                          LocalDateTime lockDate,
                          @Nullable
                          BigDecimal pullIntervalInWorkdays,
                          @Nullable
                          BigDecimal pullIntervalInMinutes,
                          @Nullable
                          BigDecimal kanbanCtnRefillTimeInDays,
                          @Nullable
                          BigDecimal kanbanCtnRefillTmeInMinutes,
                          @Nullable
                          BigDecimal kanbanCtnWaitTimeInDays,
                          @Nullable
                          BigDecimal kanbanCtnWaitTimeInMinutes,
                          @Nullable
                          BigDecimal kanbanCtnTransportTimeInDays,
                          @Nullable
                          BigDecimal kanbanCtnTransportTmeInMinutes,
                          @Nullable
                          BigDecimal knbnCtnCalcRqmtBufferInPercent,
                          @Nullable
                          BigDecimal knbnCtnCalcSupplySrceBufInPct,
                          @Nullable
                          String nrOfKanbanCtnsFlaggedToUnlock,
                          @Nullable
                          String nrOfWaitingKnbnCtnsBfrReplnmt,
                          @Nullable
                          String kanbanCtrlCycReplnmtTriggerGrp,
                          @Nullable
                          String planningWorkCenter,
                          @Nullable
                          Boolean productionOrdersAreCombined,
                          @Nullable
                          ZonedDateTime lastChangeDateTime,
                          @Nullable
                          ErpConfigContext erpConfigContext,
                          List<KanbanContainer> toKanbanContainer)
```
- Method Detail
  - getType
```
@Nonnull
public Class<KanbanControlCycle> getType()
```
    Specified by:
    
    getType in class VdmObject<KanbanControlCycle>
    
    Returns:
    
    The class of this object.
  - setKanbanControlCycle
```
public void setKanbanControlCycle(@Nullable
                                  String kanbanControlCycle)
```
    (Key Field) Constraints: Not nullable, Maximum length: 7
    Original property name from the Odata EDM: KanbanControlCycle
    The following data is defined and linked in the kanban control cycle used in Kanban and JIT Outbound processing:Production supply areaMaterialNumber of kanbans or containers and the kanban quantity or call-off quantityReplenishment strategiesIf necessary, the source of replenishment depending on the replenishment strategy
    
    Parameters:
    
    kanbanControlCycle - Number, that specifically identifies the control cycle.
  - setKanbanControlCycleCategory
```
public void setKanbanControlCycleCategory(@Nullable
                                          String kanbanControlCycleCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanControlCycleCategory
    
    Parameters:
    
    kanbanControlCycleCategory - Kanban Control Cycle Category
  - setProduct
```
public void setProduct(@Nullable
                       String product)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Product
    
    Parameters:
    
    product - Alphanumeric key uniquely identifying the material.
  - setPlant
```
public void setPlant(@Nullable
                     String plant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
    
    Parameters:
    
    plant - Key uniquely identifying a plant.
  - setProductionVersion
```
public void setProductionVersion(@Nullable
                                 String productionVersion)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProductionVersion
    The production version determines the following:the BOM alternative for a BOM explosionthe task list type, the task list group and the task list group counter for allocation to task listslot-size restrictions for repetitive manufacturing
    
    Parameters:
    
    productionVersion - Key which determines the various production techniques according to which a material can be manufactured.
  - setProductionSupplyArea
```
public void setProductionSupplyArea(@Nullable
                                    String productionSupplyArea)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ProductionSupplyArea
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Parameters:
    
    productionSupplyArea - The production supply area (PSA) serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes.
  - setSupplySourceResponsiblePerson
```
public void setSupplySourceResponsiblePerson(@Nullable
                                             String supplySourceResponsiblePerson)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SupplySourceResponsiblePerson
    You define the key for the person responsible in Customizing for MRP under Master data -> Define MRP controllers.
    
    Parameters:
    
    supplySourceResponsiblePerson - In in-house production, the responsible person defines the person that, as the Supply source, is in charge of the material provision.
  - setStorageLocation
```
public void setStorageLocation(@Nullable
                               String storageLocation)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StorageLocation
    
    Parameters:
    
    storageLocation - Storage Location
  - setStoringPositionName
```
public void setStoringPositionName(@Nullable
                                   String storingPositionName)
```
    Constraints: Not nullable, Maximum length: 25
    Original property name from the Odata EDM: StoringPositionName
    
    Parameters:
    
    storingPositionName - Specifies the precise position (e.g. a certain shelf section) in which your material can be found in the supply area.
  - setKanbanContainerDeliveryAddress
```
public void setKanbanContainerDeliveryAddress(@Nullable
                                              String kanbanContainerDeliveryAddress)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: KanbanContainerDeliveryAddress
    
    Parameters:
    
    kanbanContainerDeliveryAddress - Kanban Delivery Address
  - setProductCostCollector
```
public void setProductCostCollector(@Nullable
                                    String productCostCollector)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ProductCostCollector
    
    Parameters:
    
    productCostCollector - Number that specifies the cost collector for Repetitive Manufacturing, order-related production and KANBAN.
  - setSupplier
```
public void setSupplier(@Nullable
                        String supplier)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Supplier
    With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
    
    Parameters:
    
    supplier - Alphanumeric key uniquely identifying the document.
  - setPurchasingOrganization
```
public void setPurchasingOrganization(@Nullable
                                      String purchasingOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: PurchasingOrganization
    
    Parameters:
    
    purchasingOrganization - Purchasing Organization
  - setPurchaseOutlineAgreement
```
public void setPurchaseOutlineAgreement(@Nullable
                                        String purchaseOutlineAgreement)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PurchaseOutlineAgreement
    
    Parameters:
    
    purchaseOutlineAgreement - Number of the outline agreement.
  - setPurchaseOutlineAgreementItem
```
public void setPurchaseOutlineAgreementItem(@Nullable
                                            String purchaseOutlineAgreementItem)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: PurchaseOutlineAgreementItem
    
    Parameters:
    
    purchaseOutlineAgreementItem - Specifies the number that uniquely identifies an item in .
  - setWarehouse
```
public void setWarehouse(@Nullable
                         String warehouse)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: Warehouse
    All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
    
    Parameters:
    
    warehouse - Number that identifies a complex, physical warehouse structure within the Warehouse Management system.
  - setStorageType
```
public void setStorageType(@Nullable
                           String storageType)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: StorageType
    A typical warehouse could have the following storage types:Goods receipt areaPicking areaHigh-rack storage areaBulk storage areaOpen storage areaGoods issue area
    
    Parameters:
    
    storageType - The storage type is a subdivision of a complex, physical warehouse. Different storage types are identified by their warehousing technique, form of organization, or their function.
  - setStorageBin
```
public void setStorageBin(@Nullable
                          String storageBin)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: StorageBin
    A storage bin can be further sub-divided into bin sections. Several different materials (quants) can be stored in one bin at the same time.
    
    Parameters:
    
    storageBin - The storage bin (sometimes referred to as a "slot") is the smallest addressable unit in a warehouse. It identifies the exact location in the warehouse where goods can be stored.
  - setBaseUnit
```
public void setBaseUnit(@Nullable
                        String baseUnit)
```
    Constraints: Not nullable, Maximum length: 3
    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.
    
    Parameters:
    
    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.
  - setKanbanContainerQuantityInBsUnt
```
public void setKanbanContainerQuantityInBsUnt(@Nullable
                                              BigDecimal kanbanContainerQuantityInBsUnt)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: KanbanContainerQuantityInBsUnt
    Quantity of material (target quantity) that is specified for a kanban.Event-driven Kanban:Proposed value for the quantity of material in a kanban that is used by the system if no order quantity was entered when the kanban signal was generated.The quantity per kanban must be a whole multiple of the rounding quantity.JIT Outbound:Quantity of material that is used as a proposed call-off quantity. If a packing instruction is specified for the control cycle, the quantity is determined by its target quantity.
    
    Parameters:
    
    kanbanContainerQuantityInBsUnt - Classic Kanban:
  - setNumberOfKanbanContainers
```
public void setNumberOfKanbanContainers(@Nullable
                                        String numberOfKanbanContainers)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NumberOfKanbanContainers
    
    Parameters:
    
    numberOfKanbanContainers - The number of kanbans, which means containers, that circulate between the customer and source in the control cycle.
  - setMaxNrOfEmptyKanbanContainers
```
public void setMaxNrOfEmptyKanbanContainers(@Nullable
                                            String maxNrOfEmptyKanbanContainers)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: MaxNrOfEmptyKanbanContainers
    This setting is only relevant to control cycles for classic kanban.
    
    Parameters:
    
    maxNrOfEmptyKanbanContainers - Maximum number of kanbans that are allowed to be empty. Once this limit has been reached, the kanbans must be filled up again.
  - setInHouseProductionReplnmtStrgy
```
public void setInHouseProductionReplnmtStrgy(@Nullable
                                             String inHouseProductionReplnmtStrgy)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InHouseProductionReplnmtStrgy
    You use the replenishment strategy to define the following, for example:Whether replenishment is only triggered by kanbans or whether a procurement element is createdWhich movement type is used to post the goods receiptThe replenishment strategies are defined in Customizing for KANBAN. You then assign the appropriate replenishment strategy to the control cycle.
    
    Parameters:
    
    inHouseProductionReplnmtStrgy - The replenishment strategy defines how procurement in in-house production is to be carried out.
  - setMaterialStaging
```
public void setMaterialStaging(@Nullable
                               String materialStaging)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: MaterialStaging
    As with the location coordinates (warehouse number, storage type, and storage bin), the system files this indicator in the control cycle.The following staging types are supported:"1": Pick partsThese materials are picked according to the required quantity specified in the production order."2": Crate or kanban partsThese materials are always removed from the warehouse in full cases. These can be ordered, for example, as soon as a case of needed parts is emptied in production."3": Release order partsRelease order parts are scheduled individually and the quantities are supplied manually to replenishment storage bins based on the requirements of production orders and the stock levels in the scheduled production supply areas."4": Manual stagingMaterials are staged manually. For example, you can transport individual components using manually created transfer orders, or you can use the bypass method to transport them directly from the goods receipt zone to production. In goods receipt posting, postings are made to the production storage bins from the control cycles."0": Not relevant to WM-PPThese materials are not relevant to WM staging. They cannot be requested using the WM system.
    
    Parameters:
    
    materialStaging - The material staging indicator defines the method of how needed materials can be supplied for production with the assistance of the Warehouse Management system.
  - setDestinationBinIsDynamic
```
public void setDestinationBinIsDynamic(@Nullable
                                       Boolean destinationBinIsDynamic)
```
    Constraints: none
    Original property name from the Odata EDM: DestinationBinIsDynamic
    The dynamic bin coordinate is usually used to manage the stock figures in the interim storage areas separately according to requirement tracking numbers (for example, cost center, deliveries).
    
    Parameters:
    
    destinationBinIsDynamic - Means that the destination storage bin will be generated dynamically for this goods transfer.
  - setExtProcurementReplnmtStrgy
```
public void setExtProcurementReplnmtStrgy(@Nullable
                                          String extProcurementReplnmtStrgy)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ExtProcurementReplnmtStrgy
    You use the replenishment strategy to define the following, for example:Which procurement element is to be used to carry out procurementWhich movement type is to be used to post the goods receiptYou define the replenishment strategies in Customizing for KANBAN. You then assign the appropriate replenishment strategy to the control cycle.
    
    Parameters:
    
    extProcurementReplnmtStrgy - The replenishment strategy defines exactly how procurement using external procurement procedures is to be carried out.
  - setStockTransferReplnmtStrategy
```
public void setStockTransferReplnmtStrategy(@Nullable
                                            String stockTransferReplnmtStrategy)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StockTransferReplnmtStrategy
    You use the replenishment strategy to define the following, for example:Whether the stock transfer is to be carried out using a reservation, direct transfer posting or via the WM/PP interfaceWhich movement type is to be used to post the goods receiptYou define the replenishment strategies in Customizing for KANBAN. You then assign the appropriate replenishment strategy to the control cycle.
    
    Parameters:
    
    stockTransferReplnmtStrategy - The replenishment strategy defines exactly how procurement in stock transfer is to be carried out.
  - setReplnmtIsCtrldBySupplySource
```
public void setReplnmtIsCtrldBySupplySource(@Nullable
                                            Boolean replnmtIsCtrldBySupplySource)
```
    Constraints: none
    Original property name from the Odata EDM: ReplnmtIsCtrldBySupplySource
    An independent supply source specifies itself how material replenishment is to be carried out. That is, it specifies independently when the delivery- or production-relevant replenishment element is to be created.If you check the box, the two operations Status Change Set to Empty and Trigger Replenishment are decoupled. In this case, it is not the consumer (demand source) that triggers the replenishment but the supply source. The consumer sets the kanban to "Empty" but no replenishment element is generated and the system automatically sets the kanban to the status "Waiting". The supply source then sets these kanbans to "Empty" on the kanban board, thus generating the replenishment elements. The independent supply source thus specifies the time of replenishment itself.Usually, the replenishment strategy is defined for the control cycle and is determined automatically when the kanban signal is triggered.
    
    Parameters:
    
    replnmtIsCtrldBySupplySource - You use this checkbox to specify that an independent supply source has been assigned to the control cycle.
  - setKanbanContainerPackggProduct
```
public void setKanbanContainerPackggProduct(@Nullable
                                            String kanbanContainerPackggProduct)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: KanbanContainerPackggProduct
    Containers are created with a master record in the material master.SAP recommends that you use the material type CONT to make the selection by containers easier.
    
    Parameters:
    
    kanbanContainerPackggProduct - Material number of the container that is used for the control cycle.
  - setSeparateGRIsNeededIfSetToFull
```
public void setSeparateGRIsNeededIfSetToFull(@Nullable
                                             Boolean separateGRIsNeededIfSetToFull)
```
    Constraints: none
    Original property name from the Odata EDM: SeparateGRIsNeededIfSetToFull
    The separate GR posting should be carried out, ifthe demand source posting is linked to an automatic GR posting, but the kanban does not arrive at the demand source immediately.The material arrives with a central goods receipt and is passed on to production later.If the selection is not set, the kanban status change automatically leads to a goods receipt posting in materials management. Likewise, the goods receipt posting usually leads to an automatic status change.
    
    Parameters:
    
    separateGRIsNeededIfSetToFull - This indicator determines that the goods receipt posting is separated from the kanban status change.
  - setCostCenter
```
public void setCostCenter(@Nullable
                          String costCenter)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CostCenter
    
    Parameters:
    
    costCenter - A key that uniquely identifies a cost center.
  - setSupplySourcePlant
```
public void setSupplySourcePlant(@Nullable
                                 String supplySourcePlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SupplySourcePlant
    
    Parameters:
    
    supplySourcePlant - Plant that represents the supply source for kanban replenishment for stock transfer procedures from plant to plant or in-house production.
  - setKanbanContainerStatusSequence
```
public void setKanbanContainerStatusSequence(@Nullable
                                             String kanbanContainerStatusSequence)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: KanbanContainerStatusSequence
    If no status sequence is defined in the control cycle, the statuses "Full" and "Empty" must be used. All other statuses are optional. If the control cycle is defined with an independent supply source, the status "Waiting" is additionally a mandatory status.If a status sequence is defined in the control cycle and if a kanban signal (kanban status change) is triggered with no specification of the follow-on status, the system searches for the next mandatory or optional status in the status sequence. If you specify the follow-on status, the system can skip recommended statuses and you can also use optional statuses.For individual status changes within the status sequence, you can also specify whether activities defined by yourself (such as goods receipt, kanban print, user exit) are to be executed. In this case, you must maintain these own activities for the the status sequence in Customizing for Kanban.
    
    Parameters:
    
    kanbanContainerStatusSequence - The status sequence defines which kanban statuses must, should, can, or must not be used in Kanban processing. The status sequence is assigned in the control cycle.
  - setKanbanCtnReplnmtTriggerLogic
```
public void setKanbanCtnReplnmtTriggerLogic(@Nullable
                                            String kanbanCtnReplnmtTriggerLogic)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanCtnReplnmtTriggerLogic
    By selecting another logic, you can instruct the system to trigger replenishment for a kanban B that is set to the inactive status "wait" if a signal is given for another kanban A.These signals for triggering replenishment include:Setting the status to "in use":Here, the replenishment is triggered for kanban B when kanban A is set to the status "in use".Setting the status to "wait"Here, the replenishment is triggered for kanban B when kanban A is set to the status "wait".Arriving at or exceeding the trigger quantity:Here, the replenishment is triggered for kanban B when the actual quantity of kanban A is reduced to the trigger quantity or falls below the trigger quantity due to the quantity signal. The trigger quantity must also be maintained in the control cycle.Then kanban A is first set to status "wait". The replenishment for kanban A is triggered when the appropriate signal is given for the subsequent kanban.The purpose of this special logic is to set up a so-called single-card kanban with with two kanbans in a control cycle. Because a kanban is set to the inactive status, "wait" for certain periods, the stocks at the demand source can be further reduced - which is especially useful if the material is not always required.
    
    Parameters:
    
    kanbanCtnReplnmtTriggerLogic - Usually the replenishment for a kanban is triggered if the kanban is set to the status, "empty".
  - setKnbnCtnReplnmtTrggrQtyInBsUnt
```
public void setKnbnCtnReplnmtTrggrQtyInBsUnt(@Nullable
                                             BigDecimal knbnCtnReplnmtTrggrQtyInBsUnt)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: KnbnCtnReplnmtTrggrQtyInBsUnt
    If in KANBAN production control, you work with the quantity signal, then the quantity in a kanban is reduced by the quantity signal. If replenishment is not to be triggered when the kanban quantity is zero, but instead as soon as the quantity is reduced to the trigger quantity, then the system triggers replenishment for another kanban with the status, WAIT when the container quantity actually reaches or exceeds the trigger quantity.This field can be used for information purposes for the trigger logics for replenishment listed below (however it has no function):triggering replenishment at status IN USE andtriggering replenishment at status WAIT
    
    Parameters:
    
    knbnCtnReplnmtTrggrQtyInBsUnt - If you want to trigger replenishment when the trigger quantity is exceeded, you must define the trigger quantity here.
  - setKanbanContainerCalculationType
```
public void setKanbanContainerCalculationType(@Nullable
                                              String kanbanContainerCalculationType)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanContainerCalculationType
    The formulas for the kanban calculation are as follows:Number of kanbans = (( RT * AC) / CONT) * SF * SB + CQuantity per kanban = ((RT * AC) / (AK-C) * SF * SBKey to abbreviations: AK: Number of kanbansCONT: Quantity per kanbanRT: Replenishment lead time per kanban(the replenishment lead time also includes the pull interval)AC: Consumption per unit of time(also includes the calendar buffer, requirement buffer and requirement fluctuations)SF: Safety factor (default value 1)SB: Supply source bufferC: Constant (default value 1)
    
    Parameters:
    
    kanbanContainerCalculationType - The calculation type controls whether the number of kanbans or the quantity per kanban is to be calculated.
  - setKanbanCtnCalcSafetyFactor
```
public void setKanbanCtnCalcSafetyFactor(@Nullable
                                         BigDecimal kanbanCtnCalcSafetyFactor)
```
    Constraints: Not nullable, Precision: 5, Scale: 3
    Original property name from the Odata EDM: KanbanCtnCalcSafetyFactor
    The formulas for the kanban calculation are as follows:Number of kanbans = (( RT * AC) / CONT) * SF * SB + CQuantity per kanban = ((RT * AC) / (AK-C) * SF * SBKey to abbreviations: AK: Number of kanbansCONT: Quantity per kanbanRT: Replenishment lead time per kanban(the replenishment lead time also includes the pull interval)AC: Consumption per unit of time(also includes the calendar buffer, requirement buffer and requirement fluctuations)SF: Safety factor (default value 1)SB: Supply source bufferC: Constant (default value 1)
    
    Parameters:
    
    kanbanCtnCalcSafetyFactor - The safety factor is used to cater for fluctuations in requirements. It is multiplied by the result of the kanban calculation formula.
  - setKanbanCtnCalculationConstant
```
public void setKanbanCtnCalculationConstant(@Nullable
                                            Short kanbanCtnCalculationConstant)
```
    Constraints: none
    Original property name from the Odata EDM: KanbanCtnCalculationConstant
    If a kanban is reported empty when all the material in the kanban has been used up, the constant is set to 1.If several work centers are served by one production supply area when kanbans are reported empty in this way, the constant must be increased by the number of work centers.If, on the other hand, the kanban is reported empty as soon as the first part is withdrawn, the constant is 0.You can also use this constant to plan a safety stock.
    
    Parameters:
    
    kanbanCtnCalculationConstant - Depending on how Kanban is used in production, you set the constant in the following way:
  - setKanbanCtnRoundingQtyInBsUnt
```
public void setKanbanCtnRoundingQtyInBsUnt(@Nullable
                                           BigDecimal kanbanCtnRoundingQtyInBsUnt)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: KanbanCtnRoundingQtyInBsUnt
    Event-driven control cyclesThe kanban signal triggers the system to round the requested material quantity for this kanban up to the next whole multiple of the rounding quantity.The rounding quantity must be a multiple of the fixed kanban quantity.The kanban calculationThe kanban quantity calculated is rounded up to the next whole multiple of the rounding quantity.
    
    Parameters:
    
    kanbanCtnRoundingQtyInBsUnt - The rounding quantity is relevant for:
  - setFixedKanbanContainerQtyInBsUnt
```
public void setFixedKanbanContainerQtyInBsUnt(@Nullable
                                              BigDecimal fixedKanbanContainerQtyInBsUnt)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: FixedKanbanContainerQtyInBsUnt
    Using the fixed kanban quantity, you can define a precise quantity of material per kanban. This has the same effect as a fixed lot size and kanbans are only created for this fixed material quantity.If you enter a required quantity less than the fixed kanban quantity, the system creates a kanban for the fixed kanban quantity.If you enter a quantity greater than the fixed kanban quantity, the system creates several kanbans for the fixed quantity until the required quantity is covered. Here, if necessary, the required quantity is rounded up to a complete multiple of the fixed quantity. This means it is possible that more material is actually procured than was requested.
    
    Parameters:
    
    fixedKanbanContainerQtyInBsUnt - The fixed kanban quantity is only relevant for event-driven control cycles.
  - setKanbanContainerCalcProfile
```
public void setKanbanContainerCalcProfile(@Nullable
                                          String kanbanContainerCalcProfile)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: KanbanContainerCalcProfile
    Calculation typeThe calculation type controls whether the number of kanbans or the quantity per kanban is calculated.Safety factorThe safety factor is used to offset requirement fluctuations proportionately. It is multiplied by the result of the formula for the kanban calculation.ConstantDepending on how Kanban is used in production, you set the constant as follows:If a kanban is set to empty when the material in a kanban is completely used up, the constant is set to 1.In this case, if several work centers use material from a production supply area, you must increase the constant by the number of work centers.If, however, the kanban is set to empty as soon as the first part is taken out, the constant is 0.You can also use the constants to plan a safety stock.Smoothing typeYou use the smoothing type to specify whether dependent requirements in the period of examination are:Not smoothedSmoothed within the period of a weekSmoothed according to a predefined distribution functionFactory calendar, Grouping, Shift programThese parameters are necessary if you have maintained a sub-day replenishment lead time in the control cycle. From the shift sequence, the system calculates the average daily worktime for the conversion of the exact-to-the-day dependent requirement quantity to the quantity per replenishment lead time.
    
    Parameters:
    
    kanbanContainerCalcProfile - In the calculation profile, you can store the data for the automatic calculation of the kanban circulation:
  - setReplnmtLeadTimeInWorkdays
```
public void setReplnmtLeadTimeInWorkdays(@Nullable
                                         BigDecimal replnmtLeadTimeInWorkdays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: ReplnmtLeadTimeInWorkdays
    You can specify either the overall value for the replenishment lead time or its individual constituents (refill time, wait time, transportation time). In the latter case, the system totals up the three constituent parts and rounds the value up to a whole number.The replenishment lead time in days is used for the kanban calculation if the replenishment lead time in hours/minutes has not been maintained or no working times have been maintained in the associated calculation profile. The replenishment lead time in hours/minutes takes priority over the replenishment lead time in days, i.e. the system uses the replenishment lead time in hours/minutes as soon as you specify this value, irrespective of what you have specified for the replenishment lead time in days.In the case of control cycles for in-house production or external procurement, this time only has to be maintained if it differs from the in-house production time or planned delivery time maintained in the material master record. The goods receipt processing time is not taken into account.In control cycles for stock transfers, as a basic rule, you must always specify a replenishment lead time.
    
    Parameters:
    
    replnmtLeadTimeInWorkdays - Indicates the replenishment lead time in days.
  - setReplnmtLeadTimeInMinutes
```
public void setReplnmtLeadTimeInMinutes(@Nullable
                                        BigDecimal replnmtLeadTimeInMinutes)
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: ReplnmtLeadTimeInMinutes
    The replenishment lead time in minutes is used in the kanban calculation. The replenishment lead time in minutes takes priority over the replenishment lead time in days, that is to say, the system uses the replenishment lead time in minutes as soon as you have specified this value, irrespective of what you specified for the replenishment lead time in days.You can specify either the overall value for the replenishment lead time or the values for its individual constituents (refill time, wait time, and transportation time). In the latter case, the system calculates the total from the three constituent parts.A sub-day replenishment lead time can be used for the kanban calculation only if you have maintained working times resulting from a shift sequence in the associated calculation profile.
    
    Parameters:
    
    replnmtLeadTimeInMinutes - Indicates the replenishment lead time in hours and minutes. You can enter the minutes up to the maximum value 59999999.
  - setSalesSchedulingAgreement
```
public void setSalesSchedulingAgreement(@Nullable
                                        String salesSchedulingAgreement)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesSchedulingAgreement
    If you have determined in the replenishment strategy, that you will deliver your material directly to a customer via a SD scheduling agreement, then enter here the number of your SD scheduling agreement for the material here.
    
    Parameters:
    
    salesSchedulingAgreement - Number of the SD scheduling agreement.
  - setSalesSchedulingAgreementItem
```
public void setSalesSchedulingAgreementItem(@Nullable
                                            String salesSchedulingAgreementItem)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesSchedulingAgreementItem
    Enter the scheduling agreement item of your SD scheduling agreement here.
    
    Parameters:
    
    salesSchedulingAgreementItem - Represents the item in the scheduling agreement.
  - setSourceProductionSupplyArea
```
public void setSourceProductionSupplyArea(@Nullable
                                          String sourceProductionSupplyArea)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SourceProductionSupplyArea
    A supply area can be the supply source in a stock transfer, if the delivering storage location is divided into supply areas again. This is the case if the warehouse is supplied via Kanban (multi-level control cycles).
    
    Parameters:
    
    sourceProductionSupplyArea - Determines the supply area, which acts as a supply source in stock transfer.
  - setJITCallProfile
```
public void setJITCallProfile(@Nullable
                              String jITCallProfile)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: JITCallProfile
    You determine the following in the JIT call profile:the type of call (at present only summarized JIT call available)the partner function, through which you define the output partner for determining the transmission of the JIT call.Through the output partner you can control the grouping of JIT calls and telecommunications.the type of groupingYou can group material requirements according to plant or according to plant and unloading point.the time definitionHere you control the grouping of material requirements according to delivery date.So in the profile you determine the basic information for creating a call.In the control cycle you have a JIT call profile and a kanban-replenishment strategy with control type summarized JIT call.
    
    Parameters:
    
    jITCallProfile - Controls the creation of a JIT call.
  - setPackingInstruction
```
public void setPackingInstruction(@Nullable
                                  UUID packingInstruction)
```
    Constraints: none
    Original property name from the Odata EDM: PackingInstruction
    
    Parameters:
    
    packingInstruction - Unique identification number for a packing object.
  - setNumberOfLoadCarriers
```
public void setNumberOfLoadCarriers(@Nullable
                                    String numberOfLoadCarriers)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NumberOfLoadCarriers
    The replenishment strategy in the control cycle determines whether one kanban is created from the number of load carriers you entered or whether one kanban corresponds to one load carrier. In the last instance, the number of load carriers corresponds to the number of kanbans you requested.Automatic Supply-to-Production:This quantity is multiplied by the call quantity and is used as the minimum quantity for replenishment proposals.
    
    Parameters:
    
    numberOfLoadCarriers - Specifies the number of load carriers you can order with one call.
  - setBackflushReportingPoint
```
public void setBackflushReportingPoint(@Nullable
                                       String backflushReportingPoint)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BackflushReportingPoint
    In this field, enter the reporting point for which you want to execute the backflush. If you do not specify a reporting point here and execute the posting, the system lists all the existing reporting points for the production version in the dialog box entitled, Reporting Point Selection.You can only enter a reporting point after you have selected the indicator RP backflush selected.
    
    Parameters:
    
    backflushReportingPoint - The reporting point specifies an operation for which a backflush should be executed.
  - setKanbanCtrlCycleLifeCycleStatus
```
public void setKanbanCtrlCycleLifeCycleStatus(@Nullable
                                              String kanbanCtrlCycleLifeCycleStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanCtrlCycleLifeCycleStatus
    Created - The control cycle has been created consistently and is ready for productive use. The kanban containers have the status Locked and cannot be unlocked.Released - The control cycle has been released and is in productive use. The kanban containers can be unlocked.Locked - The control cycle is to be excluded from productive use. The kanban containers have the status Locked and cannot be unlocked. The replenishment process with the kanban containers can still be completed but cannot be retriggered.
    
    Parameters:
    
    kanbanCtrlCycleLifeCycleStatus - In Creation - The control cycle has been created without consistency check. It does not contain any kanban containers.
  - setCreationDate
```
public void setCreationDate(@Nullable
                            LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Parameters:
    
    creationDate - Date on which the control cycle is created. The creation date is set automatically when the control cycle is created.
  - setReleaseDate
```
public void setReleaseDate(@Nullable
                           LocalDateTime releaseDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ReleaseDate
    
    Parameters:
    
    releaseDate - Date on which the control cycle is released. This may also be a planned release date. The release date is set automatically when the control cycle is released.
  - setLockDate
```
public void setLockDate(@Nullable
                        LocalDateTime lockDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LockDate
    
    Parameters:
    
    lockDate - Date on which the control cycle is locked. This may be a planned lock date. The lock date is set automatically when the control cycle is locked.
  - setPullIntervalInWorkdays
```
public void setPullIntervalInWorkdays(@Nullable
                                      BigDecimal pullIntervalInWorkdays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    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.
    
    Parameters:
    
    pullIntervalInWorkdays - Time interval between the transfer of requirements from the consumer (demand source) to the supply source or the interval between the times of delivery by the supply source to the consumer.
  - setPullIntervalInMinutes
```
public void setPullIntervalInMinutes(@Nullable
                                     BigDecimal pullIntervalInMinutes)
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    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.
    
    Parameters:
    
    pullIntervalInMinutes - Time interval between the transfer of requirements from the consumer (demand source) to the supply source 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.
  - setKanbanCtnRefillTimeInDays
```
public void setKanbanCtnRefillTimeInDays(@Nullable
                                         BigDecimal kanbanCtnRefillTimeInDays)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: KanbanCtnRefillTimeInDays
    The refill time is a constituent of the replenishment lead time. You can specify the number of days for the refill time with up to two decimal places. In calculating the replenishment lead time, the system adds up the individual values and rounds up to full days.The period for refilling the container starts at the time at which the consumer (demand source) sets the status of the kanban container to EMPTY and ends when the supply source sets it to IN TRANSIT. The refill time also includes the time during which the kanban container has the status IN PROCESS.
    
    Parameters:
    
    kanbanCtnRefillTimeInDays - Indicates the time taken to refill an empty kanban container.
  - setKanbanCtnRefillTmeInMinutes
```
public void setKanbanCtnRefillTmeInMinutes(@Nullable
                                           BigDecimal kanbanCtnRefillTmeInMinutes)
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: KanbanCtnRefillTmeInMinutes
    The refill time is a constituent of the replenishment lead time. You can specify the refill time in minutes. The system then calculates the replenishment lead time from the values you have specified for the refill time, transportation time, and wait time.The period for the refilling starts at the time the demand source (consumer) sets the status of the kanban container to EMPTY and ends when the supply source sets it to IN TRANSIT. The refill time also includes the time during which the kanban container has the status IN PROCESS.
    
    Parameters:
    
    kanbanCtnRefillTmeInMinutes - Indicates the time it takes to fill an empty kanban container. You can enter the minutes up to the maximum value 59999999.
  - setKanbanCtnWaitTimeInDays
```
public void setKanbanCtnWaitTimeInDays(@Nullable
                                       BigDecimal kanbanCtnWaitTimeInDays)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: KanbanCtnWaitTimeInDays
    The wait time is a constituent of the replenishment lead time. You can specify the number of days for the wait time with up to two decimal places. In calculating the replenishment lead time, the system adds up the individual values and rounds up to full days.The wait time is only relevant to control cycles with an independent supply source.
    
    Parameters:
    
    kanbanCtnWaitTimeInDays - Indicates the time taken to convert the status of a kanban container from WAITING to EMPTY.
  - setKanbanCtnWaitTimeInMinutes
```
public void setKanbanCtnWaitTimeInMinutes(@Nullable
                                          BigDecimal kanbanCtnWaitTimeInMinutes)
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: KanbanCtnWaitTimeInMinutes
    The wait time is a constituent of the replenishment lead time. You can specify the wait time in minutes. The system then calculates the replenishment lead time from the values you have specified for the refill time, transportation time, and wait time.The wait time is only relevant to control cycles with an independent supply source.
    
    Parameters:
    
    kanbanCtnWaitTimeInMinutes - Indicates the time it takes to change the status of a kanban container from WAITING to EMPTY. You can enter the minutes up to the maximum value 59999999.
  - setKanbanCtnTransportTimeInDays
```
public void setKanbanCtnTransportTimeInDays(@Nullable
                                            BigDecimal kanbanCtnTransportTimeInDays)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: KanbanCtnTransportTimeInDays
    The transportation time is a constituent of the replenishment lead time. You can specify the number of days for the transportation time with up to two decimal places. In calculating the replenishment lead time, the system adds up the individual values and rounds up to full days.The period for transportation starts at the time at which the supply source sets the status of the kanban container to IN TRANSIT and ends when the consumer sets it to FULL.
    
    Parameters:
    
    kanbanCtnTransportTimeInDays - Indicates the time taken to transport the kanban container from the supply source to the consumer (demand source).
  - setKanbanCtnTransportTmeInMinutes
```
public void setKanbanCtnTransportTmeInMinutes(@Nullable
                                              BigDecimal kanbanCtnTransportTmeInMinutes)
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: KanbanCtnTransportTmeInMinutes
    The transportation time is a constituent of the replenishment lead time. You can specify the transportation time in minutes. The system then calculates the replenishment lead time from the values you have specified for the refill time, transportation time, and wait time.The period for transportation starts at the time the supply source sets the status of the kanban container to IN TRANSIT and ends when the demand source (consumer) sets it to FULL.
    
    Parameters:
    
    kanbanCtnTransportTmeInMinutes - Indicates the time it takes to transport the kanban container from the supply source to the demand source (consumer). You can enter the minutes up to the maximum value 59999999.
  - setKnbnCtnCalcRqmtBufferInPercent
```
public void setKnbnCtnCalcRqmtBufferInPercent(@Nullable
                                              BigDecimal knbnCtnCalcRqmtBufferInPercent)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: KnbnCtnCalcRqmtBufferInPercent
    You can specify the requirement buffer in the calculation profile or in control cycle maintenance. The requirement buffer maintained in a control cycle overrides one specified in the calculation profile.The consumer (demand source) sends preview information about its expected consumption situation to the supplier (supply source). This advance information is frequently inexact. This inexactitude in the requirement values can be specified here as a percentage.
    
    Parameters:
    
    knbnCtnCalcRqmtBufferInPercent - Buffer used in the kanban calculation to compensate for inexactitudes in the requirement information. The percentage value specified here acts as a requirement buffer.
  - setKnbnCtnCalcSupplySrceBufInPct
```
public void setKnbnCtnCalcSupplySrceBufInPct(@Nullable
                                             BigDecimal knbnCtnCalcSupplySrceBufInPct)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: KnbnCtnCalcSupplySrceBufInPct
    You can specify the supply source buffer in the calculation profile or in control cycle maintenance. The source buffer maintained in a control cycle overrides one specified in the calculation profile.
    
    Parameters:
    
    knbnCtnCalcSupplySrceBufInPct - Buffer used in the kanban calculation to even out delivery fluctuations at the supply source.
  - setNrOfKanbanCtnsFlaggedToUnlock
```
public void setNrOfKanbanCtnsFlaggedToUnlock(@Nullable
                                             String nrOfKanbanCtnsFlaggedToUnlock)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NrOfKanbanCtnsFlaggedToUnlock
    The system generates kanbans flagged for unlocking only if you have made the setting Lock New Kanbans from Kanban Calculation or the setting Always Lock New Kanbans in the Lock New Kanbans field in the activity Define Strategies for Adopting Calculation Proposals in Customizing for Kanban.If you have made the setting Always Lock New Kanbans, as a basic rule, the last change determines the number of kanbans flagged for unlocking. If, for example, the kanban calculation has determined that three new containers have to be added, these three containers are flagged for unlocking. If you then manually add another two containers in transaction PKMC, a total of five containers are flagged for unlocking.The number of locked kanban containers can exceed the number of containers flagged for unlocking.
    
    Parameters:
    
    nrOfKanbanCtnsFlaggedToUnlock - Indicates the number of kanban containers in the control cycle that are flagged for unlocking.
  - setNrOfWaitingKnbnCtnsBfrReplnmt
```
public void setNrOfWaitingKnbnCtnsBfrReplnmt(@Nullable
                                             String nrOfWaitingKnbnCtnsBfrReplnmt)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NrOfWaitingKnbnCtnsBfrReplnmt
    The trigger point is a threshold value to initiate the replenishment of a material in the case of in-house production. You can stipulate the value manually or have it calculated by the system.Each time the consumer confirms the use of a kanban container, the system checks the number of kanbans of a control cycle that have the status "Waiting". As long as the quantity has not yet reached the value of the trigger point, the system likewise sets the affected kanban container to "Waiting". As soon as the trigger point is reached, the system sets these containers to "Empty", thus triggering replenishment. In this way, you ensure that the system does not set each container to "Empty" immediately. Instead it sets them to this status only in groups. You can thus avoid frequent resetup and improve capacity utilization.For you to be able to use the trigger point function, the following prerequisites must be satisfied:You have set the Take Capacity Situation Into Account indicator in Kanban Customizing in the IMG activity Define In-House Production Strategies.You have set the calculation type 1 on the Kanban Calculation tab page in control cycle maintenance.You have specified a planning work center on the Consideration of Capacity tab page.
    
    Parameters:
    
    nrOfWaitingKnbnCtnsBfrReplnmt - Shows the number of kanban containers that have the status Waiting. This number must first be reached before the system can trigger replenishment.
  - setKanbanCtrlCycReplnmtTriggerGrp
```
public void setKanbanCtrlCycReplnmtTriggerGrp(@Nullable
                                              String kanbanCtrlCycReplnmtTriggerGrp)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: KanbanCtrlCycReplnmtTriggerGrp
    Using trigger groups enables you to work on combine and produce together materials of the same kind. The system then makes no provision for setup times in the capacity-based kanban calculation in the case of a material changeover within a trigger group.All control cycles belonging to a trigger group have the same trigger point.
    
    Parameters:
    
    kanbanCtrlCycReplnmtTriggerGrp - Group of control cycles for materials of the same kind that are produced together at a planning work center and require the same setup state.
  - setPlanningWorkCenter
```
public void setPlanningWorkCenter(@Nullable
                                  String planningWorkCenter)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: PlanningWorkCenter
    The planning work center must be included in the routings used for the materials that are to be planned.
    
    Parameters:
    
    planningWorkCenter - Shows the work center for which the system is to carry out a consideration of capacity.
  - setProductionOrdersAreCombined
```
public void setProductionOrdersAreCombined(@Nullable
                                           Boolean productionOrdersAreCombined)
```
    Constraints: none
    Original property name from the Odata EDM: ProductionOrdersAreCombined
    
    Parameters:
    
    productionOrdersAreCombined - Combine Production Order
  - setLastChangeDateTime
```
public void setLastChangeDateTime(@Nullable
                                  ZonedDateTime lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    Parameters:
    
    lastChangeDateTime - Last Change Timestamp
  - getEntityCollection
```
protected String getEntityCollection()
```
    Specified by:
    
    getEntityCollection in class VdmEntity<KanbanControlCycle>
  - getKey
```
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<KanbanControlCycle>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<KanbanControlCycle>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<KanbanControlCycle>
  - field
```
@Nonnull
public static <T> KanbanControlCycleField<T> field(@Nonnull
                                                            String fieldName,
                                                            @Nonnull
                                                            Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Parameters:
    
    fieldName - The name of the extension field as returned by the OData service.
    
    fieldType - The Java type to use for the extension field when performing value comparisons.
    
    Returns:
    
    A representation of an extension field from this entity.
  - field
```
@Nonnull
public static <T,DomainT> KanbanControlCycleField<T> field(@Nonnull
                                                                    String fieldName,
                                                                    @Nonnull
                                                                    TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - toMapOfNavigationProperties
```
protected Map<String,Object> toMapOfNavigationProperties()
```
    Overrides:
    
    toMapOfNavigationProperties in class VdmObject<KanbanControlCycle>
  - fetchKanbanContainer
```
@Nonnull
public List<KanbanContainer> fetchKanbanContainer()
                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the KanbanContainer entities (one to many) associated with this entity. This corresponds to the OData navigation property to_KanbanContainer.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated KanbanContainer entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getKanbanContainerOrFetch
```
@Nonnull
public List<KanbanContainer> getKanbanContainerOrFetch()
                                                         throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated KanbanContainer entities (one to many). This corresponds to the OData navigation property to_KanbanContainer.
    If the navigation property to_KanbanContainer of a queried KanbanControlCycle is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated KanbanContainer entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getKanbanContainerIfPresent
```
@Nonnull
public Optional<List<KanbanContainer>> getKanbanContainerIfPresent()
```
    Retrieval of associated KanbanContainer entities (one to many). This corresponds to the OData navigation property to_KanbanContainer.
    If the navigation property for an entity KanbanControlCycle has not been resolved yet, this method will not query further information. Instead its Optional result state will be empty.
    
    Returns:
    
    If the information for navigation property to_KanbanContainer is already loaded, the result will contain the KanbanContainer entities. If not, an Optional with result state empty is returned.
  - setKanbanContainer
```
public void setKanbanContainer(@Nonnull
                               List<KanbanContainer> value)
```
    Overwrites the list of associated KanbanContainer entities for the loaded navigation property to_KanbanContainer.
    If the navigation property to_KanbanContainer of a queried KanbanControlCycle is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of KanbanContainer entities.
  - addKanbanContainer
```
public void addKanbanContainer(KanbanContainer... entity)
```
    Adds elements to the list of associated KanbanContainer entities. This corresponds to the OData navigation property to_KanbanContainer.
    If the navigation property to_KanbanContainer of a queried KanbanControlCycle is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of KanbanContainer entities.
  - builder
```
public static KanbanControlCycle.KanbanControlCycleBuilder builder()
```
  - getKanbanControlCycle
```
@Nullable
public String getKanbanControlCycle()
```
    (Key Field) Constraints: Not nullable, Maximum length: 7
    Original property name from the Odata EDM: KanbanControlCycle
    The following data is defined and linked in the kanban control cycle used in Kanban and JIT Outbound processing:Production supply areaMaterialNumber of kanbans or containers and the kanban quantity or call-off quantityReplenishment strategiesIf necessary, the source of replenishment depending on the replenishment strategy
    
    Returns:
    
    Number, that specifically identifies the control cycle.
  - getKanbanControlCycleCategory
```
@Nullable
public String getKanbanControlCycleCategory()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanControlCycleCategory
    
    Returns:
    
    Kanban Control Cycle Category
  - getProduct
```
@Nullable
public String getProduct()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Product
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getPlant
```
@Nullable
public String getPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
    
    Returns:
    
    Key uniquely identifying a plant.
  - getProductionVersion
```
@Nullable
public String getProductionVersion()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProductionVersion
    The production version determines the following:the BOM alternative for a BOM explosionthe task list type, the task list group and the task list group counter for allocation to task listslot-size restrictions for repetitive manufacturing
    
    Returns:
    
    Key which determines the various production techniques according to which a material can be manufactured.
  - getProductionSupplyArea
```
@Nullable
public String getProductionSupplyArea()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ProductionSupplyArea
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Returns:
    
    The production supply area (PSA) serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes.
  - getSupplySourceResponsiblePerson
```
@Nullable
public String getSupplySourceResponsiblePerson()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SupplySourceResponsiblePerson
    You define the key for the person responsible in Customizing for MRP under Master data -> Define MRP controllers.
    
    Returns:
    
    In in-house production, the responsible person defines the person that, as the Supply source, is in charge of the material provision.
  - getStorageLocation
```
@Nullable
public String getStorageLocation()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StorageLocation
    
    Returns:
    
    Storage Location
  - getStoringPositionName
```
@Nullable
public String getStoringPositionName()
```
    Constraints: Not nullable, Maximum length: 25
    Original property name from the Odata EDM: StoringPositionName
    
    Returns:
    
    Specifies the precise position (e.g. a certain shelf section) in which your material can be found in the supply area.
  - getKanbanContainerDeliveryAddress
```
@Nullable
public String getKanbanContainerDeliveryAddress()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: KanbanContainerDeliveryAddress
    
    Returns:
    
    Kanban Delivery Address
  - getProductCostCollector
```
@Nullable
public String getProductCostCollector()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ProductCostCollector
    
    Returns:
    
    Number that specifies the cost collector for Repetitive Manufacturing, order-related production and KANBAN.
  - getSupplier
```
@Nullable
public String getSupplier()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Supplier
    With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
    
    Returns:
    
    Alphanumeric key uniquely identifying the document.
  - getPurchasingOrganization
```
@Nullable
public String getPurchasingOrganization()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: PurchasingOrganization
    
    Returns:
    
    Purchasing Organization
  - getPurchaseOutlineAgreement
```
@Nullable
public String getPurchaseOutlineAgreement()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PurchaseOutlineAgreement
    
    Returns:
    
    Number of the outline agreement.
  - getPurchaseOutlineAgreementItem
```
@Nullable
public String getPurchaseOutlineAgreementItem()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: PurchaseOutlineAgreementItem
    
    Returns:
    
    Specifies the number that uniquely identifies an item in .
  - getWarehouse
```
@Nullable
public String getWarehouse()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: Warehouse
    All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
    
    Returns:
    
    Number that identifies a complex, physical warehouse structure within the Warehouse Management system.
  - getStorageType
```
@Nullable
public String getStorageType()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: StorageType
    A typical warehouse could have the following storage types:Goods receipt areaPicking areaHigh-rack storage areaBulk storage areaOpen storage areaGoods issue area
    
    Returns:
    
    The storage type is a subdivision of a complex, physical warehouse. Different storage types are identified by their warehousing technique, form of organization, or their function.
  - getStorageBin
```
@Nullable
public String getStorageBin()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: StorageBin
    A storage bin can be further sub-divided into bin sections. Several different materials (quants) can be stored in one bin at the same time.
    
    Returns:
    
    The storage bin (sometimes referred to as a "slot") is the smallest addressable unit in a warehouse. It identifies the exact location in the warehouse where goods can be stored.
  - getBaseUnit
```
@Nullable
public String getBaseUnit()
```
    Constraints: Not nullable, Maximum length: 3
    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.
    
    Returns:
    
    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.
  - getKanbanContainerQuantityInBsUnt
```
@Nullable
public BigDecimal getKanbanContainerQuantityInBsUnt()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: KanbanContainerQuantityInBsUnt
    Quantity of material (target quantity) that is specified for a kanban.Event-driven Kanban:Proposed value for the quantity of material in a kanban that is used by the system if no order quantity was entered when the kanban signal was generated.The quantity per kanban must be a whole multiple of the rounding quantity.JIT Outbound:Quantity of material that is used as a proposed call-off quantity. If a packing instruction is specified for the control cycle, the quantity is determined by its target quantity.
    
    Returns:
    
    Classic Kanban:
  - getNumberOfKanbanContainers
```
@Nullable
public String getNumberOfKanbanContainers()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NumberOfKanbanContainers
    
    Returns:
    
    The number of kanbans, which means containers, that circulate between the customer and source in the control cycle.
  - getMaxNrOfEmptyKanbanContainers
```
@Nullable
public String getMaxNrOfEmptyKanbanContainers()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: MaxNrOfEmptyKanbanContainers
    This setting is only relevant to control cycles for classic kanban.
    
    Returns:
    
    Maximum number of kanbans that are allowed to be empty. Once this limit has been reached, the kanbans must be filled up again.
  - getInHouseProductionReplnmtStrgy
```
@Nullable
public String getInHouseProductionReplnmtStrgy()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InHouseProductionReplnmtStrgy
    You use the replenishment strategy to define the following, for example:Whether replenishment is only triggered by kanbans or whether a procurement element is createdWhich movement type is used to post the goods receiptThe replenishment strategies are defined in Customizing for KANBAN. You then assign the appropriate replenishment strategy to the control cycle.
    
    Returns:
    
    The replenishment strategy defines how procurement in in-house production is to be carried out.
  - getMaterialStaging
```
@Nullable
public String getMaterialStaging()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: MaterialStaging
    As with the location coordinates (warehouse number, storage type, and storage bin), the system files this indicator in the control cycle.The following staging types are supported:"1": Pick partsThese materials are picked according to the required quantity specified in the production order."2": Crate or kanban partsThese materials are always removed from the warehouse in full cases. These can be ordered, for example, as soon as a case of needed parts is emptied in production."3": Release order partsRelease order parts are scheduled individually and the quantities are supplied manually to replenishment storage bins based on the requirements of production orders and the stock levels in the scheduled production supply areas."4": Manual stagingMaterials are staged manually. For example, you can transport individual components using manually created transfer orders, or you can use the bypass method to transport them directly from the goods receipt zone to production. In goods receipt posting, postings are made to the production storage bins from the control cycles."0": Not relevant to WM-PPThese materials are not relevant to WM staging. They cannot be requested using the WM system.
    
    Returns:
    
    The material staging indicator defines the method of how needed materials can be supplied for production with the assistance of the Warehouse Management system.
  - getDestinationBinIsDynamic
```
@Nullable
public Boolean getDestinationBinIsDynamic()
```
    Constraints: none
    Original property name from the Odata EDM: DestinationBinIsDynamic
    The dynamic bin coordinate is usually used to manage the stock figures in the interim storage areas separately according to requirement tracking numbers (for example, cost center, deliveries).
    
    Returns:
    
    Means that the destination storage bin will be generated dynamically for this goods transfer.
  - getExtProcurementReplnmtStrgy
```
@Nullable
public String getExtProcurementReplnmtStrgy()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ExtProcurementReplnmtStrgy
    You use the replenishment strategy to define the following, for example:Which procurement element is to be used to carry out procurementWhich movement type is to be used to post the goods receiptYou define the replenishment strategies in Customizing for KANBAN. You then assign the appropriate replenishment strategy to the control cycle.
    
    Returns:
    
    The replenishment strategy defines exactly how procurement using external procurement procedures is to be carried out.
  - getStockTransferReplnmtStrategy
```
@Nullable
public String getStockTransferReplnmtStrategy()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StockTransferReplnmtStrategy
    You use the replenishment strategy to define the following, for example:Whether the stock transfer is to be carried out using a reservation, direct transfer posting or via the WM/PP interfaceWhich movement type is to be used to post the goods receiptYou define the replenishment strategies in Customizing for KANBAN. You then assign the appropriate replenishment strategy to the control cycle.
    
    Returns:
    
    The replenishment strategy defines exactly how procurement in stock transfer is to be carried out.
  - getReplnmtIsCtrldBySupplySource
```
@Nullable
public Boolean getReplnmtIsCtrldBySupplySource()
```
    Constraints: none
    Original property name from the Odata EDM: ReplnmtIsCtrldBySupplySource
    An independent supply source specifies itself how material replenishment is to be carried out. That is, it specifies independently when the delivery- or production-relevant replenishment element is to be created.If you check the box, the two operations Status Change Set to Empty and Trigger Replenishment are decoupled. In this case, it is not the consumer (demand source) that triggers the replenishment but the supply source. The consumer sets the kanban to "Empty" but no replenishment element is generated and the system automatically sets the kanban to the status "Waiting". The supply source then sets these kanbans to "Empty" on the kanban board, thus generating the replenishment elements. The independent supply source thus specifies the time of replenishment itself.Usually, the replenishment strategy is defined for the control cycle and is determined automatically when the kanban signal is triggered.
    
    Returns:
    
    You use this checkbox to specify that an independent supply source has been assigned to the control cycle.
  - getKanbanContainerPackggProduct
```
@Nullable
public String getKanbanContainerPackggProduct()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: KanbanContainerPackggProduct
    Containers are created with a master record in the material master.SAP recommends that you use the material type CONT to make the selection by containers easier.
    
    Returns:
    
    Material number of the container that is used for the control cycle.
  - getSeparateGRIsNeededIfSetToFull
```
@Nullable
public Boolean getSeparateGRIsNeededIfSetToFull()
```
    Constraints: none
    Original property name from the Odata EDM: SeparateGRIsNeededIfSetToFull
    The separate GR posting should be carried out, ifthe demand source posting is linked to an automatic GR posting, but the kanban does not arrive at the demand source immediately.The material arrives with a central goods receipt and is passed on to production later.If the selection is not set, the kanban status change automatically leads to a goods receipt posting in materials management. Likewise, the goods receipt posting usually leads to an automatic status change.
    
    Returns:
    
    This indicator determines that the goods receipt posting is separated from the kanban status change.
  - getCostCenter
```
@Nullable
public String getCostCenter()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CostCenter
    
    Returns:
    
    A key that uniquely identifies a cost center.
  - getSupplySourcePlant
```
@Nullable
public String getSupplySourcePlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SupplySourcePlant
    
    Returns:
    
    Plant that represents the supply source for kanban replenishment for stock transfer procedures from plant to plant or in-house production.
  - getKanbanContainerStatusSequence
```
@Nullable
public String getKanbanContainerStatusSequence()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: KanbanContainerStatusSequence
    If no status sequence is defined in the control cycle, the statuses "Full" and "Empty" must be used. All other statuses are optional. If the control cycle is defined with an independent supply source, the status "Waiting" is additionally a mandatory status.If a status sequence is defined in the control cycle and if a kanban signal (kanban status change) is triggered with no specification of the follow-on status, the system searches for the next mandatory or optional status in the status sequence. If you specify the follow-on status, the system can skip recommended statuses and you can also use optional statuses.For individual status changes within the status sequence, you can also specify whether activities defined by yourself (such as goods receipt, kanban print, user exit) are to be executed. In this case, you must maintain these own activities for the the status sequence in Customizing for Kanban.
    
    Returns:
    
    The status sequence defines which kanban statuses must, should, can, or must not be used in Kanban processing. The status sequence is assigned in the control cycle.
  - getKanbanCtnReplnmtTriggerLogic
```
@Nullable
public String getKanbanCtnReplnmtTriggerLogic()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanCtnReplnmtTriggerLogic
    By selecting another logic, you can instruct the system to trigger replenishment for a kanban B that is set to the inactive status "wait" if a signal is given for another kanban A.These signals for triggering replenishment include:Setting the status to "in use":Here, the replenishment is triggered for kanban B when kanban A is set to the status "in use".Setting the status to "wait"Here, the replenishment is triggered for kanban B when kanban A is set to the status "wait".Arriving at or exceeding the trigger quantity:Here, the replenishment is triggered for kanban B when the actual quantity of kanban A is reduced to the trigger quantity or falls below the trigger quantity due to the quantity signal. The trigger quantity must also be maintained in the control cycle.Then kanban A is first set to status "wait". The replenishment for kanban A is triggered when the appropriate signal is given for the subsequent kanban.The purpose of this special logic is to set up a so-called single-card kanban with with two kanbans in a control cycle. Because a kanban is set to the inactive status, "wait" for certain periods, the stocks at the demand source can be further reduced - which is especially useful if the material is not always required.
    
    Returns:
    
    Usually the replenishment for a kanban is triggered if the kanban is set to the status, "empty".
  - getKnbnCtnReplnmtTrggrQtyInBsUnt
```
@Nullable
public BigDecimal getKnbnCtnReplnmtTrggrQtyInBsUnt()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: KnbnCtnReplnmtTrggrQtyInBsUnt
    If in KANBAN production control, you work with the quantity signal, then the quantity in a kanban is reduced by the quantity signal. If replenishment is not to be triggered when the kanban quantity is zero, but instead as soon as the quantity is reduced to the trigger quantity, then the system triggers replenishment for another kanban with the status, WAIT when the container quantity actually reaches or exceeds the trigger quantity.This field can be used for information purposes for the trigger logics for replenishment listed below (however it has no function):triggering replenishment at status IN USE andtriggering replenishment at status WAIT
    
    Returns:
    
    If you want to trigger replenishment when the trigger quantity is exceeded, you must define the trigger quantity here.
  - getKanbanContainerCalculationType
```
@Nullable
public String getKanbanContainerCalculationType()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanContainerCalculationType
    The formulas for the kanban calculation are as follows:Number of kanbans = (( RT * AC) / CONT) * SF * SB + CQuantity per kanban = ((RT * AC) / (AK-C) * SF * SBKey to abbreviations: AK: Number of kanbansCONT: Quantity per kanbanRT: Replenishment lead time per kanban(the replenishment lead time also includes the pull interval)AC: Consumption per unit of time(also includes the calendar buffer, requirement buffer and requirement fluctuations)SF: Safety factor (default value 1)SB: Supply source bufferC: Constant (default value 1)
    
    Returns:
    
    The calculation type controls whether the number of kanbans or the quantity per kanban is to be calculated.
  - getKanbanCtnCalcSafetyFactor
```
@Nullable
public BigDecimal getKanbanCtnCalcSafetyFactor()
```
    Constraints: Not nullable, Precision: 5, Scale: 3
    Original property name from the Odata EDM: KanbanCtnCalcSafetyFactor
    The formulas for the kanban calculation are as follows:Number of kanbans = (( RT * AC) / CONT) * SF * SB + CQuantity per kanban = ((RT * AC) / (AK-C) * SF * SBKey to abbreviations: AK: Number of kanbansCONT: Quantity per kanbanRT: Replenishment lead time per kanban(the replenishment lead time also includes the pull interval)AC: Consumption per unit of time(also includes the calendar buffer, requirement buffer and requirement fluctuations)SF: Safety factor (default value 1)SB: Supply source bufferC: Constant (default value 1)
    
    Returns:
    
    The safety factor is used to cater for fluctuations in requirements. It is multiplied by the result of the kanban calculation formula.
  - getKanbanCtnCalculationConstant
```
@Nullable
public Short getKanbanCtnCalculationConstant()
```
    Constraints: none
    Original property name from the Odata EDM: KanbanCtnCalculationConstant
    If a kanban is reported empty when all the material in the kanban has been used up, the constant is set to 1.If several work centers are served by one production supply area when kanbans are reported empty in this way, the constant must be increased by the number of work centers.If, on the other hand, the kanban is reported empty as soon as the first part is withdrawn, the constant is 0.You can also use this constant to plan a safety stock.
    
    Returns:
    
    Depending on how Kanban is used in production, you set the constant in the following way:
  - getKanbanCtnRoundingQtyInBsUnt
```
@Nullable
public BigDecimal getKanbanCtnRoundingQtyInBsUnt()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: KanbanCtnRoundingQtyInBsUnt
    Event-driven control cyclesThe kanban signal triggers the system to round the requested material quantity for this kanban up to the next whole multiple of the rounding quantity.The rounding quantity must be a multiple of the fixed kanban quantity.The kanban calculationThe kanban quantity calculated is rounded up to the next whole multiple of the rounding quantity.
    
    Returns:
    
    The rounding quantity is relevant for:
  - getFixedKanbanContainerQtyInBsUnt
```
@Nullable
public BigDecimal getFixedKanbanContainerQtyInBsUnt()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: FixedKanbanContainerQtyInBsUnt
    Using the fixed kanban quantity, you can define a precise quantity of material per kanban. This has the same effect as a fixed lot size and kanbans are only created for this fixed material quantity.If you enter a required quantity less than the fixed kanban quantity, the system creates a kanban for the fixed kanban quantity.If you enter a quantity greater than the fixed kanban quantity, the system creates several kanbans for the fixed quantity until the required quantity is covered. Here, if necessary, the required quantity is rounded up to a complete multiple of the fixed quantity. This means it is possible that more material is actually procured than was requested.
    
    Returns:
    
    The fixed kanban quantity is only relevant for event-driven control cycles.
  - getKanbanContainerCalcProfile
```
@Nullable
public String getKanbanContainerCalcProfile()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: KanbanContainerCalcProfile
    Calculation typeThe calculation type controls whether the number of kanbans or the quantity per kanban is calculated.Safety factorThe safety factor is used to offset requirement fluctuations proportionately. It is multiplied by the result of the formula for the kanban calculation.ConstantDepending on how Kanban is used in production, you set the constant as follows:If a kanban is set to empty when the material in a kanban is completely used up, the constant is set to 1.In this case, if several work centers use material from a production supply area, you must increase the constant by the number of work centers.If, however, the kanban is set to empty as soon as the first part is taken out, the constant is 0.You can also use the constants to plan a safety stock.Smoothing typeYou use the smoothing type to specify whether dependent requirements in the period of examination are:Not smoothedSmoothed within the period of a weekSmoothed according to a predefined distribution functionFactory calendar, Grouping, Shift programThese parameters are necessary if you have maintained a sub-day replenishment lead time in the control cycle. From the shift sequence, the system calculates the average daily worktime for the conversion of the exact-to-the-day dependent requirement quantity to the quantity per replenishment lead time.
    
    Returns:
    
    In the calculation profile, you can store the data for the automatic calculation of the kanban circulation:
  - getReplnmtLeadTimeInWorkdays
```
@Nullable
public BigDecimal getReplnmtLeadTimeInWorkdays()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: ReplnmtLeadTimeInWorkdays
    You can specify either the overall value for the replenishment lead time or its individual constituents (refill time, wait time, transportation time). In the latter case, the system totals up the three constituent parts and rounds the value up to a whole number.The replenishment lead time in days is used for the kanban calculation if the replenishment lead time in hours/minutes has not been maintained or no working times have been maintained in the associated calculation profile. The replenishment lead time in hours/minutes takes priority over the replenishment lead time in days, i.e. the system uses the replenishment lead time in hours/minutes as soon as you specify this value, irrespective of what you have specified for the replenishment lead time in days.In the case of control cycles for in-house production or external procurement, this time only has to be maintained if it differs from the in-house production time or planned delivery time maintained in the material master record. The goods receipt processing time is not taken into account.In control cycles for stock transfers, as a basic rule, you must always specify a replenishment lead time.
    
    Returns:
    
    Indicates the replenishment lead time in days.
  - getReplnmtLeadTimeInMinutes
```
@Nullable
public BigDecimal getReplnmtLeadTimeInMinutes()
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: ReplnmtLeadTimeInMinutes
    The replenishment lead time in minutes is used in the kanban calculation. The replenishment lead time in minutes takes priority over the replenishment lead time in days, that is to say, the system uses the replenishment lead time in minutes as soon as you have specified this value, irrespective of what you specified for the replenishment lead time in days.You can specify either the overall value for the replenishment lead time or the values for its individual constituents (refill time, wait time, and transportation time). In the latter case, the system calculates the total from the three constituent parts.A sub-day replenishment lead time can be used for the kanban calculation only if you have maintained working times resulting from a shift sequence in the associated calculation profile.
    
    Returns:
    
    Indicates the replenishment lead time in hours and minutes. You can enter the minutes up to the maximum value 59999999.
  - getSalesSchedulingAgreement
```
@Nullable
public String getSalesSchedulingAgreement()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesSchedulingAgreement
    If you have determined in the replenishment strategy, that you will deliver your material directly to a customer via a SD scheduling agreement, then enter here the number of your SD scheduling agreement for the material here.
    
    Returns:
    
    Number of the SD scheduling agreement.
  - getSalesSchedulingAgreementItem
```
@Nullable
public String getSalesSchedulingAgreementItem()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesSchedulingAgreementItem
    Enter the scheduling agreement item of your SD scheduling agreement here.
    
    Returns:
    
    Represents the item in the scheduling agreement.
  - getSourceProductionSupplyArea
```
@Nullable
public String getSourceProductionSupplyArea()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SourceProductionSupplyArea
    A supply area can be the supply source in a stock transfer, if the delivering storage location is divided into supply areas again. This is the case if the warehouse is supplied via Kanban (multi-level control cycles).
    
    Returns:
    
    Determines the supply area, which acts as a supply source in stock transfer.
  - getJITCallProfile
```
@Nullable
public String getJITCallProfile()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: JITCallProfile
    You determine the following in the JIT call profile:the type of call (at present only summarized JIT call available)the partner function, through which you define the output partner for determining the transmission of the JIT call.Through the output partner you can control the grouping of JIT calls and telecommunications.the type of groupingYou can group material requirements according to plant or according to plant and unloading point.the time definitionHere you control the grouping of material requirements according to delivery date.So in the profile you determine the basic information for creating a call.In the control cycle you have a JIT call profile and a kanban-replenishment strategy with control type summarized JIT call.
    
    Returns:
    
    Controls the creation of a JIT call.
  - getPackingInstruction
```
@Nullable
public UUID getPackingInstruction()
```
    Constraints: none
    Original property name from the Odata EDM: PackingInstruction
    
    Returns:
    
    Unique identification number for a packing object.
  - getNumberOfLoadCarriers
```
@Nullable
public String getNumberOfLoadCarriers()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NumberOfLoadCarriers
    The replenishment strategy in the control cycle determines whether one kanban is created from the number of load carriers you entered or whether one kanban corresponds to one load carrier. In the last instance, the number of load carriers corresponds to the number of kanbans you requested.Automatic Supply-to-Production:This quantity is multiplied by the call quantity and is used as the minimum quantity for replenishment proposals.
    
    Returns:
    
    Specifies the number of load carriers you can order with one call.
  - getBackflushReportingPoint
```
@Nullable
public String getBackflushReportingPoint()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BackflushReportingPoint
    In this field, enter the reporting point for which you want to execute the backflush. If you do not specify a reporting point here and execute the posting, the system lists all the existing reporting points for the production version in the dialog box entitled, Reporting Point Selection.You can only enter a reporting point after you have selected the indicator RP backflush selected.
    
    Returns:
    
    The reporting point specifies an operation for which a backflush should be executed.
  - getKanbanCtrlCycleLifeCycleStatus
```
@Nullable
public String getKanbanCtrlCycleLifeCycleStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: KanbanCtrlCycleLifeCycleStatus
    Created - The control cycle has been created consistently and is ready for productive use. The kanban containers have the status Locked and cannot be unlocked.Released - The control cycle has been released and is in productive use. The kanban containers can be unlocked.Locked - The control cycle is to be excluded from productive use. The kanban containers have the status Locked and cannot be unlocked. The replenishment process with the kanban containers can still be completed but cannot be retriggered.
    
    Returns:
    
    In Creation - The control cycle has been created without consistency check. It does not contain any kanban containers.
  - getCreationDate
```
@Nullable
public LocalDateTime getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    Date on which the control cycle is created. The creation date is set automatically when the control cycle is created.
  - getReleaseDate
```
@Nullable
public LocalDateTime getReleaseDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ReleaseDate
    
    Returns:
    
    Date on which the control cycle is released. This may also be a planned release date. The release date is set automatically when the control cycle is released.
  - getLockDate
```
@Nullable
public LocalDateTime getLockDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LockDate
    
    Returns:
    
    Date on which the control cycle is locked. This may be a planned lock date. The lock date is set automatically when the control cycle is locked.
  - getPullIntervalInWorkdays
```
@Nullable
public BigDecimal getPullIntervalInWorkdays()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    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.
    
    Returns:
    
    Time interval between the transfer of requirements from the consumer (demand source) to the supply source or the interval between the times of delivery by the supply source to the consumer.
  - getPullIntervalInMinutes
```
@Nullable
public BigDecimal getPullIntervalInMinutes()
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    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.
    
    Returns:
    
    Time interval between the transfer of requirements from the consumer (demand source) to the supply source 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.
  - getKanbanCtnRefillTimeInDays
```
@Nullable
public BigDecimal getKanbanCtnRefillTimeInDays()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: KanbanCtnRefillTimeInDays
    The refill time is a constituent of the replenishment lead time. You can specify the number of days for the refill time with up to two decimal places. In calculating the replenishment lead time, the system adds up the individual values and rounds up to full days.The period for refilling the container starts at the time at which the consumer (demand source) sets the status of the kanban container to EMPTY and ends when the supply source sets it to IN TRANSIT. The refill time also includes the time during which the kanban container has the status IN PROCESS.
    
    Returns:
    
    Indicates the time taken to refill an empty kanban container.
  - getKanbanCtnRefillTmeInMinutes
```
@Nullable
public BigDecimal getKanbanCtnRefillTmeInMinutes()
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: KanbanCtnRefillTmeInMinutes
    The refill time is a constituent of the replenishment lead time. You can specify the refill time in minutes. The system then calculates the replenishment lead time from the values you have specified for the refill time, transportation time, and wait time.The period for the refilling starts at the time the demand source (consumer) sets the status of the kanban container to EMPTY and ends when the supply source sets it to IN TRANSIT. The refill time also includes the time during which the kanban container has the status IN PROCESS.
    
    Returns:
    
    Indicates the time it takes to fill an empty kanban container. You can enter the minutes up to the maximum value 59999999.
  - getKanbanCtnWaitTimeInDays
```
@Nullable
public BigDecimal getKanbanCtnWaitTimeInDays()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: KanbanCtnWaitTimeInDays
    The wait time is a constituent of the replenishment lead time. You can specify the number of days for the wait time with up to two decimal places. In calculating the replenishment lead time, the system adds up the individual values and rounds up to full days.The wait time is only relevant to control cycles with an independent supply source.
    
    Returns:
    
    Indicates the time taken to convert the status of a kanban container from WAITING to EMPTY.
  - getKanbanCtnWaitTimeInMinutes
```
@Nullable
public BigDecimal getKanbanCtnWaitTimeInMinutes()
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: KanbanCtnWaitTimeInMinutes
    The wait time is a constituent of the replenishment lead time. You can specify the wait time in minutes. The system then calculates the replenishment lead time from the values you have specified for the refill time, transportation time, and wait time.The wait time is only relevant to control cycles with an independent supply source.
    
    Returns:
    
    Indicates the time it takes to change the status of a kanban container from WAITING to EMPTY. You can enter the minutes up to the maximum value 59999999.
  - getKanbanCtnTransportTimeInDays
```
@Nullable
public BigDecimal getKanbanCtnTransportTimeInDays()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: KanbanCtnTransportTimeInDays
    The transportation time is a constituent of the replenishment lead time. You can specify the number of days for the transportation time with up to two decimal places. In calculating the replenishment lead time, the system adds up the individual values and rounds up to full days.The period for transportation starts at the time at which the supply source sets the status of the kanban container to IN TRANSIT and ends when the consumer sets it to FULL.
    
    Returns:
    
    Indicates the time taken to transport the kanban container from the supply source to the consumer (demand source).
  - getKanbanCtnTransportTmeInMinutes
```
@Nullable
public BigDecimal getKanbanCtnTransportTmeInMinutes()
```
    Constraints: Not nullable, Precision: 8, Scale: 0
    Original property name from the Odata EDM: KanbanCtnTransportTmeInMinutes
    The transportation time is a constituent of the replenishment lead time. You can specify the transportation time in minutes. The system then calculates the replenishment lead time from the values you have specified for the refill time, transportation time, and wait time.The period for transportation starts at the time the supply source sets the status of the kanban container to IN TRANSIT and ends when the demand source (consumer) sets it to FULL.
    
    Returns:
    
    Indicates the time it takes to transport the kanban container from the supply source to the demand source (consumer). You can enter the minutes up to the maximum value 59999999.
  - getKnbnCtnCalcRqmtBufferInPercent
```
@Nullable
public BigDecimal getKnbnCtnCalcRqmtBufferInPercent()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: KnbnCtnCalcRqmtBufferInPercent
    You can specify the requirement buffer in the calculation profile or in control cycle maintenance. The requirement buffer maintained in a control cycle overrides one specified in the calculation profile.The consumer (demand source) sends preview information about its expected consumption situation to the supplier (supply source). This advance information is frequently inexact. This inexactitude in the requirement values can be specified here as a percentage.
    
    Returns:
    
    Buffer used in the kanban calculation to compensate for inexactitudes in the requirement information. The percentage value specified here acts as a requirement buffer.
  - getKnbnCtnCalcSupplySrceBufInPct
```
@Nullable
public BigDecimal getKnbnCtnCalcSupplySrceBufInPct()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: KnbnCtnCalcSupplySrceBufInPct
    You can specify the supply source buffer in the calculation profile or in control cycle maintenance. The source buffer maintained in a control cycle overrides one specified in the calculation profile.
    
    Returns:
    
    Buffer used in the kanban calculation to even out delivery fluctuations at the supply source.
  - getNrOfKanbanCtnsFlaggedToUnlock
```
@Nullable
public String getNrOfKanbanCtnsFlaggedToUnlock()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NrOfKanbanCtnsFlaggedToUnlock
    The system generates kanbans flagged for unlocking only if you have made the setting Lock New Kanbans from Kanban Calculation or the setting Always Lock New Kanbans in the Lock New Kanbans field in the activity Define Strategies for Adopting Calculation Proposals in Customizing for Kanban.If you have made the setting Always Lock New Kanbans, as a basic rule, the last change determines the number of kanbans flagged for unlocking. If, for example, the kanban calculation has determined that three new containers have to be added, these three containers are flagged for unlocking. If you then manually add another two containers in transaction PKMC, a total of five containers are flagged for unlocking.The number of locked kanban containers can exceed the number of containers flagged for unlocking.
    
    Returns:
    
    Indicates the number of kanban containers in the control cycle that are flagged for unlocking.
  - getNrOfWaitingKnbnCtnsBfrReplnmt
```
@Nullable
public String getNrOfWaitingKnbnCtnsBfrReplnmt()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NrOfWaitingKnbnCtnsBfrReplnmt
    The trigger point is a threshold value to initiate the replenishment of a material in the case of in-house production. You can stipulate the value manually or have it calculated by the system.Each time the consumer confirms the use of a kanban container, the system checks the number of kanbans of a control cycle that have the status "Waiting". As long as the quantity has not yet reached the value of the trigger point, the system likewise sets the affected kanban container to "Waiting". As soon as the trigger point is reached, the system sets these containers to "Empty", thus triggering replenishment. In this way, you ensure that the system does not set each container to "Empty" immediately. Instead it sets them to this status only in groups. You can thus avoid frequent resetup and improve capacity utilization.For you to be able to use the trigger point function, the following prerequisites must be satisfied:You have set the Take Capacity Situation Into Account indicator in Kanban Customizing in the IMG activity Define In-House Production Strategies.You have set the calculation type 1 on the Kanban Calculation tab page in control cycle maintenance.You have specified a planning work center on the Consideration of Capacity tab page.
    
    Returns:
    
    Shows the number of kanban containers that have the status Waiting. This number must first be reached before the system can trigger replenishment.
  - getKanbanCtrlCycReplnmtTriggerGrp
```
@Nullable
public String getKanbanCtrlCycReplnmtTriggerGrp()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: KanbanCtrlCycReplnmtTriggerGrp
    Using trigger groups enables you to work on combine and produce together materials of the same kind. The system then makes no provision for setup times in the capacity-based kanban calculation in the case of a material changeover within a trigger group.All control cycles belonging to a trigger group have the same trigger point.
    
    Returns:
    
    Group of control cycles for materials of the same kind that are produced together at a planning work center and require the same setup state.
  - getPlanningWorkCenter
```
@Nullable
public String getPlanningWorkCenter()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: PlanningWorkCenter
    The planning work center must be included in the routings used for the materials that are to be planned.
    
    Returns:
    
    Shows the work center for which the system is to carry out a consideration of capacity.
  - getProductionOrdersAreCombined
```
@Nullable
public Boolean getProductionOrdersAreCombined()
```
    Constraints: none
    Original property name from the Odata EDM: ProductionOrdersAreCombined
    
    Returns:
    
    Combine Production Order
  - getLastChangeDateTime
```
@Nullable
public ZonedDateTime getLastChangeDateTime()
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    Returns:
    
    Last Change Timestamp
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setErpConfigContext
```
public void setErpConfigContext(@Nullable
                                ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Overrides:
    
    setErpConfigContext in class VdmEntity<KanbanControlCycle>
    
    Parameters:
    
    erpConfigContext -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<KanbanControlCycle>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<KanbanControlCycle>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<KanbanControlCycle>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<KanbanControlCycle>

Class KanbanControlCycle

Nested Class Summary

Field Summary

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

Constructor Summary

Method Summary

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

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

KANBAN_CONTROL_CYCLE

KANBAN_CONTROL_CYCLE_CATEGORY

PRODUCT

PLANT

PRODUCTION_VERSION

PRODUCTION_SUPPLY_AREA

SUPPLY_SOURCE_RESPONSIBLE_PERSON

STORAGE_LOCATION

STORING_POSITION_NAME

KANBAN_CONTAINER_DELIVERY_ADDRESS

PRODUCT_COST_COLLECTOR

SUPPLIER

PURCHASING_ORGANIZATION

PURCHASE_OUTLINE_AGREEMENT

PURCHASE_OUTLINE_AGREEMENT_ITEM

WAREHOUSE

STORAGE_TYPE

STORAGE_BIN

BASE_UNIT

KANBAN_CONTAINER_QUANTITY_IN_BS_UNT

NUMBER_OF_KANBAN_CONTAINERS

MAX_NR_OF_EMPTY_KANBAN_CONTAINERS

IN_HOUSE_PRODUCTION_REPLNMT_STRGY

MATERIAL_STAGING

DESTINATION_BIN_IS_DYNAMIC

EXT_PROCUREMENT_REPLNMT_STRGY

STOCK_TRANSFER_REPLNMT_STRATEGY

REPLNMT_IS_CTRLD_BY_SUPPLY_SOURCE

KANBAN_CONTAINER_PACKGG_PRODUCT

SEPARATE_GR_IS_NEEDED_IF_SET_TO_FULL

COST_CENTER

SUPPLY_SOURCE_PLANT

KANBAN_CONTAINER_STATUS_SEQUENCE

KANBAN_CTN_REPLNMT_TRIGGER_LOGIC

KNBN_CTN_REPLNMT_TRGGR_QTY_IN_BS_UNT

KANBAN_CONTAINER_CALCULATION_TYPE

KANBAN_CTN_CALC_SAFETY_FACTOR

KANBAN_CTN_CALCULATION_CONSTANT

KANBAN_CTN_ROUNDING_QTY_IN_BS_UNT

FIXED_KANBAN_CONTAINER_QTY_IN_BS_UNT

KANBAN_CONTAINER_CALC_PROFILE

REPLNMT_LEAD_TIME_IN_WORKDAYS

REPLNMT_LEAD_TIME_IN_MINUTES

SALES_SCHEDULING_AGREEMENT

SALES_SCHEDULING_AGREEMENT_ITEM

SOURCE_PRODUCTION_SUPPLY_AREA

JIT_CALL_PROFILE

PACKING_INSTRUCTION

NUMBER_OF_LOAD_CARRIERS

BACKFLUSH_REPORTING_POINT

KANBAN_CTRL_CYCLE_LIFE_CYCLE_STATUS

CREATION_DATE

RELEASE_DATE

LOCK_DATE

PULL_INTERVAL_IN_WORKDAYS

PULL_INTERVAL_IN_MINUTES

KANBAN_CTN_REFILL_TIME_IN_DAYS

KANBAN_CTN_REFILL_TME_IN_MINUTES

KANBAN_CTN_WAIT_TIME_IN_DAYS

KANBAN_CTN_WAIT_TIME_IN_MINUTES

KANBAN_CTN_TRANSPORT_TIME_IN_DAYS

KANBAN_CTN_TRANSPORT_TME_IN_MINUTES

KNBN_CTN_CALC_RQMT_BUFFER_IN_PERCENT

KNBN_CTN_CALC_SUPPLY_SRCE_BUF_IN_PCT

NR_OF_KANBAN_CTNS_FLAGGED_TO_UNLOCK

NR_OF_WAITING_KNBN_CTNS_BFR_REPLNMT

KANBAN_CTRL_CYC_REPLNMT_TRIGGER_GRP

PLANNING_WORK_CENTER

PRODUCTION_ORDERS_ARE_COMBINED