OutbDeliveryItem (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<OutbDeliveryItem>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.outbounddelivery.OutbDeliveryItem

public class OutbDeliveryItem
extends VdmEntity<OutbDeliveryItem>

A_OutbDeliveryItemType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class OutbDeliveryItem.OutbDeliveryItemBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`OutbDeliveryItem.OutbDeliveryItemBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static OutbDeliveryItemField<BigDecimal>`	`ACTUAL_DELIVERED_QTY_IN_BASE_UNIT` Use with available fluent helpers to apply the ActualDeliveredQtyInBaseUnit field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`ACTUAL_DELIVERY_QUANTITY` Use with available fluent helpers to apply the ActualDeliveryQuantity field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP1` Use with available fluent helpers to apply the AdditionalCustomerGroup1 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP2` Use with available fluent helpers to apply the AdditionalCustomerGroup2 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP3` Use with available fluent helpers to apply the AdditionalCustomerGroup3 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP4` Use with available fluent helpers to apply the AdditionalCustomerGroup4 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP5` Use with available fluent helpers to apply the AdditionalCustomerGroup5 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_MATERIAL_GROUP1` Use with available fluent helpers to apply the AdditionalMaterialGroup1 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_MATERIAL_GROUP2` Use with available fluent helpers to apply the AdditionalMaterialGroup2 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_MATERIAL_GROUP3` Use with available fluent helpers to apply the AdditionalMaterialGroup3 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_MATERIAL_GROUP4` Use with available fluent helpers to apply the AdditionalMaterialGroup4 field to query operations.
`static OutbDeliveryItemField<String>`	`ADDITIONAL_MATERIAL_GROUP5` Use with available fluent helpers to apply the AdditionalMaterialGroup5 field to query operations.
`static OutbDeliveryItemSelectable`	`ALL_FIELDS` Selector for all available fields of OutbDeliveryItem.
`static OutbDeliveryItemField<String>`	`ALTERNATE_PRODUCT_NUMBER` Use with available fluent helpers to apply the AlternateProductNumber field to query operations.
`static OutbDeliveryItemField<String>`	`BASE_UNIT` Use with available fluent helpers to apply the BaseUnit field to query operations.
`static OutbDeliveryItemField<String>`	`BATCH` Use with available fluent helpers to apply the Batch field to query operations.
`static OutbDeliveryItemField<String>`	`BATCH_BY_SUPPLIER` Use with available fluent helpers to apply the BatchBySupplier field to query operations.
`static OutbDeliveryItemField<String>`	`BATCH_CLASSIFICATION` Use with available fluent helpers to apply the BatchClassification field to query operations.
`static OutbDeliveryItemField<String>`	`BOM_EXPLOSION` Use with available fluent helpers to apply the BOMExplosion field to query operations.
`static OutbDeliveryItemField<String>`	`BUSINESS_AREA` Use with available fluent helpers to apply the BusinessArea field to query operations.
`static OutbDeliveryItemField<String>`	`CONSUMPTION_POSTING` Use with available fluent helpers to apply the ConsumptionPosting field to query operations.
`static OutbDeliveryItemField<String>`	`CONTROLLING_AREA` Use with available fluent helpers to apply the ControllingArea field to query operations.
`static OutbDeliveryItemField<String>`	`COST_CENTER` Use with available fluent helpers to apply the CostCenter field to query operations.
`static OutbDeliveryItemField<String>`	`CREATED_BY_USER` Use with available fluent helpers to apply the CreatedByUser field to query operations.
`static OutbDeliveryItemField<Calendar>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static OutbDeliveryItemField<Calendar>`	`CREATION_TIME` Use with available fluent helpers to apply the CreationTime field to query operations.
`static OutbDeliveryItemField<String>`	`CUST_ENGINEERING_CHG_STATUS` Use with available fluent helpers to apply the CustEngineeringChgStatus field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_DOCUMENT` Use with available fluent helpers to apply the DeliveryDocument field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_DOCUMENT_ITEM` Use with available fluent helpers to apply the DeliveryDocumentItem field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_DOCUMENT_ITEM_CATEGORY` Use with available fluent helpers to apply the DeliveryDocumentItemCategory field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_DOCUMENT_ITEM_TEXT` Use with available fluent helpers to apply the DeliveryDocumentItemText field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_GROUP` Use with available fluent helpers to apply the DeliveryGroup field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_QUANTITY_UNIT` Use with available fluent helpers to apply the DeliveryQuantityUnit field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_RELATED_BILLING_STATUS` Use with available fluent helpers to apply the DeliveryRelatedBillingStatus field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`DELIVERY_TO_BASE_QUANTITY_DNMNTR` Use with available fluent helpers to apply the DeliveryToBaseQuantityDnmntr field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`DELIVERY_TO_BASE_QUANTITY_NMRTR` Use with available fluent helpers to apply the DeliveryToBaseQuantityNmrtr field to query operations.
`static OutbDeliveryItemField<String>`	`DELIVERY_VERSION` Use with available fluent helpers to apply the DeliveryVersion field to query operations.
`static OutbDeliveryItemField<String>`	`DEPARTMENT_CLASSIFICATION_BY_CUST` Use with available fluent helpers to apply the DepartmentClassificationByCust field to query operations.
`static OutbDeliveryItemField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static OutbDeliveryItemField<String>`	`DIVISION` Use with available fluent helpers to apply the Division field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`FIXED_SHIPG_PROCG_DURATION_IN_DAYS` Use with available fluent helpers to apply the FixedShipgProcgDurationInDays field to query operations.
`static OutbDeliveryItemField<String>`	`GL_ACCOUNT` Use with available fluent helpers to apply the GLAccount field to query operations.
`static OutbDeliveryItemField<String>`	`GOODS_MOVEMENT_REASON_CODE` Use with available fluent helpers to apply the GoodsMovementReasonCode field to query operations.
`static OutbDeliveryItemField<String>`	`GOODS_MOVEMENT_STATUS` Use with available fluent helpers to apply the GoodsMovementStatus field to query operations.
`static OutbDeliveryItemField<String>`	`GOODS_MOVEMENT_TYPE` Use with available fluent helpers to apply the GoodsMovementType field to query operations.
`static OutbDeliveryItemField<String>`	`HIGHER_LEVEL_ITEM` Use with available fluent helpers to apply the HigherLevelItem field to query operations.
`static OutbDeliveryItemField<String>`	`INSPECTION_LOT` Use with available fluent helpers to apply the InspectionLot field to query operations.
`static OutbDeliveryItemField<String>`	`INSPECTION_PARTIAL_LOT` Use with available fluent helpers to apply the InspectionPartialLot field to query operations.
`static OutbDeliveryItemField<String>`	`INTERCOMPANY_BILLING_STATUS` Use with available fluent helpers to apply the IntercompanyBillingStatus field to query operations.
`static OutbDeliveryItemField<String>`	`INTERNATIONAL_ARTICLE_NUMBER` Use with available fluent helpers to apply the InternationalArticleNumber field to query operations.
`static OutbDeliveryItemField<String>`	`INVENTORY_SPECIAL_STOCK_TYPE` Use with available fluent helpers to apply the InventorySpecialStockType field to query operations.
`static OutbDeliveryItemField<String>`	`INVENTORY_VALUATION_TYPE` Use with available fluent helpers to apply the InventoryValuationType field to query operations.
`static OutbDeliveryItemField<Boolean>`	`IS_COMPLETELY_DELIVERED` Use with available fluent helpers to apply the IsCompletelyDelivered field to query operations.
`static OutbDeliveryItemField<String>`	`IS_NOT_GOODS_MOVEMENTS_RELEVANT` Use with available fluent helpers to apply the IsNotGoodsMovementsRelevant field to query operations.
`static OutbDeliveryItemField<Boolean>`	`IS_SEPARATE_VALUATION` Use with available fluent helpers to apply the IsSeparateValuation field to query operations.
`static OutbDeliveryItemField<String>`	`ISSG_OR_RCVG_BATCH` Use with available fluent helpers to apply the IssgOrRcvgBatch field to query operations.
`static OutbDeliveryItemField<String>`	`ISSG_OR_RCVG_MATERIAL` Use with available fluent helpers to apply the IssgOrRcvgMaterial field to query operations.
`static OutbDeliveryItemField<String>`	`ISSG_OR_RCVG_SPCL_STOCK_IND` Use with available fluent helpers to apply the IssgOrRcvgSpclStockInd field to query operations.
`static OutbDeliveryItemField<String>`	`ISSG_OR_RCVG_STOCK_CATEGORY` Use with available fluent helpers to apply the IssgOrRcvgStockCategory field to query operations.
`static OutbDeliveryItemField<String>`	`ISSG_OR_RCVG_VALUATION_TYPE` Use with available fluent helpers to apply the IssgOrRcvgValuationType field to query operations.
`static OutbDeliveryItemField<String>`	`ISSUING_OR_RECEIVING_PLANT` Use with available fluent helpers to apply the IssuingOrReceivingPlant field to query operations.
`static OutbDeliveryItemField<String>`	`ISSUING_OR_RECEIVING_STORAGE_LOC` Use with available fluent helpers to apply the IssuingOrReceivingStorageLoc field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_BILLING_BLOCK_REASON` Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_BILLING_INCOMPLETION_STATUS` Use with available fluent helpers to apply the ItemBillingIncompletionStatus field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_DELIVERY_INCOMPLETION_STATUS` Use with available fluent helpers to apply the ItemDeliveryIncompletionStatus field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_GDS_MVT_INCOMPLETION_STS` Use with available fluent helpers to apply the ItemGdsMvtIncompletionSts field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_GENERAL_INCOMPLETION_STATUS` Use with available fluent helpers to apply the ItemGeneralIncompletionStatus field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`ITEM_GROSS_WEIGHT` Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_IS_BILLING_RELEVANT` Use with available fluent helpers to apply the ItemIsBillingRelevant field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`ITEM_NET_WEIGHT` Use with available fluent helpers to apply the ItemNetWeight field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_PACKING_INCOMPLETION_STATUS` Use with available fluent helpers to apply the ItemPackingIncompletionStatus field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_PICKING_INCOMPLETION_STATUS` Use with available fluent helpers to apply the ItemPickingIncompletionStatus field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`ITEM_VOLUME` Use with available fluent helpers to apply the ItemVolume field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_VOLUME_UNIT` Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
`static OutbDeliveryItemField<String>`	`ITEM_WEIGHT_UNIT` Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
`static OutbDeliveryItemField<Calendar>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static OutbDeliveryItemField<String>`	`LOADING_GROUP` Use with available fluent helpers to apply the LoadingGroup field to query operations.
`static OutbDeliveryItemField<Calendar>`	`MANUFACTURE_DATE` Use with available fluent helpers to apply the ManufactureDate field to query operations.
`static OutbDeliveryItemField<String>`	`MATERIAL` Use with available fluent helpers to apply the Material field to query operations.
`static OutbDeliveryItemField<String>`	`MATERIAL_BY_CUSTOMER` Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
`static OutbDeliveryItemField<String>`	`MATERIAL_FREIGHT_GROUP` Use with available fluent helpers to apply the MaterialFreightGroup field to query operations.
`static OutbDeliveryItemField<String>`	`MATERIAL_GROUP` Use with available fluent helpers to apply the MaterialGroup field to query operations.
`static OutbDeliveryItemField<Boolean>`	`MATERIAL_IS_BATCH_MANAGED` Use with available fluent helpers to apply the MaterialIsBatchManaged field to query operations.
`static OutbDeliveryItemField<Boolean>`	`MATERIAL_IS_INT_BATCH_MANAGED` Use with available fluent helpers to apply the MaterialIsIntBatchManaged field to query operations.
`static OutbDeliveryItemField<Integer>`	`NUMBER_OF_SERIAL_NUMBERS` Use with available fluent helpers to apply the NumberOfSerialNumbers field to query operations.
`static OutbDeliveryItemField<String>`	`ORDER_ID` Use with available fluent helpers to apply the OrderID field to query operations.
`static OutbDeliveryItemField<String>`	`ORDER_ITEM` Use with available fluent helpers to apply the OrderItem field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`ORIGINAL_DELIVERY_QUANTITY` Use with available fluent helpers to apply the OriginalDeliveryQuantity field to query operations.
`static OutbDeliveryItemField<String>`	`ORIGINALLY_REQUESTED_MATERIAL` Use with available fluent helpers to apply the OriginallyRequestedMaterial field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`OVERDELIV_TOLRTD_LMT_RATIO_IN_PCT` Use with available fluent helpers to apply the OverdelivTolrtdLmtRatioInPct field to query operations.
`static OutbDeliveryItemField<String>`	`PACKING_STATUS` Use with available fluent helpers to apply the PackingStatus field to query operations.
`static OutbDeliveryItemField<String>`	`PARTIAL_DELIVERY_IS_ALLOWED` Use with available fluent helpers to apply the PartialDeliveryIsAllowed field to query operations.
`static OutbDeliveryItemField<String>`	`PAYMENT_GUARANTEE_FORM` Use with available fluent helpers to apply the PaymentGuaranteeForm field to query operations.
`static OutbDeliveryItemField<String>`	`PICKING_CONFIRMATION_STATUS` Use with available fluent helpers to apply the PickingConfirmationStatus field to query operations.
`static OutbDeliveryItemField<String>`	`PICKING_CONTROL` Use with available fluent helpers to apply the PickingControl field to query operations.
`static OutbDeliveryItemField<String>`	`PICKING_STATUS` Use with available fluent helpers to apply the PickingStatus field to query operations.
`static OutbDeliveryItemField<String>`	`PLANT` Use with available fluent helpers to apply the Plant field to query operations.
`static OutbDeliveryItemField<String>`	`PRIMARY_POSTING_SWITCH` Use with available fluent helpers to apply the PrimaryPostingSwitch field to query operations.
`static OutbDeliveryItemField<Calendar>`	`PRODUCT_AVAILABILITY_DATE` Use with available fluent helpers to apply the ProductAvailabilityDate field to query operations.
`static OutbDeliveryItemField<Calendar>`	`PRODUCT_AVAILABILITY_TIME` Use with available fluent helpers to apply the ProductAvailabilityTime field to query operations.
`static OutbDeliveryItemField<String>`	`PRODUCT_CONFIGURATION` Use with available fluent helpers to apply the ProductConfiguration field to query operations.
`static OutbDeliveryItemField<String>`	`PRODUCT_HIERARCHY_NODE` Use with available fluent helpers to apply the ProductHierarchyNode field to query operations.
`static OutbDeliveryItemField<String>`	`PROFIT_CENTER` Use with available fluent helpers to apply the ProfitCenter field to query operations.
`static OutbDeliveryItemField<String>`	`PROFITABILITY_SEGMENT` Use with available fluent helpers to apply the ProfitabilitySegment field to query operations.
`static OutbDeliveryItemField<String>`	`PROOF_OF_DELIVERY_RELEVANCE_CODE` Use with available fluent helpers to apply the ProofOfDeliveryRelevanceCode field to query operations.
`static OutbDeliveryItemField<String>`	`PROOF_OF_DELIVERY_STATUS` Use with available fluent helpers to apply the ProofOfDeliveryStatus field to query operations.
`static OutbDeliveryItemField<Boolean>`	`QUANTITY_IS_FIXED` Use with available fluent helpers to apply the QuantityIsFixed field to query operations.
`static OutbDeliveryItemField<String>`	`RECEIVING_POINT` Use with available fluent helpers to apply the ReceivingPoint field to query operations.
`static OutbDeliveryItemField<String>`	`REFERENCE_DOCUMENT_LOGICAL_SYSTEM` Use with available fluent helpers to apply the ReferenceDocumentLogicalSystem field to query operations.
`static OutbDeliveryItemField<String>`	`REFERENCE_SD_DOCUMENT` Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
`static OutbDeliveryItemField<String>`	`REFERENCE_SD_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
`static OutbDeliveryItemField<String>`	`REFERENCE_SD_DOCUMENT_ITEM` Use with available fluent helpers to apply the ReferenceSDDocumentItem field to query operations.
`static OutbDeliveryItemField<String>`	`RETAIL_PROMOTION` Use with available fluent helpers to apply the RetailPromotion field to query operations.
`static OutbDeliveryItemField<String>`	`SALES_DOCUMENT_ITEM_TYPE` Use with available fluent helpers to apply the SalesDocumentItemType field to query operations.
`static OutbDeliveryItemField<String>`	`SALES_GROUP` Use with available fluent helpers to apply the SalesGroup field to query operations.
`static OutbDeliveryItemField<String>`	`SALES_OFFICE` Use with available fluent helpers to apply the SalesOffice field to query operations.
`static OutbDeliveryItemField<String>`	`SD_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the SDDocumentCategory field to query operations.
`static OutbDeliveryItemField<String>`	`SD_PROCESS_STATUS` Use with available fluent helpers to apply the SDProcessStatus field to query operations.
`static OutbDeliveryItemField<Calendar>`	`SHELF_LIFE_EXPIRATION_DATE` Use with available fluent helpers to apply the ShelfLifeExpirationDate field to query operations.
`static OutbDeliveryItemField<Calendar>`	`STATISTICS_DATE` Use with available fluent helpers to apply the StatisticsDate field to query operations.
`static OutbDeliveryItemField<String>`	`STOCK_TYPE` Use with available fluent helpers to apply the StockType field to query operations.
`static OutbDeliveryItemField<String>`	`STORAGE_BIN` Use with available fluent helpers to apply the StorageBin field to query operations.
`static OutbDeliveryItemField<String>`	`STORAGE_LOCATION` Use with available fluent helpers to apply the StorageLocation field to query operations.
`static OutbDeliveryItemField<String>`	`STORAGE_TYPE` Use with available fluent helpers to apply the StorageType field to query operations.
`static OutbDeliveryItemField<String>`	`SUBSEQUENT_MOVEMENT_TYPE` Use with available fluent helpers to apply the SubsequentMovementType field to query operations.
`static OutbDeliveryItemLink<OutbDeliveryDocFlow>`	`TO_DOCUMENT_FLOW` Use with available fluent helpers to apply the to_DocumentFlow navigation property to query operations.
`static OutbDeliveryItemLink<SerialNmbrDelivery>`	`TO_SERIAL_DELIVERY_ITEM` Use with available fluent helpers to apply the to_SerialDeliveryItem navigation property to query operations.
`static OutbDeliveryItemField<String>`	`TRANSPORTATION_GROUP` Use with available fluent helpers to apply the TransportationGroup field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`UNDERDELIV_TOLRTD_LMT_RATIO_IN_PCT` Use with available fluent helpers to apply the UnderdelivTolrtdLmtRatioInPct field to query operations.
`static OutbDeliveryItemField<Boolean>`	`UNLIMITED_OVERDELIVERY_IS_ALLOWED` Use with available fluent helpers to apply the UnlimitedOverdeliveryIsAllowed field to query operations.
`static OutbDeliveryItemField<BigDecimal>`	`VARBL_SHIPG_PROCG_DURATION_IN_DAYS` Use with available fluent helpers to apply the VarblShipgProcgDurationInDays field to query operations.
`static OutbDeliveryItemField<String>`	`WAREHOUSE` Use with available fluent helpers to apply the Warehouse field to query operations.
`static OutbDeliveryItemField<String>`	`WAREHOUSE_ACTIVITY_STATUS` Use with available fluent helpers to apply the WarehouseActivityStatus field to query operations.
`static OutbDeliveryItemField<String>`	`WAREHOUSE_STAGING_AREA` Use with available fluent helpers to apply the WarehouseStagingArea field to query operations.
`static OutbDeliveryItemField<String>`	`WAREHOUSE_STOCK_CATEGORY` Use with available fluent helpers to apply the WarehouseStockCategory field to query operations.
`static OutbDeliveryItemField<String>`	`WAREHOUSE_STORAGE_BIN` Use with available fluent helpers to apply the WarehouseStorageBin field to query operations.

Constructor Summary

Constructors
Constructor and Description
`OutbDeliveryItem()`
OutbDeliveryItem(BigDecimal actualDeliveredQtyInBaseUnit, String deliveryVersion, BigDecimal actualDeliveryQuantity, String additionalCustomerGroup1, String additionalCustomerGroup2, String additionalCustomerGroup3, String additionalCustomerGroup4, String additionalCustomerGroup5, String additionalMaterialGroup1, String additionalMaterialGroup2, String additionalMaterialGroup3, String additionalMaterialGroup4, String additionalMaterialGroup5, String alternateProductNumber, String baseUnit, String batch, String batchBySupplier, String batchClassification, String bOMExplosion, String businessArea, String consumptionPosting, String controllingArea, String costCenter, String createdByUser, Calendar creationDate, Calendar creationTime, String custEngineeringChgStatus, String deliveryDocument, String deliveryDocumentItem, String deliveryDocumentItemCategory, String deliveryDocumentItemText, String deliveryGroup, String deliveryQuantityUnit, String deliveryRelatedBillingStatus, BigDecimal deliveryToBaseQuantityDnmntr, BigDecimal deliveryToBaseQuantityNmrtr, String departmentClassificationByCust, String distributionChannel, String division, BigDecimal fixedShipgProcgDurationInDays, String gLAccount, String goodsMovementReasonCode, String goodsMovementStatus, String goodsMovementType, String higherLevelItem, String inspectionLot, String inspectionPartialLot, String intercompanyBillingStatus, String internationalArticleNumber, String inventorySpecialStockType, String inventoryValuationType, Boolean isCompletelyDelivered, String isNotGoodsMovementsRelevant, Boolean isSeparateValuation, String issgOrRcvgBatch, String issgOrRcvgMaterial, String issgOrRcvgSpclStockInd, String issgOrRcvgStockCategory, String issgOrRcvgValuationType, String issuingOrReceivingPlant, String issuingOrReceivingStorageLoc, String itemBillingBlockReason, String itemBillingIncompletionStatus, String itemDeliveryIncompletionStatus, String itemGdsMvtIncompletionSts, String itemGeneralIncompletionStatus, BigDecimal itemGrossWeight, String itemIsBillingRelevant, BigDecimal itemNetWeight, String itemPackingIncompletionStatus, String itemPickingIncompletionStatus, BigDecimal itemVolume, String itemVolumeUnit, String itemWeightUnit, Calendar lastChangeDate, String loadingGroup, Calendar manufactureDate, String material, String materialByCustomer, String materialFreightGroup, String materialGroup, Boolean materialIsBatchManaged, Boolean materialIsIntBatchManaged, Integer numberOfSerialNumbers, String orderID, String orderItem, BigDecimal originalDeliveryQuantity, String originallyRequestedMaterial, BigDecimal overdelivTolrtdLmtRatioInPct, String packingStatus, String partialDeliveryIsAllowed, String paymentGuaranteeForm, String pickingConfirmationStatus, String pickingControl, String pickingStatus, String plant, String primaryPostingSwitch, Calendar productAvailabilityDate, Calendar productAvailabilityTime, String productConfiguration, String productHierarchyNode, String profitabilitySegment, String profitCenter, String proofOfDeliveryRelevanceCode, String proofOfDeliveryStatus, Boolean quantityIsFixed, String receivingPoint, String referenceDocumentLogicalSystem, String referenceSDDocument, String referenceSDDocumentCategory, String referenceSDDocumentItem, String retailPromotion, String salesDocumentItemType, String salesGroup, String salesOffice, String sDDocumentCategory, String sDProcessStatus, Calendar shelfLifeExpirationDate, Calendar statisticsDate, String stockType, String storageBin, String storageLocation, String storageType, String subsequentMovementType, String transportationGroup, BigDecimal underdelivTolrtdLmtRatioInPct, Boolean unlimitedOverdeliveryIsAllowed, BigDecimal varblShipgProcgDurationInDays, String warehouse, String warehouseActivityStatus, String warehouseStagingArea, String warehouseStockCategory, String warehouseStorageBin, ErpConfigContext erpConfigContext, List<OutbDeliveryDocFlow> toDocumentFlow, SerialNmbrDelivery toSerialDeliveryItem)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addDocumentFlow(OutbDeliveryDocFlow... entity)` Adds elements to the list of associated OutbDeliveryDocFlow entities.
`static OutbDeliveryItem.OutbDeliveryItemBuilder`	`builder()`
`boolean`	`equals(Object o)`
`List<OutbDeliveryDocFlow>`	`fetchDocumentFlow()` Fetches the OutbDeliveryDocFlow entities (one to many) associated with this entity.
`SerialNmbrDelivery`	`fetchSerialDeliveryItem()` Fetches the SerialNmbrDelivery entity (one to one) associated with this entity.
`static <T> OutbDeliveryItemField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`BigDecimal`	`getActualDeliveredQtyInBaseUnit()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getActualDeliveryQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3 The delivery quantity may be proposed from a sales order item.
`String`	`getAdditionalCustomerGroup1()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup2()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup3()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup4()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup5()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalMaterialGroup1()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup2()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup3()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup4()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup5()` Constraints: Not nullable, Maximum length: 3
`String`	`getAlternateProductNumber()` Constraints: Not nullable, Maximum length: 40 It does not need to be created as its own material master in the ERP system.
`String`	`getBaseUnit()` Constraints: Not nullable, Maximum length: 3 You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.
`String`	`getBatch()` Constraints: Not nullable, Maximum length: 10
`String`	`getBatchBySupplier()` Constraints: Not nullable, Maximum length: 15
`String`	`getBatchClassification()` Constraints: Not nullable, Maximum length: 18 You are required by the authorities (for example, the Food and Drug Authority in the USA) to keep a record of the selection values used to locate a particular batch so that you are always able to compare these values with the original specifications.
`String`	`getBOMExplosion()` Constraints: Not nullable, Maximum length: 8
`String`	`getBusinessArea()` Constraints: Not nullable, Maximum length: 4
`String`	`getConsumptionPosting()` Constraints: Not nullable, Maximum length: 1 The indicator is used in the case of goods receipts for purchase orders and is derived from the account assignment category of the purchase order.
`String`	`getControllingArea()` Constraints: Not nullable, Maximum length: 4 The controlling area is the highest organizational unit in Controlling.
`String`	`getCostCenter()` Constraints: Not nullable, Maximum length: 10
`String`	`getCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`Calendar`	`getCreationDate()` Constraints: Not nullable, Precision: 7
`Calendar`	`getCreationTime()` Constraints: Not nullable, Precision: 0
`String`	`getCustEngineeringChgStatus()` Constraints: Not nullable, Maximum length: 17 The customer sends this number in with a material number to request an engineering change to take effect as of a certain delivery date or cumulative quantity.
`String`	`getDeliveryDocument()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getDeliveryDocumentItem()` (Key Field) Constraints: Not nullable, Maximum length: 6
`String`	`getDeliveryDocumentItemCategory()` Constraints: Not nullable, Maximum length: 4 The delivery item category determines how the system processes an item.
`String`	`getDeliveryDocumentItemText()` Constraints: Not nullable, Maximum length: 40 Short texts are used throughout sales order processing, shipping, and billing.
`String`	`getDeliveryGroup()` Constraints: Not nullable, Maximum length: 3 The system uses delivery groups to check the availability of items that should be delivered together.
`String`	`getDeliveryQuantityUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getDeliveryRelatedBillingStatus()` Constraints: Not nullable, Maximum length: 1 The status line tells you if the item is not yet billed, is partly billed, is completely billed, or is not relevant for billing.
`BigDecimal`	`getDeliveryToBaseQuantityDnmntr()` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`BigDecimal`	`getDeliveryToBaseQuantityNmrtr()` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`String`	`getDeliveryVersion()` Constraints: Not nullable, Maximum length: 4
`String`	`getDepartmentClassificationByCust()` Constraints: Not nullable, Maximum length: 4
`String`	`getDistributionChannel()` Constraints: Not nullable, Maximum length: 2 You can maintain information about customers and materials by sales organization and distribution channel.
`String`	`getDivision()` Constraints: Not nullable, Maximum length: 2 A product or service is always assigned to just one division.
`List<OutbDeliveryDocFlow>`	`getDocumentFlowOrFetch()` Retrieval of associated OutbDeliveryDocFlow entities (one to many).
`com.google.common.base.Optional<List<OutbDeliveryDocFlow>>`	`getDocumentFlowOrNull()` Retrieval of associated OutbDeliveryDocFlow entities (one to many).
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`BigDecimal`	`getFixedShipgProcgDurationInDays()` Constraints: Not nullable, Precision: 5, Scale: 2
`String`	`getGLAccount()` Constraints: Not nullable, Maximum length: 10
`String`	`getGoodsMovementReasonCode()` Constraints: Not nullable, Maximum length: 4 Please do not change the entry in this field.
`String`	`getGoodsMovementStatus()` Constraints: Not nullable, Maximum length: 1 The status provides the following information: For an outbound delivery, the status informs you whether the item has already left the warehouse or company premises, or still being processed.
`String`	`getGoodsMovementType()` Constraints: Not nullable, Maximum length: 3
`String`	`getHigherLevelItem()` Constraints: Not nullable, Maximum length: 6 Items can be organized hierarchically.
`String`	`getInspectionLot()` Constraints: Not nullable, Maximum length: 12 The inspection lot number is assigned by the system.
`String`	`getInspectionPartialLot()` Constraints: Not nullable, Maximum length: 6 You can process partial lots by: Inspecting during production using inspection points Running a batch split for the delivery note
`String`	`getIntercompanyBillingStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getInternationalArticleNumber()` Constraints: Not nullable, Maximum length: 18
`String`	`getInventorySpecialStockType()` Constraints: Not nullable, Maximum length: 1 If you need to separately manage certain stock (for example, consignment stock) of a material, the stock type in question is defined using this indicator.
`String`	`getInventoryValuationType()` Constraints: Not nullable, Maximum length: 10 The valuation types allowed for a material are determined by the valuation category.
`Boolean`	`getIsCompletelyDelivered()` Constraints: none
`String`	`getIsNotGoodsMovementsRelevant()` Constraints: Not nullable, Maximum length: 1 When this indicator is set, goods movement is not posted for this item - regardless of the movement type assigned to it.
`Boolean`	`getIsSeparateValuation()` Constraints: none
`String`	`getIssgOrRcvgBatch()` Constraints: Not nullable, Maximum length: 10 The "receiving batch" is the number of the batch under which the quantity to be transferred is now to be recorded.
`String`	`getIssgOrRcvgMaterial()` Constraints: Not nullable, Maximum length: 40 The "receiving material" is the material number under which the quantity to be transferred is now to be recorded.
`String`	`getIssgOrRcvgSpclStockInd()` Constraints: Not nullable, Maximum length: 1 This indicator is used, for example, in the case of the physical transfer of a consignment material and when consignment material is transferred from the supplier's stock to the company's own stock.
`String`	`getIssgOrRcvgStockCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getIssgOrRcvgValuationType()` Constraints: Not nullable, Maximum length: 10
`String`	`getIssuingOrReceivingPlant()` Constraints: Not nullable, Maximum length: 4 The receiving plant is the plant or internal organizational unit that is to receive the goods.
`String`	`getIssuingOrReceivingStorageLoc()` Constraints: Not nullable, Maximum length: 4 The receiving storage location is the storage location that is to receive the goods.
`String`	`getItemBillingBlockReason()` Constraints: Not nullable, Maximum length: 2 The system can automatically propose a billing block for sales documents that must be checked before billing (for example, returns, credit and debit memo requests).
`String`	`getItemBillingIncompletionStatus()` Constraints: Not nullable, Maximum length: 1 The status line tells you to what extent the information necessary for billing the item is complete.
`String`	`getItemDeliveryIncompletionStatus()` Constraints: Not nullable, Maximum length: 1 The status line tells you if delivery-related item information is complete.
`String`	`getItemGdsMvtIncompletionSts()` Constraints: Not nullable, Maximum length: 1 The status provides information on how far the data required for billing the item is complete.
`String`	`getItemGeneralIncompletionStatus()` Constraints: Not nullable, Maximum length: 1 The status line tells you if all item information, necessary for further processing this item, is complete.
`BigDecimal`	`getItemGrossWeight()` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order.
`String`	`getItemIsBillingRelevant()` Constraints: Not nullable, Maximum length: 1 A: Relevant for delivery-related billing Billing is based on the outbound delivery.
`BigDecimal`	`getItemNetWeight()` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order.
`String`	`getItemPackingIncompletionStatus()` Constraints: Not nullable, Maximum length: 1 The status indicates the degree to which the data required for billing the item are complete.
`String`	`getItemPickingIncompletionStatus()` Constraints: Not nullable, Maximum length: 1 The status indicates whether the delivery-related item data is complete.
`BigDecimal`	`getItemVolume()` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order.
`String`	`getItemVolumeUnit()` Constraints: Not nullable, Maximum length: 3 If you specify a volume, you have to enter the corresponding volume unit here.
`String`	`getItemWeightUnit()` Constraints: Not nullable, Maximum length: 3 If you specify a weight, you must enter the corresponding unit of weight here.
`Calendar`	`getLastChangeDate()` Constraints: Not nullable, Precision: 7
`String`	`getLoadingGroup()` Constraints: Not nullable, Maximum length: 4 The system uses the loading group as well as the Shipping conditions and Delivering plant to automatically determine the shipping point for the item.
`Calendar`	`getManufactureDate()` Constraints: Not nullable, Precision: 7
`String`	`getMaterial()` Constraints: Not nullable, Maximum length: 40
`String`	`getMaterialByCustomer()` Constraints: Not nullable, Maximum length: 35 The customer's own identifier for a material can be stored in a customer-material info record and can be used to enter data during sales order processing.
`String`	`getMaterialFreightGroup()` Constraints: Not nullable, Maximum length: 8 Freight codes and classes in a freight code set are determined by the material freight group.
`String`	`getMaterialGroup()` Constraints: Not nullable, Maximum length: 9 You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
`Boolean`	`getMaterialIsBatchManaged()` Constraints: noneThis indicator can be set in the material master record manually or, if batches are valuated individually, it is set automatically for the plants concerned, in which case it cannot be changed.
`Boolean`	`getMaterialIsIntBatchManaged()` Constraints: none
`Integer`	`getNumberOfSerialNumbers()` Constraints: none
`String`	`getOrderID()` Constraints: Not nullable, Maximum length: 12
`String`	`getOrderItem()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getOriginalDeliveryQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3 When creating the inbound delivery, the notified quantity is transferred as the original quantity.
`String`	`getOriginallyRequestedMaterial()` Constraints: Not nullable, Maximum length: 40 If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
`BigDecimal`	`getOverdelivTolrtdLmtRatioInPct()` Constraints: Not nullable, Precision: 3, Scale: 1 If you have set the indicator in the Partial delivery/Item field to 'D' (partial delivery allowed), this takes priority.
`String`	`getPackingStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getPartialDeliveryIsAllowed()` Constraints: Not nullable, Maximum length: 1 You use this field to control partial deliveries at the item level.
`String`	`getPaymentGuaranteeForm()` Constraints: Not nullable, Maximum length: 2 The form of payment guarantee specifies how a sales document item is guaranteed.
`String`	`getPickingConfirmationStatus()` Constraints: Not nullable, Maximum length: 1 When you create a delivery with an item subject to pick/putaway confirmation, the item is assigned the status A (Subject to confirmation but not yet confirmed).
`String`	`getPickingControl()` Constraints: Not nullable, Maximum length: 1
`String`	`getPickingStatus()` Constraints: Not nullable, Maximum length: 1 The status message tells you whether the item is relevant for delivery.
`String`	`getPlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getPrimaryPostingSwitch()` Constraints: Not nullable, Maximum length: 1
`Calendar`	`getProductAvailabilityDate()` Constraints: Not nullable, Precision: 7 The system uses the material availability date to generate automatic production and purchasing requirements.
`Calendar`	`getProductAvailabilityTime()` Constraints: Not nullable, Precision: 0
`String`	`getProductConfiguration()` Constraints: Not nullable, Maximum length: 18 This number clearly identifies one particular configuration of a standard product.
`String`	`getProductHierarchyNode()` Constraints: Not nullable, Maximum length: 18 In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.
`String`	`getProfitabilitySegment()` Constraints: Not nullable, Maximum length: 10 Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
`String`	`getProfitCenter()` Constraints: Not nullable, Maximum length: 10
`String`	`getProofOfDeliveryRelevanceCode()` Constraints: Not nullable, Maximum length: 1 The indicator can have the following settings: ' ': not POD relevant 'A' : always POD relevant 'B' : only POD relevant when there are quantity differences The indicator is copied from the purchasing or sales document into the delivery, if control of POD relevance in the delivery item category is set to "Copy POD relevance from preceding document".
`String`	`getProofOfDeliveryStatus()` Constraints: Not nullable, Maximum length: 1 The status message informs you whether the ship-to party reported a proof of delivery for this item.
`Boolean`	`getQuantityIsFixed()` Constraints: noneSet this indicator if the quantity in a relational system does not change.
`String`	`getReceivingPoint()` Constraints: Not nullable, Maximum length: 25 Several receiving points can be defined for each plant.
`String`	`getReferenceDocumentLogicalSystem()` Constraints: Not nullable, Maximum length: 10
`String`	`getReferenceSDDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getReferenceSDDocumentCategory()` Constraints: Not nullable, Maximum length: 4
`String`	`getReferenceSDDocumentItem()` Constraints: Not nullable, Maximum length: 6
`String`	`getRetailPromotion()` Constraints: Not nullable, Maximum length: 10 For each item of a purchasing document, you can specify the promotion to which the item belongs.
`String`	`getSalesDocumentItemType()` Constraints: Not nullable, Maximum length: 1 The system processes items that refer to a specific material differently than items that do not refer to a material.
`String`	`getSalesGroup()` Constraints: Not nullable, Maximum length: 3 By using sales groups you can designate different areas of responsibility within a sales office.
`String`	`getSalesOffice()` Constraints: Not nullable, Maximum length: 4 When you create sales statistics, you can use a sales office as one of the selection criteria.
`String`	`getSDDocumentCategory()` Constraints: Not nullable, Maximum length: 4 The document category determines how the system stores and keeps track of document data.
`String`	`getSDProcessStatus()` Constraints: Not nullable, Maximum length: 1 The system determines the overall status from all statuses (for example, delivery and billing) for this item.
`SerialNmbrDelivery`	`getSerialDeliveryItemOrFetch()` Retrieval of associated SerialNmbrDelivery entity (one to one).
`com.google.common.base.Optional<SerialNmbrDelivery>`	`getSerialDeliveryItemOrNull()` Retrieval of associated SerialNmbrDelivery entity (one to one).
`Calendar`	`getShelfLifeExpirationDate()` Constraints: Not nullable, Precision: 7 You enter it yourself.
`Calendar`	`getStatisticsDate()` Constraints: Not nullable, Precision: 7 Write a user-exit if you require the system to copy the statistics date to the billing document.
`String`	`getStockType()` Constraints: Not nullable, Maximum length: 1 Possible stocks are: unrestricted-use stock (blank, F) stock in quality inspection (X, 2) blocked stock (S, 3) Select the corresponding indicator for the stock type required.
`String`	`getStorageBin()` Constraints: Not nullable, Maximum length: 10 A storage bin can be further sub-divided into bin sections.
`String`	`getStorageLocation()` Constraints: Not nullable, Maximum length: 4
`String`	`getStorageType()` Constraints: Not nullable, Maximum length: 3 A typical warehouse could have the following storage types: Goods receipt area Picking area High-rack storage area Bulk storage area Open storage area Goods issue area
`String`	`getSubsequentMovementType()` Constraints: Not nullable, Maximum length: 3
`String`	`getTransportationGroup()` Constraints: Not nullable, Maximum length: 4 Transportation groups are used for automatic route scheduling during sales order and delivery note processing.
`Class<OutbDeliveryItem>`	`getType()`
`BigDecimal`	`getUnderdelivTolrtdLmtRatioInPct()` Constraints: Not nullable, Precision: 3, Scale: 1
`Boolean`	`getUnlimitedOverdeliveryIsAllowed()` Constraints: none
`BigDecimal`	`getVarblShipgProcgDurationInDays()` Constraints: Not nullable, Precision: 5, Scale: 2 The system uses the variable during capacity planning for deliveries.
`String`	`getWarehouse()` Constraints: Not nullable, Maximum length: 3 All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number.
`String`	`getWarehouseActivityStatus()` Constraints: Not nullable, Maximum length: 1 If your delivery processing includes the SAP Warehouse Management (WM) system, the system automatically indicates the WM status for each item in a delivery.
`String`	`getWarehouseStagingArea()` Constraints: Not nullable, Maximum length: 10 Staging areas can be used for different purposes (at the same time, if necessary): o Goods issue o Goods receipt o Cross-docking processes o Direct distribution
`String`	`getWarehouseStockCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getWarehouseStorageBin()` Constraints: Not nullable, Maximum length: 10 This storage bin is only significant if you do not use SAP warehouse management.
`int`	`hashCode()`
`void`	`setActualDeliveredQtyInBaseUnit(BigDecimal actualDeliveredQtyInBaseUnit)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setActualDeliveryQuantity(BigDecimal actualDeliveryQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3 The delivery quantity may be proposed from a sales order item.
`void`	`setAdditionalCustomerGroup1(String additionalCustomerGroup1)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup2(String additionalCustomerGroup2)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup3(String additionalCustomerGroup3)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup4(String additionalCustomerGroup4)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup5(String additionalCustomerGroup5)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalMaterialGroup1(String additionalMaterialGroup1)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup2(String additionalMaterialGroup2)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup3(String additionalMaterialGroup3)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup4(String additionalMaterialGroup4)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup5(String additionalMaterialGroup5)` Constraints: Not nullable, Maximum length: 3
`void`	`setAlternateProductNumber(String alternateProductNumber)` Constraints: Not nullable, Maximum length: 40 It does not need to be created as its own material master in the ERP system.
`void`	`setBaseUnit(String baseUnit)` Constraints: Not nullable, Maximum length: 3 You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.
`void`	`setBatch(String batch)` Constraints: Not nullable, Maximum length: 10
`void`	`setBatchBySupplier(String batchBySupplier)` Constraints: Not nullable, Maximum length: 15
`void`	`setBatchClassification(String batchClassification)` Constraints: Not nullable, Maximum length: 18 You are required by the authorities (for example, the Food and Drug Authority in the USA) to keep a record of the selection values used to locate a particular batch so that you are always able to compare these values with the original specifications.
`void`	`setBOMExplosion(String bOMExplosion)` Constraints: Not nullable, Maximum length: 8
`void`	`setBusinessArea(String businessArea)` Constraints: Not nullable, Maximum length: 4
`void`	`setConsumptionPosting(String consumptionPosting)` Constraints: Not nullable, Maximum length: 1 The indicator is used in the case of goods receipts for purchase orders and is derived from the account assignment category of the purchase order.
`void`	`setControllingArea(String controllingArea)` Constraints: Not nullable, Maximum length: 4 The controlling area is the highest organizational unit in Controlling.
`void`	`setCostCenter(String costCenter)` Constraints: Not nullable, Maximum length: 10
`void`	`setCreatedByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(Calendar creationDate)` Constraints: Not nullable, Precision: 7
`void`	`setCreationTime(Calendar creationTime)` Constraints: Not nullable, Precision: 0
`void`	`setCustEngineeringChgStatus(String custEngineeringChgStatus)` Constraints: Not nullable, Maximum length: 17 The customer sends this number in with a material number to request an engineering change to take effect as of a certain delivery date or cumulative quantity.
`void`	`setDeliveryDocument(String deliveryDocument)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setDeliveryDocumentItem(String deliveryDocumentItem)` (Key Field) Constraints: Not nullable, Maximum length: 6
`void`	`setDeliveryDocumentItemCategory(String deliveryDocumentItemCategory)` Constraints: Not nullable, Maximum length: 4 The delivery item category determines how the system processes an item.
`void`	`setDeliveryDocumentItemText(String deliveryDocumentItemText)` Constraints: Not nullable, Maximum length: 40 Short texts are used throughout sales order processing, shipping, and billing.
`void`	`setDeliveryGroup(String deliveryGroup)` Constraints: Not nullable, Maximum length: 3 The system uses delivery groups to check the availability of items that should be delivered together.
`void`	`setDeliveryQuantityUnit(String deliveryQuantityUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setDeliveryRelatedBillingStatus(String deliveryRelatedBillingStatus)` Constraints: Not nullable, Maximum length: 1 The status line tells you if the item is not yet billed, is partly billed, is completely billed, or is not relevant for billing.
`void`	`setDeliveryToBaseQuantityDnmntr(BigDecimal deliveryToBaseQuantityDnmntr)` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`void`	`setDeliveryToBaseQuantityNmrtr(BigDecimal deliveryToBaseQuantityNmrtr)` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`void`	`setDeliveryVersion(String deliveryVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setDepartmentClassificationByCust(String departmentClassificationByCust)` Constraints: Not nullable, Maximum length: 4
`void`	`setDistributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2 You can maintain information about customers and materials by sales organization and distribution channel.
`void`	`setDivision(String division)` Constraints: Not nullable, Maximum length: 2 A product or service is always assigned to just one division.
`void`	`setDocumentFlow(List<OutbDeliveryDocFlow> value)` Overwrites the list of associated OutbDeliveryDocFlow entities for the loaded navigation property to_DocumentFlow.
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`void`	`setFixedShipgProcgDurationInDays(BigDecimal fixedShipgProcgDurationInDays)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setGLAccount(String gLAccount)` Constraints: Not nullable, Maximum length: 10
`void`	`setGoodsMovementReasonCode(String goodsMovementReasonCode)` Constraints: Not nullable, Maximum length: 4 Please do not change the entry in this field.
`void`	`setGoodsMovementStatus(String goodsMovementStatus)` Constraints: Not nullable, Maximum length: 1 The status provides the following information: For an outbound delivery, the status informs you whether the item has already left the warehouse or company premises, or still being processed.
`void`	`setGoodsMovementType(String goodsMovementType)` Constraints: Not nullable, Maximum length: 3
`void`	`setHigherLevelItem(String higherLevelItem)` Constraints: Not nullable, Maximum length: 6 Items can be organized hierarchically.
`void`	`setInspectionLot(String inspectionLot)` Constraints: Not nullable, Maximum length: 12 The inspection lot number is assigned by the system.
`void`	`setInspectionPartialLot(String inspectionPartialLot)` Constraints: Not nullable, Maximum length: 6 You can process partial lots by: Inspecting during production using inspection points Running a batch split for the delivery note
`void`	`setIntercompanyBillingStatus(String intercompanyBillingStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setInternationalArticleNumber(String internationalArticleNumber)` Constraints: Not nullable, Maximum length: 18
`void`	`setInventorySpecialStockType(String inventorySpecialStockType)` Constraints: Not nullable, Maximum length: 1 If you need to separately manage certain stock (for example, consignment stock) of a material, the stock type in question is defined using this indicator.
`void`	`setInventoryValuationType(String inventoryValuationType)` Constraints: Not nullable, Maximum length: 10 The valuation types allowed for a material are determined by the valuation category.
`void`	`setIsCompletelyDelivered(Boolean isCompletelyDelivered)` Constraints: none
`void`	`setIsNotGoodsMovementsRelevant(String isNotGoodsMovementsRelevant)` Constraints: Not nullable, Maximum length: 1 When this indicator is set, goods movement is not posted for this item - regardless of the movement type assigned to it.
`void`	`setIsSeparateValuation(Boolean isSeparateValuation)` Constraints: none
`void`	`setIssgOrRcvgBatch(String issgOrRcvgBatch)` Constraints: Not nullable, Maximum length: 10 The "receiving batch" is the number of the batch under which the quantity to be transferred is now to be recorded.
`void`	`setIssgOrRcvgMaterial(String issgOrRcvgMaterial)` Constraints: Not nullable, Maximum length: 40 The "receiving material" is the material number under which the quantity to be transferred is now to be recorded.
`void`	`setIssgOrRcvgSpclStockInd(String issgOrRcvgSpclStockInd)` Constraints: Not nullable, Maximum length: 1 This indicator is used, for example, in the case of the physical transfer of a consignment material and when consignment material is transferred from the supplier's stock to the company's own stock.
`void`	`setIssgOrRcvgStockCategory(String issgOrRcvgStockCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setIssgOrRcvgValuationType(String issgOrRcvgValuationType)` Constraints: Not nullable, Maximum length: 10
`void`	`setIssuingOrReceivingPlant(String issuingOrReceivingPlant)` Constraints: Not nullable, Maximum length: 4 The receiving plant is the plant or internal organizational unit that is to receive the goods.
`void`	`setIssuingOrReceivingStorageLoc(String issuingOrReceivingStorageLoc)` Constraints: Not nullable, Maximum length: 4 The receiving storage location is the storage location that is to receive the goods.
`void`	`setItemBillingBlockReason(String itemBillingBlockReason)` Constraints: Not nullable, Maximum length: 2 The system can automatically propose a billing block for sales documents that must be checked before billing (for example, returns, credit and debit memo requests).
`void`	`setItemBillingIncompletionStatus(String itemBillingIncompletionStatus)` Constraints: Not nullable, Maximum length: 1 The status line tells you to what extent the information necessary for billing the item is complete.
`void`	`setItemDeliveryIncompletionStatus(String itemDeliveryIncompletionStatus)` Constraints: Not nullable, Maximum length: 1 The status line tells you if delivery-related item information is complete.
`void`	`setItemGdsMvtIncompletionSts(String itemGdsMvtIncompletionSts)` Constraints: Not nullable, Maximum length: 1 The status provides information on how far the data required for billing the item is complete.
`void`	`setItemGeneralIncompletionStatus(String itemGeneralIncompletionStatus)` Constraints: Not nullable, Maximum length: 1 The status line tells you if all item information, necessary for further processing this item, is complete.
`void`	`setItemGrossWeight(BigDecimal itemGrossWeight)` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order.
`void`	`setItemIsBillingRelevant(String itemIsBillingRelevant)` Constraints: Not nullable, Maximum length: 1 A: Relevant for delivery-related billing Billing is based on the outbound delivery.
`void`	`setItemNetWeight(BigDecimal itemNetWeight)` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order.
`void`	`setItemPackingIncompletionStatus(String itemPackingIncompletionStatus)` Constraints: Not nullable, Maximum length: 1 The status indicates the degree to which the data required for billing the item are complete.
`void`	`setItemPickingIncompletionStatus(String itemPickingIncompletionStatus)` Constraints: Not nullable, Maximum length: 1 The status indicates whether the delivery-related item data is complete.
`void`	`setItemVolume(BigDecimal itemVolume)` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order.
`void`	`setItemVolumeUnit(String itemVolumeUnit)` Constraints: Not nullable, Maximum length: 3 If you specify a volume, you have to enter the corresponding volume unit here.
`void`	`setItemWeightUnit(String itemWeightUnit)` Constraints: Not nullable, Maximum length: 3 If you specify a weight, you must enter the corresponding unit of weight here.
`void`	`setLastChangeDate(Calendar lastChangeDate)` Constraints: Not nullable, Precision: 7
`void`	`setLoadingGroup(String loadingGroup)` Constraints: Not nullable, Maximum length: 4 The system uses the loading group as well as the Shipping conditions and Delivering plant to automatically determine the shipping point for the item.
`void`	`setManufactureDate(Calendar manufactureDate)` Constraints: Not nullable, Precision: 7
`void`	`setMaterial(String material)` Constraints: Not nullable, Maximum length: 40
`void`	`setMaterialByCustomer(String materialByCustomer)` Constraints: Not nullable, Maximum length: 35 The customer's own identifier for a material can be stored in a customer-material info record and can be used to enter data during sales order processing.
`void`	`setMaterialFreightGroup(String materialFreightGroup)` Constraints: Not nullable, Maximum length: 8 Freight codes and classes in a freight code set are determined by the material freight group.
`void`	`setMaterialGroup(String materialGroup)` Constraints: Not nullable, Maximum length: 9 You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
`void`	`setMaterialIsBatchManaged(Boolean materialIsBatchManaged)` Constraints: noneThis indicator can be set in the material master record manually or, if batches are valuated individually, it is set automatically for the plants concerned, in which case it cannot be changed.
`void`	`setMaterialIsIntBatchManaged(Boolean materialIsIntBatchManaged)` Constraints: none
`void`	`setNumberOfSerialNumbers(Integer numberOfSerialNumbers)` Constraints: none
`void`	`setOrderID(String orderID)` Constraints: Not nullable, Maximum length: 12
`void`	`setOrderItem(String orderItem)` Constraints: Not nullable, Maximum length: 4
`void`	`setOriginalDeliveryQuantity(BigDecimal originalDeliveryQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3 When creating the inbound delivery, the notified quantity is transferred as the original quantity.
`void`	`setOriginallyRequestedMaterial(String originallyRequestedMaterial)` Constraints: Not nullable, Maximum length: 40 If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
`void`	`setOverdelivTolrtdLmtRatioInPct(BigDecimal overdelivTolrtdLmtRatioInPct)` Constraints: Not nullable, Precision: 3, Scale: 1 If you have set the indicator in the Partial delivery/Item field to 'D' (partial delivery allowed), this takes priority.
`void`	`setPackingStatus(String packingStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setPartialDeliveryIsAllowed(String partialDeliveryIsAllowed)` Constraints: Not nullable, Maximum length: 1 You use this field to control partial deliveries at the item level.
`void`	`setPaymentGuaranteeForm(String paymentGuaranteeForm)` Constraints: Not nullable, Maximum length: 2 The form of payment guarantee specifies how a sales document item is guaranteed.
`void`	`setPickingConfirmationStatus(String pickingConfirmationStatus)` Constraints: Not nullable, Maximum length: 1 When you create a delivery with an item subject to pick/putaway confirmation, the item is assigned the status A (Subject to confirmation but not yet confirmed).
`void`	`setPickingControl(String pickingControl)` Constraints: Not nullable, Maximum length: 1
`void`	`setPickingStatus(String pickingStatus)` Constraints: Not nullable, Maximum length: 1 The status message tells you whether the item is relevant for delivery.
`void`	`setPlant(String plant)` Constraints: Not nullable, Maximum length: 4
`void`	`setPrimaryPostingSwitch(String primaryPostingSwitch)` Constraints: Not nullable, Maximum length: 1
`void`	`setProductAvailabilityDate(Calendar productAvailabilityDate)` Constraints: Not nullable, Precision: 7 The system uses the material availability date to generate automatic production and purchasing requirements.
`void`	`setProductAvailabilityTime(Calendar productAvailabilityTime)` Constraints: Not nullable, Precision: 0
`void`	`setProductConfiguration(String productConfiguration)` Constraints: Not nullable, Maximum length: 18 This number clearly identifies one particular configuration of a standard product.
`void`	`setProductHierarchyNode(String productHierarchyNode)` Constraints: Not nullable, Maximum length: 18 In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.
`void`	`setProfitabilitySegment(String profitabilitySegment)` Constraints: Not nullable, Maximum length: 10 Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
`void`	`setProfitCenter(String profitCenter)` Constraints: Not nullable, Maximum length: 10
`void`	`setProofOfDeliveryRelevanceCode(String proofOfDeliveryRelevanceCode)` Constraints: Not nullable, Maximum length: 1 The indicator can have the following settings: ' ': not POD relevant 'A' : always POD relevant 'B' : only POD relevant when there are quantity differences The indicator is copied from the purchasing or sales document into the delivery, if control of POD relevance in the delivery item category is set to "Copy POD relevance from preceding document".
`void`	`setProofOfDeliveryStatus(String proofOfDeliveryStatus)` Constraints: Not nullable, Maximum length: 1 The status message informs you whether the ship-to party reported a proof of delivery for this item.
`void`	`setQuantityIsFixed(Boolean quantityIsFixed)` Constraints: noneSet this indicator if the quantity in a relational system does not change.
`void`	`setReceivingPoint(String receivingPoint)` Constraints: Not nullable, Maximum length: 25 Several receiving points can be defined for each plant.
`void`	`setReferenceDocumentLogicalSystem(String referenceDocumentLogicalSystem)` Constraints: Not nullable, Maximum length: 10
`void`	`setReferenceSDDocument(String referenceSDDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setReferenceSDDocumentCategory(String referenceSDDocumentCategory)` Constraints: Not nullable, Maximum length: 4
`void`	`setReferenceSDDocumentItem(String referenceSDDocumentItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setRetailPromotion(String retailPromotion)` Constraints: Not nullable, Maximum length: 10 For each item of a purchasing document, you can specify the promotion to which the item belongs.
`void`	`setSalesDocumentItemType(String salesDocumentItemType)` Constraints: Not nullable, Maximum length: 1 The system processes items that refer to a specific material differently than items that do not refer to a material.
`void`	`setSalesGroup(String salesGroup)` Constraints: Not nullable, Maximum length: 3 By using sales groups you can designate different areas of responsibility within a sales office.
`void`	`setSalesOffice(String salesOffice)` Constraints: Not nullable, Maximum length: 4 When you create sales statistics, you can use a sales office as one of the selection criteria.
`void`	`setSDDocumentCategory(String sDDocumentCategory)` Constraints: Not nullable, Maximum length: 4 The document category determines how the system stores and keeps track of document data.
`void`	`setSDProcessStatus(String sDProcessStatus)` Constraints: Not nullable, Maximum length: 1 The system determines the overall status from all statuses (for example, delivery and billing) for this item.
`void`	`setSerialDeliveryItem(SerialNmbrDelivery value)` Overwrites the associated SerialNmbrDelivery entity for the loaded navigation property to_SerialDeliveryItem.
`void`	`setShelfLifeExpirationDate(Calendar shelfLifeExpirationDate)` Constraints: Not nullable, Precision: 7 You enter it yourself.
`void`	`setStatisticsDate(Calendar statisticsDate)` Constraints: Not nullable, Precision: 7 Write a user-exit if you require the system to copy the statistics date to the billing document.
`void`	`setStockType(String stockType)` Constraints: Not nullable, Maximum length: 1 Possible stocks are: unrestricted-use stock (blank, F) stock in quality inspection (X, 2) blocked stock (S, 3) Select the corresponding indicator for the stock type required.
`void`	`setStorageBin(String storageBin)` Constraints: Not nullable, Maximum length: 10 A storage bin can be further sub-divided into bin sections.
`void`	`setStorageLocation(String storageLocation)` Constraints: Not nullable, Maximum length: 4
`void`	`setStorageType(String storageType)` Constraints: Not nullable, Maximum length: 3 A typical warehouse could have the following storage types: Goods receipt area Picking area High-rack storage area Bulk storage area Open storage area Goods issue area
`void`	`setSubsequentMovementType(String subsequentMovementType)` Constraints: Not nullable, Maximum length: 3
`void`	`setTransportationGroup(String transportationGroup)` Constraints: Not nullable, Maximum length: 4 Transportation groups are used for automatic route scheduling during sales order and delivery note processing.
`void`	`setUnderdelivTolrtdLmtRatioInPct(BigDecimal underdelivTolrtdLmtRatioInPct)` Constraints: Not nullable, Precision: 3, Scale: 1
`void`	`setUnlimitedOverdeliveryIsAllowed(Boolean unlimitedOverdeliveryIsAllowed)` Constraints: none
`void`	`setVarblShipgProcgDurationInDays(BigDecimal varblShipgProcgDurationInDays)` Constraints: Not nullable, Precision: 5, Scale: 2 The system uses the variable during capacity planning for deliveries.
`void`	`setWarehouse(String warehouse)` Constraints: Not nullable, Maximum length: 3 All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number.
`void`	`setWarehouseActivityStatus(String warehouseActivityStatus)` Constraints: Not nullable, Maximum length: 1 If your delivery processing includes the SAP Warehouse Management (WM) system, the system automatically indicates the WM status for each item in a delivery.
`void`	`setWarehouseStagingArea(String warehouseStagingArea)` Constraints: Not nullable, Maximum length: 10 Staging areas can be used for different purposes (at the same time, if necessary): o Goods issue o Goods receipt o Cross-docking processes o Direct distribution
`void`	`setWarehouseStockCategory(String warehouseStockCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setWarehouseStorageBin(String warehouseStorageBin)` Constraints: Not nullable, Maximum length: 10 This storage bin is only significant if you do not use SAP warehouse management.
`String`	`toString()`

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

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField

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

- Field Detail
  - ALL_FIELDS
```
public static final OutbDeliveryItemSelectable ALL_FIELDS
```
    Selector for all available fields of OutbDeliveryItem.
  - ACTUAL_DELIVERED_QTY_IN_BASE_UNIT
```
public static final OutbDeliveryItemField<BigDecimal> ACTUAL_DELIVERED_QTY_IN_BASE_UNIT
```
    Use with available fluent helpers to apply the ActualDeliveredQtyInBaseUnit field to query operations.
  - DELIVERY_VERSION
```
public static final OutbDeliveryItemField<String> DELIVERY_VERSION
```
    Use with available fluent helpers to apply the DeliveryVersion field to query operations.
  - ACTUAL_DELIVERY_QUANTITY
```
public static final OutbDeliveryItemField<BigDecimal> ACTUAL_DELIVERY_QUANTITY
```
    Use with available fluent helpers to apply the ActualDeliveryQuantity field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP1
```
public static final OutbDeliveryItemField<String> ADDITIONAL_CUSTOMER_GROUP1
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup1 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP2
```
public static final OutbDeliveryItemField<String> ADDITIONAL_CUSTOMER_GROUP2
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup2 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP3
```
public static final OutbDeliveryItemField<String> ADDITIONAL_CUSTOMER_GROUP3
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup3 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP4
```
public static final OutbDeliveryItemField<String> ADDITIONAL_CUSTOMER_GROUP4
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup4 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP5
```
public static final OutbDeliveryItemField<String> ADDITIONAL_CUSTOMER_GROUP5
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup5 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP1
```
public static final OutbDeliveryItemField<String> ADDITIONAL_MATERIAL_GROUP1
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup1 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP2
```
public static final OutbDeliveryItemField<String> ADDITIONAL_MATERIAL_GROUP2
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup2 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP3
```
public static final OutbDeliveryItemField<String> ADDITIONAL_MATERIAL_GROUP3
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup3 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP4
```
public static final OutbDeliveryItemField<String> ADDITIONAL_MATERIAL_GROUP4
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup4 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP5
```
public static final OutbDeliveryItemField<String> ADDITIONAL_MATERIAL_GROUP5
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup5 field to query operations.
  - ALTERNATE_PRODUCT_NUMBER
```
public static final OutbDeliveryItemField<String> ALTERNATE_PRODUCT_NUMBER
```
    Use with available fluent helpers to apply the AlternateProductNumber field to query operations.
  - BASE_UNIT
```
public static final OutbDeliveryItemField<String> BASE_UNIT
```
    Use with available fluent helpers to apply the BaseUnit field to query operations.
  - BATCH
```
public static final OutbDeliveryItemField<String> BATCH
```
    Use with available fluent helpers to apply the Batch field to query operations.
  - BATCH_BY_SUPPLIER
```
public static final OutbDeliveryItemField<String> BATCH_BY_SUPPLIER
```
    Use with available fluent helpers to apply the BatchBySupplier field to query operations.
  - BATCH_CLASSIFICATION
```
public static final OutbDeliveryItemField<String> BATCH_CLASSIFICATION
```
    Use with available fluent helpers to apply the BatchClassification field to query operations.
  - BOM_EXPLOSION
```
public static final OutbDeliveryItemField<String> BOM_EXPLOSION
```
    Use with available fluent helpers to apply the BOMExplosion field to query operations.
  - BUSINESS_AREA
```
public static final OutbDeliveryItemField<String> BUSINESS_AREA
```
    Use with available fluent helpers to apply the BusinessArea field to query operations.
  - CONSUMPTION_POSTING
```
public static final OutbDeliveryItemField<String> CONSUMPTION_POSTING
```
    Use with available fluent helpers to apply the ConsumptionPosting field to query operations.
  - CONTROLLING_AREA
```
public static final OutbDeliveryItemField<String> CONTROLLING_AREA
```
    Use with available fluent helpers to apply the ControllingArea field to query operations.
  - COST_CENTER
```
public static final OutbDeliveryItemField<String> COST_CENTER
```
    Use with available fluent helpers to apply the CostCenter field to query operations.
  - CREATED_BY_USER
```
public static final OutbDeliveryItemField<String> CREATED_BY_USER
```
    Use with available fluent helpers to apply the CreatedByUser field to query operations.
  - CREATION_DATE
```
public static final OutbDeliveryItemField<Calendar> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATION_TIME
```
public static final OutbDeliveryItemField<Calendar> CREATION_TIME
```
    Use with available fluent helpers to apply the CreationTime field to query operations.
  - CUST_ENGINEERING_CHG_STATUS
```
public static final OutbDeliveryItemField<String> CUST_ENGINEERING_CHG_STATUS
```
    Use with available fluent helpers to apply the CustEngineeringChgStatus field to query operations.
  - DELIVERY_DOCUMENT
```
public static final OutbDeliveryItemField<String> DELIVERY_DOCUMENT
```
    Use with available fluent helpers to apply the DeliveryDocument field to query operations.
  - DELIVERY_DOCUMENT_ITEM
```
public static final OutbDeliveryItemField<String> DELIVERY_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the DeliveryDocumentItem field to query operations.
  - DELIVERY_DOCUMENT_ITEM_CATEGORY
```
public static final OutbDeliveryItemField<String> DELIVERY_DOCUMENT_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the DeliveryDocumentItemCategory field to query operations.
  - DELIVERY_DOCUMENT_ITEM_TEXT
```
public static final OutbDeliveryItemField<String> DELIVERY_DOCUMENT_ITEM_TEXT
```
    Use with available fluent helpers to apply the DeliveryDocumentItemText field to query operations.
  - DELIVERY_GROUP
```
public static final OutbDeliveryItemField<String> DELIVERY_GROUP
```
    Use with available fluent helpers to apply the DeliveryGroup field to query operations.
  - DELIVERY_QUANTITY_UNIT
```
public static final OutbDeliveryItemField<String> DELIVERY_QUANTITY_UNIT
```
    Use with available fluent helpers to apply the DeliveryQuantityUnit field to query operations.
  - DELIVERY_RELATED_BILLING_STATUS
```
public static final OutbDeliveryItemField<String> DELIVERY_RELATED_BILLING_STATUS
```
    Use with available fluent helpers to apply the DeliveryRelatedBillingStatus field to query operations.
  - DELIVERY_TO_BASE_QUANTITY_DNMNTR
```
public static final OutbDeliveryItemField<BigDecimal> DELIVERY_TO_BASE_QUANTITY_DNMNTR
```
    Use with available fluent helpers to apply the DeliveryToBaseQuantityDnmntr field to query operations.
  - DELIVERY_TO_BASE_QUANTITY_NMRTR
```
public static final OutbDeliveryItemField<BigDecimal> DELIVERY_TO_BASE_QUANTITY_NMRTR
```
    Use with available fluent helpers to apply the DeliveryToBaseQuantityNmrtr field to query operations.
  - DEPARTMENT_CLASSIFICATION_BY_CUST
```
public static final OutbDeliveryItemField<String> DEPARTMENT_CLASSIFICATION_BY_CUST
```
    Use with available fluent helpers to apply the DepartmentClassificationByCust field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final OutbDeliveryItemField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - DIVISION
```
public static final OutbDeliveryItemField<String> DIVISION
```
    Use with available fluent helpers to apply the Division field to query operations.
  - FIXED_SHIPG_PROCG_DURATION_IN_DAYS
```
public static final OutbDeliveryItemField<BigDecimal> FIXED_SHIPG_PROCG_DURATION_IN_DAYS
```
    Use with available fluent helpers to apply the FixedShipgProcgDurationInDays field to query operations.
  - GL_ACCOUNT
```
public static final OutbDeliveryItemField<String> GL_ACCOUNT
```
    Use with available fluent helpers to apply the GLAccount field to query operations.
  - GOODS_MOVEMENT_REASON_CODE
```
public static final OutbDeliveryItemField<String> GOODS_MOVEMENT_REASON_CODE
```
    Use with available fluent helpers to apply the GoodsMovementReasonCode field to query operations.
  - GOODS_MOVEMENT_STATUS
```
public static final OutbDeliveryItemField<String> GOODS_MOVEMENT_STATUS
```
    Use with available fluent helpers to apply the GoodsMovementStatus field to query operations.
  - GOODS_MOVEMENT_TYPE
```
public static final OutbDeliveryItemField<String> GOODS_MOVEMENT_TYPE
```
    Use with available fluent helpers to apply the GoodsMovementType field to query operations.
  - HIGHER_LEVEL_ITEM
```
public static final OutbDeliveryItemField<String> HIGHER_LEVEL_ITEM
```
    Use with available fluent helpers to apply the HigherLevelItem field to query operations.
  - INSPECTION_LOT
```
public static final OutbDeliveryItemField<String> INSPECTION_LOT
```
    Use with available fluent helpers to apply the InspectionLot field to query operations.
  - INSPECTION_PARTIAL_LOT
```
public static final OutbDeliveryItemField<String> INSPECTION_PARTIAL_LOT
```
    Use with available fluent helpers to apply the InspectionPartialLot field to query operations.
  - INTERCOMPANY_BILLING_STATUS
```
public static final OutbDeliveryItemField<String> INTERCOMPANY_BILLING_STATUS
```
    Use with available fluent helpers to apply the IntercompanyBillingStatus field to query operations.
  - INTERNATIONAL_ARTICLE_NUMBER
```
public static final OutbDeliveryItemField<String> INTERNATIONAL_ARTICLE_NUMBER
```
    Use with available fluent helpers to apply the InternationalArticleNumber field to query operations.
  - INVENTORY_SPECIAL_STOCK_TYPE
```
public static final OutbDeliveryItemField<String> INVENTORY_SPECIAL_STOCK_TYPE
```
    Use with available fluent helpers to apply the InventorySpecialStockType field to query operations.
  - INVENTORY_VALUATION_TYPE
```
public static final OutbDeliveryItemField<String> INVENTORY_VALUATION_TYPE
```
    Use with available fluent helpers to apply the InventoryValuationType field to query operations.
  - IS_COMPLETELY_DELIVERED
```
public static final OutbDeliveryItemField<Boolean> IS_COMPLETELY_DELIVERED
```
    Use with available fluent helpers to apply the IsCompletelyDelivered field to query operations.
  - IS_NOT_GOODS_MOVEMENTS_RELEVANT
```
public static final OutbDeliveryItemField<String> IS_NOT_GOODS_MOVEMENTS_RELEVANT
```
    Use with available fluent helpers to apply the IsNotGoodsMovementsRelevant field to query operations.
  - IS_SEPARATE_VALUATION
```
public static final OutbDeliveryItemField<Boolean> IS_SEPARATE_VALUATION
```
    Use with available fluent helpers to apply the IsSeparateValuation field to query operations.
  - ISSG_OR_RCVG_BATCH
```
public static final OutbDeliveryItemField<String> ISSG_OR_RCVG_BATCH
```
    Use with available fluent helpers to apply the IssgOrRcvgBatch field to query operations.
  - ISSG_OR_RCVG_MATERIAL
```
public static final OutbDeliveryItemField<String> ISSG_OR_RCVG_MATERIAL
```
    Use with available fluent helpers to apply the IssgOrRcvgMaterial field to query operations.
  - ISSG_OR_RCVG_SPCL_STOCK_IND
```
public static final OutbDeliveryItemField<String> ISSG_OR_RCVG_SPCL_STOCK_IND
```
    Use with available fluent helpers to apply the IssgOrRcvgSpclStockInd field to query operations.
  - ISSG_OR_RCVG_STOCK_CATEGORY
```
public static final OutbDeliveryItemField<String> ISSG_OR_RCVG_STOCK_CATEGORY
```
    Use with available fluent helpers to apply the IssgOrRcvgStockCategory field to query operations.
  - ISSG_OR_RCVG_VALUATION_TYPE
```
public static final OutbDeliveryItemField<String> ISSG_OR_RCVG_VALUATION_TYPE
```
    Use with available fluent helpers to apply the IssgOrRcvgValuationType field to query operations.
  - ISSUING_OR_RECEIVING_PLANT
```
public static final OutbDeliveryItemField<String> ISSUING_OR_RECEIVING_PLANT
```
    Use with available fluent helpers to apply the IssuingOrReceivingPlant field to query operations.
  - ISSUING_OR_RECEIVING_STORAGE_LOC
```
public static final OutbDeliveryItemField<String> ISSUING_OR_RECEIVING_STORAGE_LOC
```
    Use with available fluent helpers to apply the IssuingOrReceivingStorageLoc field to query operations.
  - ITEM_BILLING_BLOCK_REASON
```
public static final OutbDeliveryItemField<String> ITEM_BILLING_BLOCK_REASON
```
    Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
  - ITEM_BILLING_INCOMPLETION_STATUS
```
public static final OutbDeliveryItemField<String> ITEM_BILLING_INCOMPLETION_STATUS
```
    Use with available fluent helpers to apply the ItemBillingIncompletionStatus field to query operations.
  - ITEM_DELIVERY_INCOMPLETION_STATUS
```
public static final OutbDeliveryItemField<String> ITEM_DELIVERY_INCOMPLETION_STATUS
```
    Use with available fluent helpers to apply the ItemDeliveryIncompletionStatus field to query operations.
  - ITEM_GDS_MVT_INCOMPLETION_STS
```
public static final OutbDeliveryItemField<String> ITEM_GDS_MVT_INCOMPLETION_STS
```
    Use with available fluent helpers to apply the ItemGdsMvtIncompletionSts field to query operations.
  - ITEM_GENERAL_INCOMPLETION_STATUS
```
public static final OutbDeliveryItemField<String> ITEM_GENERAL_INCOMPLETION_STATUS
```
    Use with available fluent helpers to apply the ItemGeneralIncompletionStatus field to query operations.
  - ITEM_GROSS_WEIGHT
```
public static final OutbDeliveryItemField<BigDecimal> ITEM_GROSS_WEIGHT
```
    Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
  - ITEM_IS_BILLING_RELEVANT
```
public static final OutbDeliveryItemField<String> ITEM_IS_BILLING_RELEVANT
```
    Use with available fluent helpers to apply the ItemIsBillingRelevant field to query operations.
  - ITEM_NET_WEIGHT
```
public static final OutbDeliveryItemField<BigDecimal> ITEM_NET_WEIGHT
```
    Use with available fluent helpers to apply the ItemNetWeight field to query operations.
  - ITEM_PACKING_INCOMPLETION_STATUS
```
public static final OutbDeliveryItemField<String> ITEM_PACKING_INCOMPLETION_STATUS
```
    Use with available fluent helpers to apply the ItemPackingIncompletionStatus field to query operations.
  - ITEM_PICKING_INCOMPLETION_STATUS
```
public static final OutbDeliveryItemField<String> ITEM_PICKING_INCOMPLETION_STATUS
```
    Use with available fluent helpers to apply the ItemPickingIncompletionStatus field to query operations.
  - ITEM_VOLUME
```
public static final OutbDeliveryItemField<BigDecimal> ITEM_VOLUME
```
    Use with available fluent helpers to apply the ItemVolume field to query operations.
  - ITEM_VOLUME_UNIT
```
public static final OutbDeliveryItemField<String> ITEM_VOLUME_UNIT
```
    Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
  - ITEM_WEIGHT_UNIT
```
public static final OutbDeliveryItemField<String> ITEM_WEIGHT_UNIT
```
    Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
  - LAST_CHANGE_DATE
```
public static final OutbDeliveryItemField<Calendar> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - LOADING_GROUP
```
public static final OutbDeliveryItemField<String> LOADING_GROUP
```
    Use with available fluent helpers to apply the LoadingGroup field to query operations.
  - MANUFACTURE_DATE
```
public static final OutbDeliveryItemField<Calendar> MANUFACTURE_DATE
```
    Use with available fluent helpers to apply the ManufactureDate field to query operations.
  - MATERIAL
```
public static final OutbDeliveryItemField<String> MATERIAL
```
    Use with available fluent helpers to apply the Material field to query operations.
  - MATERIAL_BY_CUSTOMER
```
public static final OutbDeliveryItemField<String> MATERIAL_BY_CUSTOMER
```
    Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
  - MATERIAL_FREIGHT_GROUP
```
public static final OutbDeliveryItemField<String> MATERIAL_FREIGHT_GROUP
```
    Use with available fluent helpers to apply the MaterialFreightGroup field to query operations.
  - MATERIAL_GROUP
```
public static final OutbDeliveryItemField<String> MATERIAL_GROUP
```
    Use with available fluent helpers to apply the MaterialGroup field to query operations.
  - MATERIAL_IS_BATCH_MANAGED
```
public static final OutbDeliveryItemField<Boolean> MATERIAL_IS_BATCH_MANAGED
```
    Use with available fluent helpers to apply the MaterialIsBatchManaged field to query operations.
  - MATERIAL_IS_INT_BATCH_MANAGED
```
public static final OutbDeliveryItemField<Boolean> MATERIAL_IS_INT_BATCH_MANAGED
```
    Use with available fluent helpers to apply the MaterialIsIntBatchManaged field to query operations.
  - NUMBER_OF_SERIAL_NUMBERS
```
public static final OutbDeliveryItemField<Integer> NUMBER_OF_SERIAL_NUMBERS
```
    Use with available fluent helpers to apply the NumberOfSerialNumbers field to query operations.
  - ORDER_ID
```
public static final OutbDeliveryItemField<String> ORDER_ID
```
    Use with available fluent helpers to apply the OrderID field to query operations.
  - ORDER_ITEM
```
public static final OutbDeliveryItemField<String> ORDER_ITEM
```
    Use with available fluent helpers to apply the OrderItem field to query operations.
  - ORIGINAL_DELIVERY_QUANTITY
```
public static final OutbDeliveryItemField<BigDecimal> ORIGINAL_DELIVERY_QUANTITY
```
    Use with available fluent helpers to apply the OriginalDeliveryQuantity field to query operations.
  - ORIGINALLY_REQUESTED_MATERIAL
```
public static final OutbDeliveryItemField<String> ORIGINALLY_REQUESTED_MATERIAL
```
    Use with available fluent helpers to apply the OriginallyRequestedMaterial field to query operations.
  - OVERDELIV_TOLRTD_LMT_RATIO_IN_PCT
```
public static final OutbDeliveryItemField<BigDecimal> OVERDELIV_TOLRTD_LMT_RATIO_IN_PCT
```
    Use with available fluent helpers to apply the OverdelivTolrtdLmtRatioInPct field to query operations.
  - PACKING_STATUS
```
public static final OutbDeliveryItemField<String> PACKING_STATUS
```
    Use with available fluent helpers to apply the PackingStatus field to query operations.
  - PARTIAL_DELIVERY_IS_ALLOWED
```
public static final OutbDeliveryItemField<String> PARTIAL_DELIVERY_IS_ALLOWED
```
    Use with available fluent helpers to apply the PartialDeliveryIsAllowed field to query operations.
  - PAYMENT_GUARANTEE_FORM
```
public static final OutbDeliveryItemField<String> PAYMENT_GUARANTEE_FORM
```
    Use with available fluent helpers to apply the PaymentGuaranteeForm field to query operations.
  - PICKING_CONFIRMATION_STATUS
```
public static final OutbDeliveryItemField<String> PICKING_CONFIRMATION_STATUS
```
    Use with available fluent helpers to apply the PickingConfirmationStatus field to query operations.
  - PICKING_CONTROL
```
public static final OutbDeliveryItemField<String> PICKING_CONTROL
```
    Use with available fluent helpers to apply the PickingControl field to query operations.
  - PICKING_STATUS
```
public static final OutbDeliveryItemField<String> PICKING_STATUS
```
    Use with available fluent helpers to apply the PickingStatus field to query operations.
  - PLANT
```
public static final OutbDeliveryItemField<String> PLANT
```
    Use with available fluent helpers to apply the Plant field to query operations.
  - PRIMARY_POSTING_SWITCH
```
public static final OutbDeliveryItemField<String> PRIMARY_POSTING_SWITCH
```
    Use with available fluent helpers to apply the PrimaryPostingSwitch field to query operations.
  - PRODUCT_AVAILABILITY_DATE
```
public static final OutbDeliveryItemField<Calendar> PRODUCT_AVAILABILITY_DATE
```
    Use with available fluent helpers to apply the ProductAvailabilityDate field to query operations.
  - PRODUCT_AVAILABILITY_TIME
```
public static final OutbDeliveryItemField<Calendar> PRODUCT_AVAILABILITY_TIME
```
    Use with available fluent helpers to apply the ProductAvailabilityTime field to query operations.
  - PRODUCT_CONFIGURATION
```
public static final OutbDeliveryItemField<String> PRODUCT_CONFIGURATION
```
    Use with available fluent helpers to apply the ProductConfiguration field to query operations.
  - PRODUCT_HIERARCHY_NODE
```
public static final OutbDeliveryItemField<String> PRODUCT_HIERARCHY_NODE
```
    Use with available fluent helpers to apply the ProductHierarchyNode field to query operations.
  - PROFITABILITY_SEGMENT
```
public static final OutbDeliveryItemField<String> PROFITABILITY_SEGMENT
```
    Use with available fluent helpers to apply the ProfitabilitySegment field to query operations.
  - PROFIT_CENTER
```
public static final OutbDeliveryItemField<String> PROFIT_CENTER
```
    Use with available fluent helpers to apply the ProfitCenter field to query operations.
  - PROOF_OF_DELIVERY_RELEVANCE_CODE
```
public static final OutbDeliveryItemField<String> PROOF_OF_DELIVERY_RELEVANCE_CODE
```
    Use with available fluent helpers to apply the ProofOfDeliveryRelevanceCode field to query operations.
  - PROOF_OF_DELIVERY_STATUS
```
public static final OutbDeliveryItemField<String> PROOF_OF_DELIVERY_STATUS
```
    Use with available fluent helpers to apply the ProofOfDeliveryStatus field to query operations.
  - QUANTITY_IS_FIXED
```
public static final OutbDeliveryItemField<Boolean> QUANTITY_IS_FIXED
```
    Use with available fluent helpers to apply the QuantityIsFixed field to query operations.
  - RECEIVING_POINT
```
public static final OutbDeliveryItemField<String> RECEIVING_POINT
```
    Use with available fluent helpers to apply the ReceivingPoint field to query operations.
  - REFERENCE_DOCUMENT_LOGICAL_SYSTEM
```
public static final OutbDeliveryItemField<String> REFERENCE_DOCUMENT_LOGICAL_SYSTEM
```
    Use with available fluent helpers to apply the ReferenceDocumentLogicalSystem field to query operations.
  - REFERENCE_SD_DOCUMENT
```
public static final OutbDeliveryItemField<String> REFERENCE_SD_DOCUMENT
```
    Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
  - REFERENCE_SD_DOCUMENT_CATEGORY
```
public static final OutbDeliveryItemField<String> REFERENCE_SD_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
  - REFERENCE_SD_DOCUMENT_ITEM
```
public static final OutbDeliveryItemField<String> REFERENCE_SD_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the ReferenceSDDocumentItem field to query operations.
  - RETAIL_PROMOTION
```
public static final OutbDeliveryItemField<String> RETAIL_PROMOTION
```
    Use with available fluent helpers to apply the RetailPromotion field to query operations.
  - SALES_DOCUMENT_ITEM_TYPE
```
public static final OutbDeliveryItemField<String> SALES_DOCUMENT_ITEM_TYPE
```
    Use with available fluent helpers to apply the SalesDocumentItemType field to query operations.
  - SALES_GROUP
```
public static final OutbDeliveryItemField<String> SALES_GROUP
```
    Use with available fluent helpers to apply the SalesGroup field to query operations.
  - SALES_OFFICE
```
public static final OutbDeliveryItemField<String> SALES_OFFICE
```
    Use with available fluent helpers to apply the SalesOffice field to query operations.
  - SD_DOCUMENT_CATEGORY
```
public static final OutbDeliveryItemField<String> SD_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the SDDocumentCategory field to query operations.
  - SD_PROCESS_STATUS
```
public static final OutbDeliveryItemField<String> SD_PROCESS_STATUS
```
    Use with available fluent helpers to apply the SDProcessStatus field to query operations.
  - SHELF_LIFE_EXPIRATION_DATE
```
public static final OutbDeliveryItemField<Calendar> SHELF_LIFE_EXPIRATION_DATE
```
    Use with available fluent helpers to apply the ShelfLifeExpirationDate field to query operations.
  - STATISTICS_DATE
```
public static final OutbDeliveryItemField<Calendar> STATISTICS_DATE
```
    Use with available fluent helpers to apply the StatisticsDate field to query operations.
  - STOCK_TYPE
```
public static final OutbDeliveryItemField<String> STOCK_TYPE
```
    Use with available fluent helpers to apply the StockType field to query operations.
  - STORAGE_BIN
```
public static final OutbDeliveryItemField<String> STORAGE_BIN
```
    Use with available fluent helpers to apply the StorageBin field to query operations.
  - STORAGE_LOCATION
```
public static final OutbDeliveryItemField<String> STORAGE_LOCATION
```
    Use with available fluent helpers to apply the StorageLocation field to query operations.
  - STORAGE_TYPE
```
public static final OutbDeliveryItemField<String> STORAGE_TYPE
```
    Use with available fluent helpers to apply the StorageType field to query operations.
  - SUBSEQUENT_MOVEMENT_TYPE
```
public static final OutbDeliveryItemField<String> SUBSEQUENT_MOVEMENT_TYPE
```
    Use with available fluent helpers to apply the SubsequentMovementType field to query operations.
  - TRANSPORTATION_GROUP
```
public static final OutbDeliveryItemField<String> TRANSPORTATION_GROUP
```
    Use with available fluent helpers to apply the TransportationGroup field to query operations.
  - UNDERDELIV_TOLRTD_LMT_RATIO_IN_PCT
```
public static final OutbDeliveryItemField<BigDecimal> UNDERDELIV_TOLRTD_LMT_RATIO_IN_PCT
```
    Use with available fluent helpers to apply the UnderdelivTolrtdLmtRatioInPct field to query operations.
  - UNLIMITED_OVERDELIVERY_IS_ALLOWED
```
public static final OutbDeliveryItemField<Boolean> UNLIMITED_OVERDELIVERY_IS_ALLOWED
```
    Use with available fluent helpers to apply the UnlimitedOverdeliveryIsAllowed field to query operations.
  - VARBL_SHIPG_PROCG_DURATION_IN_DAYS
```
public static final OutbDeliveryItemField<BigDecimal> VARBL_SHIPG_PROCG_DURATION_IN_DAYS
```
    Use with available fluent helpers to apply the VarblShipgProcgDurationInDays field to query operations.
  - WAREHOUSE
```
public static final OutbDeliveryItemField<String> WAREHOUSE
```
    Use with available fluent helpers to apply the Warehouse field to query operations.
  - WAREHOUSE_ACTIVITY_STATUS
```
public static final OutbDeliveryItemField<String> WAREHOUSE_ACTIVITY_STATUS
```
    Use with available fluent helpers to apply the WarehouseActivityStatus field to query operations.
  - WAREHOUSE_STAGING_AREA
```
public static final OutbDeliveryItemField<String> WAREHOUSE_STAGING_AREA
```
    Use with available fluent helpers to apply the WarehouseStagingArea field to query operations.
  - WAREHOUSE_STOCK_CATEGORY
```
public static final OutbDeliveryItemField<String> WAREHOUSE_STOCK_CATEGORY
```
    Use with available fluent helpers to apply the WarehouseStockCategory field to query operations.
  - WAREHOUSE_STORAGE_BIN
```
public static final OutbDeliveryItemField<String> WAREHOUSE_STORAGE_BIN
```
    Use with available fluent helpers to apply the WarehouseStorageBin field to query operations.
  - TO_DOCUMENT_FLOW
```
public static final OutbDeliveryItemLink<OutbDeliveryDocFlow> TO_DOCUMENT_FLOW
```
    Use with available fluent helpers to apply the to_DocumentFlow navigation property to query operations.
  - TO_SERIAL_DELIVERY_ITEM
```
public static final OutbDeliveryItemLink<SerialNmbrDelivery> TO_SERIAL_DELIVERY_ITEM
```
    Use with available fluent helpers to apply the to_SerialDeliveryItem navigation property to query operations.
- Constructor Detail
  - OutbDeliveryItem
```
public OutbDeliveryItem()
```
  - OutbDeliveryItem
```
public OutbDeliveryItem(@Nullable
                        BigDecimal actualDeliveredQtyInBaseUnit,
                        @Nullable
                        String deliveryVersion,
                        @Nullable
                        BigDecimal actualDeliveryQuantity,
                        @Nullable
                        String additionalCustomerGroup1,
                        @Nullable
                        String additionalCustomerGroup2,
                        @Nullable
                        String additionalCustomerGroup3,
                        @Nullable
                        String additionalCustomerGroup4,
                        @Nullable
                        String additionalCustomerGroup5,
                        @Nullable
                        String additionalMaterialGroup1,
                        @Nullable
                        String additionalMaterialGroup2,
                        @Nullable
                        String additionalMaterialGroup3,
                        @Nullable
                        String additionalMaterialGroup4,
                        @Nullable
                        String additionalMaterialGroup5,
                        @Nullable
                        String alternateProductNumber,
                        @Nullable
                        String baseUnit,
                        @Nullable
                        String batch,
                        @Nullable
                        String batchBySupplier,
                        @Nullable
                        String batchClassification,
                        @Nullable
                        String bOMExplosion,
                        @Nullable
                        String businessArea,
                        @Nullable
                        String consumptionPosting,
                        @Nullable
                        String controllingArea,
                        @Nullable
                        String costCenter,
                        @Nullable
                        String createdByUser,
                        @Nullable
                        Calendar creationDate,
                        @Nullable
                        Calendar creationTime,
                        @Nullable
                        String custEngineeringChgStatus,
                        @Nullable
                        String deliveryDocument,
                        @Nullable
                        String deliveryDocumentItem,
                        @Nullable
                        String deliveryDocumentItemCategory,
                        @Nullable
                        String deliveryDocumentItemText,
                        @Nullable
                        String deliveryGroup,
                        @Nullable
                        String deliveryQuantityUnit,
                        @Nullable
                        String deliveryRelatedBillingStatus,
                        @Nullable
                        BigDecimal deliveryToBaseQuantityDnmntr,
                        @Nullable
                        BigDecimal deliveryToBaseQuantityNmrtr,
                        @Nullable
                        String departmentClassificationByCust,
                        @Nullable
                        String distributionChannel,
                        @Nullable
                        String division,
                        @Nullable
                        BigDecimal fixedShipgProcgDurationInDays,
                        @Nullable
                        String gLAccount,
                        @Nullable
                        String goodsMovementReasonCode,
                        @Nullable
                        String goodsMovementStatus,
                        @Nullable
                        String goodsMovementType,
                        @Nullable
                        String higherLevelItem,
                        @Nullable
                        String inspectionLot,
                        @Nullable
                        String inspectionPartialLot,
                        @Nullable
                        String intercompanyBillingStatus,
                        @Nullable
                        String internationalArticleNumber,
                        @Nullable
                        String inventorySpecialStockType,
                        @Nullable
                        String inventoryValuationType,
                        @Nullable
                        Boolean isCompletelyDelivered,
                        @Nullable
                        String isNotGoodsMovementsRelevant,
                        @Nullable
                        Boolean isSeparateValuation,
                        @Nullable
                        String issgOrRcvgBatch,
                        @Nullable
                        String issgOrRcvgMaterial,
                        @Nullable
                        String issgOrRcvgSpclStockInd,
                        @Nullable
                        String issgOrRcvgStockCategory,
                        @Nullable
                        String issgOrRcvgValuationType,
                        @Nullable
                        String issuingOrReceivingPlant,
                        @Nullable
                        String issuingOrReceivingStorageLoc,
                        @Nullable
                        String itemBillingBlockReason,
                        @Nullable
                        String itemBillingIncompletionStatus,
                        @Nullable
                        String itemDeliveryIncompletionStatus,
                        @Nullable
                        String itemGdsMvtIncompletionSts,
                        @Nullable
                        String itemGeneralIncompletionStatus,
                        @Nullable
                        BigDecimal itemGrossWeight,
                        @Nullable
                        String itemIsBillingRelevant,
                        @Nullable
                        BigDecimal itemNetWeight,
                        @Nullable
                        String itemPackingIncompletionStatus,
                        @Nullable
                        String itemPickingIncompletionStatus,
                        @Nullable
                        BigDecimal itemVolume,
                        @Nullable
                        String itemVolumeUnit,
                        @Nullable
                        String itemWeightUnit,
                        @Nullable
                        Calendar lastChangeDate,
                        @Nullable
                        String loadingGroup,
                        @Nullable
                        Calendar manufactureDate,
                        @Nullable
                        String material,
                        @Nullable
                        String materialByCustomer,
                        @Nullable
                        String materialFreightGroup,
                        @Nullable
                        String materialGroup,
                        @Nullable
                        Boolean materialIsBatchManaged,
                        @Nullable
                        Boolean materialIsIntBatchManaged,
                        @Nullable
                        Integer numberOfSerialNumbers,
                        @Nullable
                        String orderID,
                        @Nullable
                        String orderItem,
                        @Nullable
                        BigDecimal originalDeliveryQuantity,
                        @Nullable
                        String originallyRequestedMaterial,
                        @Nullable
                        BigDecimal overdelivTolrtdLmtRatioInPct,
                        @Nullable
                        String packingStatus,
                        @Nullable
                        String partialDeliveryIsAllowed,
                        @Nullable
                        String paymentGuaranteeForm,
                        @Nullable
                        String pickingConfirmationStatus,
                        @Nullable
                        String pickingControl,
                        @Nullable
                        String pickingStatus,
                        @Nullable
                        String plant,
                        @Nullable
                        String primaryPostingSwitch,
                        @Nullable
                        Calendar productAvailabilityDate,
                        @Nullable
                        Calendar productAvailabilityTime,
                        @Nullable
                        String productConfiguration,
                        @Nullable
                        String productHierarchyNode,
                        @Nullable
                        String profitabilitySegment,
                        @Nullable
                        String profitCenter,
                        @Nullable
                        String proofOfDeliveryRelevanceCode,
                        @Nullable
                        String proofOfDeliveryStatus,
                        @Nullable
                        Boolean quantityIsFixed,
                        @Nullable
                        String receivingPoint,
                        @Nullable
                        String referenceDocumentLogicalSystem,
                        @Nullable
                        String referenceSDDocument,
                        @Nullable
                        String referenceSDDocumentCategory,
                        @Nullable
                        String referenceSDDocumentItem,
                        @Nullable
                        String retailPromotion,
                        @Nullable
                        String salesDocumentItemType,
                        @Nullable
                        String salesGroup,
                        @Nullable
                        String salesOffice,
                        @Nullable
                        String sDDocumentCategory,
                        @Nullable
                        String sDProcessStatus,
                        @Nullable
                        Calendar shelfLifeExpirationDate,
                        @Nullable
                        Calendar statisticsDate,
                        @Nullable
                        String stockType,
                        @Nullable
                        String storageBin,
                        @Nullable
                        String storageLocation,
                        @Nullable
                        String storageType,
                        @Nullable
                        String subsequentMovementType,
                        @Nullable
                        String transportationGroup,
                        @Nullable
                        BigDecimal underdelivTolrtdLmtRatioInPct,
                        @Nullable
                        Boolean unlimitedOverdeliveryIsAllowed,
                        @Nullable
                        BigDecimal varblShipgProcgDurationInDays,
                        @Nullable
                        String warehouse,
                        @Nullable
                        String warehouseActivityStatus,
                        @Nullable
                        String warehouseStagingArea,
                        @Nullable
                        String warehouseStockCategory,
                        @Nullable
                        String warehouseStorageBin,
                        @Nullable
                        ErpConfigContext erpConfigContext,
                        List<OutbDeliveryDocFlow> toDocumentFlow,
                        @Nullable
                        SerialNmbrDelivery toSerialDeliveryItem)
```
- Method Detail
  - getType
```
public Class<OutbDeliveryItem> getType()
```
    Specified by:
    
    getType in class VdmObject<OutbDeliveryItem>
    
    Returns:
    
    The class of this object.
  - field
```
public static <T> OutbDeliveryItemField<T> field(String fieldName,
                                                 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.
  - fetchDocumentFlow
```
public List<OutbDeliveryDocFlow> fetchDocumentFlow()
                                            throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the OutbDeliveryDocFlow entities (one to many) associated with this entity. This corresponds to the OData navigation property to_DocumentFlow.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated OutbDeliveryDocFlow 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.
  - getDocumentFlowOrFetch
```
public List<OutbDeliveryDocFlow> getDocumentFlowOrFetch()
                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated OutbDeliveryDocFlow entities (one to many).
    If the navigation property to_DocumentFlow of a queried OutbDeliveryItem 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 OutbDeliveryDocFlow 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.
  - getDocumentFlowOrNull
```
public com.google.common.base.Optional<List<OutbDeliveryDocFlow>> getDocumentFlowOrNull()
```
    Retrieval of associated OutbDeliveryDocFlow entities (one to many).
    If the navigation property to_DocumentFlow for an entity OutbDeliveryItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_DocumentFlow is already loaded, the result will contain the OutbDeliveryDocFlow entities. If not, a null value state is returned.
  - setDocumentFlow
```
public void setDocumentFlow(@NonNull
                            List<OutbDeliveryDocFlow> value)
```
    Overwrites the list of associated OutbDeliveryDocFlow entities for the loaded navigation property to_DocumentFlow.
    If the navigation property to_DocumentFlow of a queried OutbDeliveryItem 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 OutbDeliveryDocFlow entities.
  - addDocumentFlow
```
public void addDocumentFlow(OutbDeliveryDocFlow... entity)
```
    Adds elements to the list of associated OutbDeliveryDocFlow entities.
    If the navigation property to_DocumentFlow of a queried OutbDeliveryItem 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 OutbDeliveryDocFlow entities.
  - fetchSerialDeliveryItem
```
public SerialNmbrDelivery fetchSerialDeliveryItem()
                                           throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SerialNmbrDelivery entity (one to one) associated with this entity. This corresponds to the OData navigation property to_SerialDeliveryItem.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated SerialNmbrDelivery entity, or null if an entity is not associated.
    
    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.
  - getSerialDeliveryItemOrFetch
```
public SerialNmbrDelivery getSerialDeliveryItemOrFetch()
                                                throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SerialNmbrDelivery entity (one to one).
    If the navigation property to_SerialDeliveryItem of a queried OutbDeliveryItem 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 SerialNmbrDelivery entity.
    
    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.
  - getSerialDeliveryItemOrNull
```
public com.google.common.base.Optional<SerialNmbrDelivery> getSerialDeliveryItemOrNull()
```
    Retrieval of associated SerialNmbrDelivery entity (one to one).
    If the navigation property to_SerialDeliveryItem for an entity OutbDeliveryItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_SerialDeliveryItem is already loaded, the result will contain the SerialNmbrDelivery entity. If not, a null value state is returned.
  - setSerialDeliveryItem
```
public void setSerialDeliveryItem(SerialNmbrDelivery value)
```
    Overwrites the associated SerialNmbrDelivery entity for the loaded navigation property to_SerialDeliveryItem.
    
    Parameters:
    
    value - New SerialNmbrDelivery entity.
  - builder
```
public static OutbDeliveryItem.OutbDeliveryItemBuilder builder()
```
  - getActualDeliveredQtyInBaseUnit
```
@Nullable
public BigDecimal getActualDeliveredQtyInBaseUnit()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Returns:
    
    The item quantity, expressed in base units of measure.
  - getDeliveryVersion
```
@Nullable
public String getDeliveryVersion()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Delivery Version
  - getActualDeliveryQuantity
```
@Nullable
public BigDecimal getActualDeliveryQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    The delivery quantity may be proposed from a sales order item. You can change the quantity in the delivery, subject to any limitations that apply to over- and underdeliveries. If the delivery does not refer to a sales order, you can enter a delivery quantity manually.
    
    Returns:
    
    The quantity of the item for delivery. The quantity is expressed in sales units.
  - getAdditionalCustomerGroup1
```
@Nullable
public String getAdditionalCustomerGroup1()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup2
```
@Nullable
public String getAdditionalCustomerGroup2()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup3
```
@Nullable
public String getAdditionalCustomerGroup3()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup4
```
@Nullable
public String getAdditionalCustomerGroup4()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup5
```
@Nullable
public String getAdditionalCustomerGroup5()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalMaterialGroup1
```
@Nullable
public String getAdditionalMaterialGroup1()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup2
```
@Nullable
public String getAdditionalMaterialGroup2()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup3
```
@Nullable
public String getAdditionalMaterialGroup3()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup4
```
@Nullable
public String getAdditionalMaterialGroup4()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup5
```
@Nullable
public String getAdditionalMaterialGroup5()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAlternateProductNumber
```
@Nullable
public String getAlternateProductNumber()
```
    Constraints: Not nullable, Maximum length: 40
    It does not need to be created as its own material master in the ERP system. Within Logistics Execution in the ERP system, it is stored without validation. The translation to the internal material number needs to be provided in the external system or within an implementation of a Business Add-In (BAdI).
    
    Returns:
    
    The Alternate Product Number (APN) is an alternative identification of the product that the business partner uses.
  - getBaseUnit
```
@Nullable
public String getBaseUnit()
```
    Constraints: Not nullable, Maximum length: 3
    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 Management In Inventory Management, the base unit of measure is the same as the stockkeeping unit. Services Services have units of measure of their own, including the following: Service unit Unit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level. Blanket Unit 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.
  - getBatch
```
@Nullable
public String getBatch()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Assigns a material that is manufactured in batches or production lots to a specific batch.
  - getBatchBySupplier
```
@Nullable
public String getBatchBySupplier()
```
    Constraints: Not nullable, Maximum length: 15
    
    Returns:
    
    Number under which the batch is managed at the supplier's.
  - getBatchClassification
```
@Nullable
public String getBatchClassification()
```
    Constraints: Not nullable, Maximum length: 18
    You are required by the authorities (for example, the Food and Drug Authority in the USA) to keep a record of the selection values used to locate a particular batch so that you are always able to compare these values with the original specifications. This internal number enables you to meet this requirement.
    
    Returns:
    
    Number assigned by the system which indicates the selection values by which the batch was found.
  - getBOMExplosion
```
@Nullable
public String getBOMExplosion()
```
    Constraints: Not nullable, Maximum length: 8
    
    Returns:
    
    Number used by the component supplier to identify the production series from which the customer releases and receives materials.
  - getBusinessArea
```
@Nullable
public String getBusinessArea()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Key that uniquely identifies a business area.
  - getConsumptionPosting
```
@Nullable
public String getConsumptionPosting()
```
    Constraints: Not nullable, Maximum length: 1
    The indicator is used in the case of goods receipts for purchase orders and is derived from the account assignment category of the purchase order.
    
    Returns:
    
    Specifies that the consumption is to be posted to a consumption account (V) or an asset account (A).
  - getControllingArea
```
@Nullable
public String getControllingArea()
```
    Constraints: Not nullable, Maximum length: 4
    The controlling area is the highest organizational unit in Controlling. Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
    
    Returns:
    
    Uniquely identifies a controlling area.
  - getCostCenter
```
@Nullable
public String getCostCenter()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    A key that uniquely identifies a cost center.
  - getCreatedByUser
```
@Nullable
public String getCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    
    Returns:
    
    Name of Person Who Created Object
  - getCreationDate
```
@Nullable
public Calendar getCreationDate()
```
    Constraints: Not nullable, Precision: 7
    
    Returns:
    
    Date on Which Record Was Created
  - getCreationTime
```
@Nullable
public Calendar getCreationTime()
```
    Constraints: Not nullable, Precision: 0
    
    Returns:
    
    The time of day at which the document was posted and stored in the system.
  - getCustEngineeringChgStatus
```
@Nullable
public String getCustEngineeringChgStatus()
```
    Constraints: Not nullable, Maximum length: 17
    The customer sends this number in with a material number to request an engineering change to take effect as of a certain delivery date or cumulative quantity.
    
    Returns:
    
    Customer number for the production series from which they release and receive materials.
  - getDeliveryDocument
```
@Nullable
public String getDeliveryDocument()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    The number that uniquely identifies the delivery.
  - getDeliveryDocumentItem
```
@Nullable
public String getDeliveryDocumentItem()
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    The number that uniquely identifies the item in a delivery.
  - getDeliveryDocumentItemCategory
```
@Nullable
public String getDeliveryDocumentItemCategory()
```
    Constraints: Not nullable, Maximum length: 4
    The delivery item category determines how the system processes an item. If, for example, you identify an item as a return item, you tell the system, in this case, that the item is not relevant for picking. The system proposes a delivery item category.
    
    Returns:
    
    A classification that distinguishes between different types of delivery items (for example, return items and text items).
  - getDeliveryDocumentItemText
```
@Nullable
public String getDeliveryDocumentItemText()
```
    Constraints: Not nullable, Maximum length: 40
    Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations. The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
    
    Returns:
    
    A short description of the item.
  - getDeliveryGroup
```
@Nullable
public String getDeliveryGroup()
```
    Constraints: Not nullable, Maximum length: 3
    The system uses delivery groups to check the availability of items that should be delivered together. The delivery date of the latest schedule line in the delivery group is taken as the general date for the whole group. During sales order processing, you can enter a number (up to three digits) that identifies a delivery group. The number is freely definable. If necessary, the system adjusts requirements that have already been created and changes the material availability dates for individual items to the delivery date that it has determined for the group. If a typewriter is usually delivered with a case, you can define the two items as a delivery group. If an item has more than one schedule line with a confirmed quantity, then the system deletes all undelivered schedule lines up to the last one. The system automatically carries over the quantities from the deleted schedule lines into the last one. If necessary, the system changes the delivery date of the last schedule line to that of the delivery group.
    
    Returns:
    
    A combination of items that should be delivered together.
  - getDeliveryQuantityUnit
```
@Nullable
public String getDeliveryQuantityUnit()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Unit of measure in which the material is sold.
  - getDeliveryRelatedBillingStatus
```
@Nullable
public String getDeliveryRelatedBillingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you if the item is not yet billed, is partly billed, is completely billed, or is not relevant for billing.
    
    Returns:
    
    Displays the billing status of the item.
  - getDeliveryToBaseQuantityDnmntr
```
@Nullable
public BigDecimal getDeliveryToBaseQuantityDnmntr()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Returns:
    
    Denominator of the conversion factor that the system uses to convert sales units base units of measure.
  - getDeliveryToBaseQuantityNmrtr
```
@Nullable
public BigDecimal getDeliveryToBaseQuantityNmrtr()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Returns:
    
    Numerator of the conversion factor that the system uses to convert sales units base units of measure.
  - getDepartmentClassificationByCust
```
@Nullable
public String getDepartmentClassificationByCust()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Identifies the department for which the contact person works (for example: purchasing, accounting, marketing, etc.)
  - getDistributionChannel
```
@Nullable
public String getDistributionChannel()
```
    Constraints: Not nullable, Maximum length: 2
    You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel. You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel. For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Returns:
    
    The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.
  - getDivision
```
@Nullable
public String getDivision()
```
    Constraints: Not nullable, Maximum length: 2
    A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
    
    Returns:
    
    A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.
  - getFixedShipgProcgDurationInDays
```
@Nullable
public BigDecimal getFixedShipgProcgDurationInDays()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    
    Returns:
    
    Fixed shipping processing time in days (= setup time)
  - getGLAccount
```
@Nullable
public String getGLAccount()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    The G/L account number identifies the G/L account in a chart of accounts.
  - getGoodsMovementReasonCode
```
@Nullable
public String getGoodsMovementReasonCode()
```
    Constraints: Not nullable, Maximum length: 4
    Please do not change the entry in this field. Any changes made could lead to program errors or terminations.
    
    Returns:
    
    This indicator is used for internal program control.
  - getGoodsMovementStatus
```
@Nullable
public String getGoodsMovementStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status provides the following information: For an outbound delivery, the status informs you whether the item has already left the warehouse or company premises, or still being processed. For an inbound delivery, the system shows you whether the goods have already been received, or are waiting to be received. The status also informs you whether or not an item is relevant for delivery. A text item is not relevant, for example.
    
    Returns:
    
    The status shows if a goods issue or receipt has taken place for a delivery item.
  - getGoodsMovementType
```
@Nullable
public String getGoodsMovementType()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Specifies a key for the type of goods movement. Each goods movement (for example, purchase order to warehouse) is allocated to a movement type in the system.
  - getHigherLevelItem
```
@Nullable
public String getHigherLevelItem()
```
    Constraints: Not nullable, Maximum length: 6
    Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
    
    Returns:
    
    The number of the higher-level item to which this item belongs in a hierarchy.
  - getInspectionLot
```
@Nullable
public String getInspectionLot()
```
    Constraints: Not nullable, Maximum length: 12
    The inspection lot number is assigned by the system.
    
    Returns:
    
    Number that uniquely identifies an inspection lot.
  - getInspectionPartialLot
```
@Nullable
public String getInspectionPartialLot()
```
    Constraints: Not nullable, Maximum length: 6
    You can process partial lots by: Inspecting during production using inspection points Running a batch split for the delivery note
    
    Returns:
    
    The partial lot's number, which is only unique within the corresponding inspection lot.
  - getIntercompanyBillingStatus
```
@Nullable
public String getIntercompanyBillingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Intercompany Billing Status
  - getInternationalArticleNumber
```
@Nullable
public String getInternationalArticleNumber()
```
    Constraints: Not nullable, Maximum length: 18
    
    Returns:
    
    Glossary definition
  - getInventorySpecialStockType
```
@Nullable
public String getInventorySpecialStockType()
```
    Constraints: Not nullable, Maximum length: 1
    If you need to separately manage certain stock (for example, consignment stock) of a material, the stock type in question is defined using this indicator.
    
    Returns:
    
    Specifies the special stock type.
  - getInventoryValuationType
```
@Nullable
public String getInventoryValuationType()
```
    Constraints: Not nullable, Maximum length: 10
    The valuation types allowed for a material are determined by the valuation category. If a material is valuated according to its origin (valuation category H), you can define the possible countries of origin as valuation types.
    
    Returns:
    
    Uniquely identifies separately valuated stocks of a material.
  - getIsCompletelyDelivered
```
@Nullable
public Boolean getIsCompletelyDelivered()
```
    Constraints: none
    
    Returns:
    
    Indicates that the item is to be regarded as closed.
  - getIsNotGoodsMovementsRelevant
```
@Nullable
public String getIsNotGoodsMovementsRelevant()
```
    Constraints: Not nullable, Maximum length: 1
    When this indicator is set, goods movement is not posted for this item - regardless of the movement type assigned to it.
    
    Returns:
    
    You can use this indicator to control whether the item is relevant for goods movement when the delivery is still being created.
  - getIsSeparateValuation
```
@Nullable
public Boolean getIsSeparateValuation()
```
    Constraints: none
    
    Returns:
    
    Indicator: Separate valuation
  - getIssgOrRcvgBatch
```
@Nullable
public String getIssgOrRcvgBatch()
```
    Constraints: Not nullable, Maximum length: 10
    The "receiving batch" is the number of the batch under which the quantity to be transferred is now to be recorded. The "issuing batch" (in the case of a reversal) is the number of the batch from which a quantity is to be deducted.
    
    Returns:
    
    Specifies the receiving/issuing batch.
  - getIssgOrRcvgMaterial
```
@Nullable
public String getIssgOrRcvgMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    The "receiving material" is the material number under which the quantity to be transferred is now to be recorded. The "issuing material" (in the case of a reversal) is the material from whose stock a certain quantity is to be deducted. Note The value of the transfer posting is determined not by the material entered here but by the material specified in the Material field. Note the following with regard to the receiving/issuing material: The material must exist The material must be managed in the same stockkeeping unit as the issuing material
    
    Returns:
    
    Indicates the receiving/issuing material.
  - getIssgOrRcvgSpclStockInd
```
@Nullable
public String getIssgOrRcvgSpclStockInd()
```
    Constraints: Not nullable, Maximum length: 1
    This indicator is used, for example, in the case of the physical transfer of a consignment material and when consignment material is transferred from the supplier's stock to the company's own stock.
    
    Returns:
    
    Specifies the special stock indicator in the second posting line of a document item.
  - getIssgOrRcvgStockCategory
```
@Nullable
public String getIssgOrRcvgStockCategory()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Uniquely identifies a specific warehouse stock of a material, for example, quality inspection stock, returned stock, and so on.
  - getIssgOrRcvgValuationType
```
@Nullable
public String getIssgOrRcvgValuationType()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Key used in the split valuation of materials (that is, the separate valuation of different stocks of the same material) to permit stocks of a transfer batch to be differentiated according to different criteria.
  - getIssuingOrReceivingPlant
```
@Nullable
public String getIssuingOrReceivingPlant()
```
    Constraints: Not nullable, Maximum length: 4
    The receiving plant is the plant or internal organizational unit that is to receive the goods. The issuing plant is the plant that issues the goods. Note The value of the transfer posting is determined not by the plant entered here but by the plant specified in the Plant field.
    
    Returns:
    
    Indicates the receiving or issuing plant.
  - getIssuingOrReceivingStorageLoc
```
@Nullable
public String getIssuingOrReceivingStorageLoc()
```
    Constraints: Not nullable, Maximum length: 4
    The receiving storage location is the storage location that is to receive the goods. The issuing storage location is the storage location that issues the goods.
    
    Returns:
    
    Indicates the receiving or the issuing storage location.
  - getItemBillingBlockReason
```
@Nullable
public String getItemBillingBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    The system can automatically propose a billing block for sales documents that must be checked before billing (for example, returns, credit and debit memo requests). If the system proposes a block, you can change the block manually for each item. If the system does not propose a block, enter one of values predefined for your system. If the item has more than one schedule line, the block applies to each line. You can change the block for individual schedule lines.
    
    Returns:
    
    Indicates if the item is blocked for billing.
  - getItemBillingIncompletionStatus
```
@Nullable
public String getItemBillingIncompletionStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you to what extent the information necessary for billing the item is complete. A sales order item, for example, is incomplete for billing if prices are missing. You cannot bill the item until you provide the missing information.
    
    Returns:
    
    Displays the incompletion status of billing-related information that applies to this item.
  - getItemDeliveryIncompletionStatus
```
@Nullable
public String getItemDeliveryIncompletionStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you if delivery-related item information is complete. You must enter this information, if you want to process the item further. A sales order item is incomplete for delivery processing if, for example, you do not enter a shipping point. You cannot deliver the item until you provide this information.
    
    Returns:
    
    Displays the status of delivery-related information that applies to this item.
  - getItemGdsMvtIncompletionSts
```
@Nullable
public String getItemGdsMvtIncompletionSts()
```
    Constraints: Not nullable, Maximum length: 1
    The status provides information on how far the data required for billing the item is complete. A sales document item is incomplete for billing, for example, if price specifications are missing. You can only invoice the item if you have completed the missing data.
    
    Returns:
    
    Shows the incompletion status of data relevant for billing documents that concerns this item.
  - getItemGeneralIncompletionStatus
```
@Nullable
public String getItemGeneralIncompletionStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you if all item information, necessary for further processing this item, is complete.
    
    Returns:
    
    Displays the status of all information that applies to this item.
  - getItemGrossWeight
```
@Nullable
public BigDecimal getItemGrossWeight()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order. If there is no related sales order, the system uses the gross weight from the material master record. You can change the gross weight manually in the delivery document.
    
    Returns:
    
    The total gross weight of all items in the delivery. The gross weight represents the net weight plus the weight of packaging.
  - getItemIsBillingRelevant
```
@Nullable
public String getItemIsBillingRelevant()
```
    Constraints: Not nullable, Maximum length: 1
    A: Relevant for delivery-related billing Billing is based on the outbound delivery. The billing status is only updated in the outbound delivery. B: Relevant for order-related billing Billing is based on the sales document. The billing status depends on the requested delivery quantity. Item categories REN (returns) and BVN (cash sales items) are set up with billing relevance B in the standard system. C: Relevant for order-related billing Billing is based on the sales document. The billing status depends on the target quantity. Item categories G2N (credit memo) and L2N (debit memo) are set up with billing relevance C in the standard system. D: Relevant for pro forma To create a pro forma invoice, the billing relevance indicator must not be blank. Indicator D is also used as follows for cross-company-code business processing: If there are free-of-charge outbound deliveries, the company code that is responsible for the delivery should be granted an internal settlement. You can use indicator D to enable this for free-of-charge deliveries. F: Relevant for order-related billing - Status based on invoice receipt quantity Relevant for order-related billing based on the invoice receipt quantity (third-party business). The system does not transfer the order to the billing due list until the vendor invoice has been received and processed in the purchasing department. After each invoice receipt, a customer invoice is created for the quantity that appears on the vendor invoice. The order has status "Billed" until the next vendor invoice is received. Item category TAS (third-party business) is set up with billing relevance F in the standard system. This process can also be related to the goods receipt quantity. You can make the control setting as to whether the invoice receipt quantity or the goods receipt quantity is relevant for billing in the copy control for billing on the item level in the billing quantity field. G: Relevant for order-related billing of the delivery quantity The order is relevant for billing; more specifically, the cumulated quantity that has already been delivered is relevant. You can use this category to bill for multiple partial deliveries in one process. H: Relevant for delivery-related billing – no zero quantities You can use this category to prevent items with a value of zero from being included in billing. I: Relevant for order-related billing – billing plan Billing takes place using the billing plan and its status. The status of the order item can be understood as the overall status of the billing plan billing statuses. Item categories WVN (maintenance contract item), MVN (lease item), and TAO (milestone billing) are set up with billing relevance I in the standard system. J: Relevant for deliveries across EU countries The delivery is only relevant for billing if: The country of departure (country where plant is located) and destination country (country where ship-to party is located) are different EU countries. Item categories KBN (consignment fill-up), KAN (consignment pick-up), and NLN (standard stock transfer item) are set up with billing relevance J in the standard system. K: Relevant for delivery-related partial quantity billing You use this indicator if you want to select both items and partial quantities for billing.
    
    Returns:
    
    Indicates what should be the basis for billing.
  - getItemNetWeight
```
@Nullable
public BigDecimal getItemNetWeight()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record. You can change the net weight manually in the delivery document.
    
    Returns:
    
    The total net weight of all items in the delivery.
  - getItemPackingIncompletionStatus
```
@Nullable
public String getItemPackingIncompletionStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status indicates the degree to which the data required for billing the item are complete. For example, a sales order item is incomplete for billing if prices are missing. You cannot bill the item unless you have entered the missing data.
    
    Returns:
    
    Displays the incomplete status of billing-relevant data for this item.
  - getItemPickingIncompletionStatus
```
@Nullable
public String getItemPickingIncompletionStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status indicates whether the delivery-related item data is complete. You must enter these data if you want to further process the item. For example, a sales order item is incomplete for delivery processing if you do not specify a shipping point. You cannot deliver the item unless you have entered these data.
    
    Returns:
    
    Displays the status of the delivery-related data for this item.
  - getItemVolume
```
@Nullable
public BigDecimal getItemVolume()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order. If there is no related sales order, the system uses the volume from the material master record. You can change the volume manually in the delivery document.
    
    Returns:
    
    The total volume of all items in the delivery.
  - getItemVolumeUnit
```
@Nullable
public String getItemVolumeUnit()
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a volume, you have to enter the corresponding volume unit here.
    
    Returns:
    
    Unit referring to the volume of the material.
  - getItemWeightUnit
```
@Nullable
public String getItemWeightUnit()
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a weight, you must enter the corresponding unit of weight here.
    
    Returns:
    
    Unit referring to the gross weight or net weight of the material.
  - getLastChangeDate
```
@Nullable
public Calendar getLastChangeDate()
```
    Constraints: Not nullable, Precision: 7
    
    Returns:
    
    Date of Last Change
  - getLoadingGroup
```
@Nullable
public String getLoadingGroup()
```
    Constraints: Not nullable, Maximum length: 4
    The system uses the loading group as well as the Shipping conditions and Delivering plant to automatically determine the shipping point for the item. Different loading groups could consist, for example, of materials that require the same: Equipment during loading (for example, a fork-lift truck) Amount of time for loading Loading point (for example, loading bay #6)
    
    Returns:
    
    A grouping of materials that share the same loading requirements.
  - getManufactureDate
```
@Nullable
public Calendar getManufactureDate()
```
    Constraints: Not nullable, Precision: 7
    
    Returns:
    
    Date of Manufacture
  - getMaterial
```
@Nullable
public String getMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getMaterialByCustomer
```
@Nullable
public String getMaterialByCustomer()
```
    Constraints: Not nullable, Maximum length: 35
    The customer's own identifier for a material can be stored in a customer-material info record and can be used to enter data during sales order processing.
    
    Returns:
    
    The identifier that the customer uses to identify a particular material.
  - getMaterialFreightGroup
```
@Nullable
public String getMaterialFreightGroup()
```
    Constraints: Not nullable, Maximum length: 8
    Freight codes and classes in a freight code set are determined by the material freight group. The freight code set is used to determine freight costs and for communication with service agents. Maintain the corresponding group for the material.
    
    Returns:
    
    The material freight group is used to group materials so that they can be classifed according to freight code and class.
  - getMaterialGroup
```
@Nullable
public String getMaterialGroup()
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Returns:
    
    Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - getMaterialIsBatchManaged
```
@Nullable
public Boolean getMaterialIsBatchManaged()
```
    Constraints: none
    This indicator can be set in the material master record manually or, if batches are valuated individually, it is set automatically for the plants concerned, in which case it cannot be changed. The indicator cannot be changed if stocks exist in either the current period or in the previous period. The reason for checking the previous period is because stocks can be posted to this period when goods movements are entered.
    
    Returns:
    
    Specifies whether the material is managed in batches.
  - getMaterialIsIntBatchManaged
```
@Nullable
public Boolean getMaterialIsIntBatchManaged()
```
    Constraints: none
    
    Returns:
    
    Indicator that specifies that the material is managed in batches.
  - getNumberOfSerialNumbers
```
@Nullable
public Integer getNumberOfSerialNumbers()
```
    Constraints: none
    
    Returns:
    
    Specifies the number of serial numbers which have been created for a material.
  - getOrderID
```
@Nullable
public String getOrderID()
```
    Constraints: Not nullable, Maximum length: 12
    
    Returns:
    
    Key that uniquely identifies an order within a client.
  - getOrderItem
```
@Nullable
public String getOrderItem()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Uniquely identifies the order item.
  - getOriginalDeliveryQuantity
```
@Nullable
public BigDecimal getOriginalDeliveryQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    When creating the inbound delivery, the notified quantity is transferred as the original quantity. Should you want to change the notified quantity at a later point in time, because the actual quantity delivered is different, you can decide whether or not you want this change to be displayed in the Original Quantity field. Should you want to change the delivery quantity in an inbound delivery that already exists in the system, then you will receive a dialog box with the following choices: If you choose Yes, the delivery quantity will be changed and the originally/previously notified quantity will continue to be displayed in the Original Quantity field. This will then document in the system that the vendor actually delivered a different quantity than that originally notified. If you choose No, the delivery quantity will be changed and the previously notified quantity shown in the Original Quantity field will be overwritten with the new delivery quantity. In this case, the delivery quantity that was changed by the vendor will not be documented in the system. In the confirmation overview of the scheduling agreement, the fields Quantity and Original Quantity show you whether or not the vendor actually delivered the quantity he originally notified you of. In a shipping notification, your vendor notifies you of the impending delivery of 450 pc Steel_01. When the inbound delivery is created, the 450 pc are recorded as delivery quantity and original quantity. However, you vendor actually delivers 500 pc. You therefore change the delivery quantity in the inbound delivery. A dialog box then appears, offering you the following options: Yes - Document originally notified quantity Result The delivery quantity is changed to 500 pc and the quantity variance is documented, i.e. the originally notified quantity of 450 pc continues to be shown in the Original Quantity field. No - Do not document originally notified quantity Result The delivery quantity is changed to 500 pc and the quantity variance is not documented, i.e. the originally notified quantity of 450 pc shown in the Original Quantity field is replaced by the quantity 500 pc actually delivered. Note If you use this function, then the GR assignment should be set in Customizing for Purchasing, in the confirmation control for the used confirmation categories.
    
    Returns:
    
    Contains the original notified quantity.
  - getOriginallyRequestedMaterial
```
@Nullable
public String getOriginallyRequestedMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
    
    Returns:
    
    Material originally requested by the customer.
  - getOverdelivTolrtdLmtRatioInPct
```
@Nullable
public BigDecimal getOverdelivTolrtdLmtRatioInPct()
```
    Constraints: Not nullable, Precision: 3, Scale: 1
    If you have set the indicator in the Partial delivery/Item field to 'D' (partial delivery allowed), this takes priority. It makes no sense to define a tolerance limit for overdelivery in such case.
    
    Returns:
    
    Percentage (based on the order quantity) up to which an overdelivery of this item will be accepted.
  - getPackingStatus
```
@Nullable
public String getPackingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Packing status of item
  - getPartialDeliveryIsAllowed
```
@Nullable
public String getPartialDeliveryIsAllowed()
```
    Constraints: Not nullable, Maximum length: 1
    You use this field to control partial deliveries at the item level. If the customer allows partial delivery, you can choose from different partial delivery options. For example, you can specify whether the customer allows you to make one delivery attempt only on the requested delivery date or whether unlimited delivery attempts are possible. When partial delivery indicator 'D' is set, the order can never have status 'fully delivered'. You must complete each item by entering a reason for rejection. This could be applied to scheduling agreements, for example. You can enter a value in this field only if the customer allows partial deliveries for the entire sales document.
    
    Returns:
    
    Specifies whether the customer requires full or partial delivery for the item.
  - getPaymentGuaranteeForm
```
@Nullable
public String getPaymentGuaranteeForm()
```
    Constraints: Not nullable, Maximum length: 2
    The form of payment guarantee specifies how a sales document item is guaranteed. Payment cards Letter of credit Standby letter of credit Bank guarantee
    
    Returns:
    
    This code identifies the form of payment guarantee.
  - getPickingConfirmationStatus
```
@Nullable
public String getPickingConfirmationStatus()
```
    Constraints: Not nullable, Maximum length: 1
    When you create a delivery with an item subject to pick/putaway confirmation, the item is assigned the status A (Subject to confirmation but not yet confirmed). Once you confirm the pick/putaway, the system assigns either status B (Partially confirmed) or C (Fully confirmed). Goods movement cannot be posted for items subject to pick/putaway confirmation until the pick/putaway quantities for the items have been fully confirmed.
    
    Returns:
    
    Indicates the pick/putaway confirmation status for a delivery item.
  - getPickingControl
```
@Nullable
public String getPickingControl()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Indicator for picking control
  - getPickingStatus
```
@Nullable
public String getPickingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status message tells you whether the item is relevant for delivery. If the item is relevant for delivery, the status indicates whether picking/putaway has: Begun Been partially carried out Been completed Picking/putaway is not relevant for some items, for example, text items or service items.
    
    Returns:
    
    The picking/putaway status of the delivery item.
  - getPlant
```
@Nullable
public String getPlant()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Key uniquely identifying a plant.
  - getPrimaryPostingSwitch
```
@Nullable
public String getPrimaryPostingSwitch()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Indicator: UNMAT in main posting
  - getProductAvailabilityDate
```
@Nullable
public Calendar getProductAvailabilityDate()
```
    Constraints: Not nullable, Precision: 7
    The system uses the material availability date to generate automatic production and purchasing requirements. The system calculates the material availability date by working backwards from the customer's requested delivery date, taking into account how much time is needed for delivery-related procedures, such as picking, packing, loading, and transportation. The system proposes the material availability date. You can change the date manually in the sales document. The picking date is the same as the material availability date.
    
    Returns:
    
    The date by which sufficient quantities of the item must be available for picking to begin.
  - getProductAvailabilityTime
```
@Nullable
public Calendar getProductAvailabilityTime()
```
    Constraints: Not nullable, Precision: 0
    
    Returns:
    
    Material Staging Time (Local, Relating to a Plant)
  - getProductConfiguration
```
@Nullable
public String getProductConfiguration()
```
    Constraints: Not nullable, Maximum length: 18
    This number clearly identifies one particular configuration of a standard product.
    
    Returns:
    
    Specifies the internal object number which links a standard product to a class type.
  - getProductHierarchyNode
```
@Nullable
public String getProductHierarchyNode()
```
    Constraints: Not nullable, Maximum length: 18
    In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters. Level Number of characters allowed 1 5 2 5 3 8 You define a product hierarchy with the following levels: Level Example Description 1 00005 Electrical goods 2 00003 Wet appliances 3 00000001 Washing machine In this case, a washing machine belongs to the product hierarchy 000050000300000001.
    
    Returns:
    
    Alphanumeric character string for grouping together materials by combining different characteristics. It is used for analyses and price determination.
  - getProfitabilitySegment
```
@Nullable
public String getProfitabilitySegment()
```
    Constraints: Not nullable, Maximum length: 10
    Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
    
    Returns:
    
    See glossary
  - getProfitCenter
```
@Nullable
public String getProfitCenter()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Key which together with the controlling area uniquely identifies a profit center.
  - getProofOfDeliveryRelevanceCode
```
@Nullable
public String getProofOfDeliveryRelevanceCode()
```
    Constraints: Not nullable, Maximum length: 1
    The indicator can have the following settings: ' ': not POD relevant 'A' : always POD relevant 'B' : only POD relevant when there are quantity differences The indicator is copied from the purchasing or sales document into the delivery, if control of POD relevance in the delivery item category is set to "Copy POD relevance from preceding document".
    
    Returns:
    
    This indicator controls the POD relevance of a delivery item along with the delivery item category, that is to say, whether a delivery item is relevant for proof of delivery on the ship-to party side.
  - getProofOfDeliveryStatus
```
@Nullable
public String getProofOfDeliveryStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The status message informs you whether the ship-to party reported a proof of delivery for this item. This status may have the following values for a delivery item: ' ' Not relevant for the POD process 'A' Relevant for the POD process 'B' Differences were reported 'C' Quantities were verified and confirmed
    
    Returns:
    
    Proof of delivery status (POD status) per item
  - getQuantityIsFixed
```
@Nullable
public Boolean getQuantityIsFixed()
```
    Constraints: none
    Set this indicator if the quantity in a relational system does not change. If an item of a BOM is marked as being fixed and the quantity of the finished product to be manufactured is changed, the quantity of this item does not change. If a "materials to be provided" item is not marked as being fixed, and the quantity of the subcontracted item is changed, the quantity of the material to be provided to the subcontractor changes proportionately.
    
    Returns:
    
    Determines that the quantity of an item is constant.
  - getReceivingPoint
```
@Nullable
public String getReceivingPoint()
```
    Constraints: Not nullable, Maximum length: 25
    Several receiving points can be defined for each plant. The receiving points can then be assigned to individual departments. The receiving point can be printed on delivery documents (SD function).
    
    Returns:
    
    A receiving point is a location close to the address or the unloading point of the goods recipient.
  - getReferenceDocumentLogicalSystem
```
@Nullable
public String getReferenceDocumentLogicalSystem()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Logical System in the Preceding Document
  - getReferenceSDDocument
```
@Nullable
public String getReferenceSDDocument()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Identifies the sales order to which the delivery refers.
  - getReferenceSDDocumentCategory
```
@Nullable
public String getReferenceSDDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Specifies the sales document category of the preceding sales, delivery, or billing document.
  - getReferenceSDDocumentItem
```
@Nullable
public String getReferenceSDDocumentItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    The number of the sales order item to which the delivery item refers.
  - getRetailPromotion
```
@Nullable
public String getRetailPromotion()
```
    Constraints: Not nullable, Maximum length: 10
    For each item of a purchasing document, you can specify the promotion to which the item belongs. Depending on your system settings, special prices and conditions that are maintained in the IS-R system (Retail) for this promotion are applied when a promotion number is entered. This field also allows you to create purchasing documents on a selective basis for a certain promotion. For example, you can create a purchase order containing only those items that are to be procured for one promotion.
    
    Returns:
    
    Number identifying a promotion for which procurement is to take place.
  - getSalesDocumentItemType
```
@Nullable
public String getSalesDocumentItemType()
```
    Constraints: Not nullable, Maximum length: 1
    The system processes items that refer to a specific material differently than items that do not refer to a material. For example, text items do not require processing for pricing, taxes, and weight calculations.
    
    Returns:
    
    A way of classifying items that require different kinds of processing by the system.
  - getSalesGroup
```
@Nullable
public String getSalesGroup()
```
    Constraints: Not nullable, Maximum length: 3
    By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria. If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market. You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
    
    Returns:
    
    A group of sales people who are responsible for processing sales of certain products or services.
  - getSalesOffice
```
@Nullable
public String getSalesOffice()
```
    Constraints: Not nullable, Maximum length: 4
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Returns:
    
    A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.
  - getSDDocumentCategory
```
@Nullable
public String getSDDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 4
    The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
    
    Returns:
    
    A classification for the different types of documents that you can process in the sales and distribution system (for example: quotations, sales orders, deliveries, and invoices).
  - getSDProcessStatus
```
@Nullable
public String getSDProcessStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
    
    Returns:
    
    Displays the overall processing status of the item.
  - getShelfLifeExpirationDate
```
@Nullable
public Calendar getShelfLifeExpirationDate()
```
    Constraints: Not nullable, Precision: 7
    You enter it yourself. You enter a date of production, and the system calculates the shelf life expiration date from the date of production plus the shelf life in days (from the material master record). Note This date can still be changed upon receipt of the usage decision for an inspection lot.
    
    Returns:
    
    The date is set upon goods receipt in one of the following ways:
  - getStatisticsDate
```
@Nullable
public Calendar getStatisticsDate()
```
    Constraints: Not nullable, Precision: 7
    Write a user-exit if you require the system to copy the statistics date to the billing document. The field definition may change depending on the user-exit.
    
    Returns:
    
    Statistics date copied to subsequent documents.
  - getStockType
```
@Nullable
public String getStockType()
```
    Constraints: Not nullable, Maximum length: 1
    Possible stocks are: unrestricted-use stock (blank, F) stock in quality inspection (X, 2) blocked stock (S, 3) Select the corresponding indicator for the stock type required. It is due to earlier release levels that there are two valid values for each stock type. Each value has the same effect.
    
    Returns:
    
    Indicates the stock type to which the given quantity is posted.
  - getStorageBin
```
@Nullable
public String getStorageBin()
```
    Constraints: Not nullable, Maximum length: 10
    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.
  - getStorageLocation
```
@Nullable
public String getStorageLocation()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Number of the storage location at which the material is stored. A plant may contain one or more storage locations.
  - getStorageType
```
@Nullable
public String getStorageType()
```
    Constraints: Not nullable, Maximum length: 3
    A typical warehouse could have the following storage types: Goods receipt area Picking area High-rack storage area Bulk storage area Open storage area Goods 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.
  - getSubsequentMovementType
```
@Nullable
public String getSubsequentMovementType()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Subsequent movement type
  - getTransportationGroup
```
@Nullable
public String getTransportationGroup()
```
    Constraints: Not nullable, Maximum length: 4
    Transportation groups are used for automatic route scheduling during sales order and delivery note processing. Suppose that you sell food products, some of which are perishable and require refrigeration. You create a transportation group that includes all the products that need refrigerated trucks for delivery.
    
    Returns:
    
    A grouping of materials that share the same route and transportation requirements.
  - getUnderdelivTolrtdLmtRatioInPct
```
@Nullable
public BigDecimal getUnderdelivTolrtdLmtRatioInPct()
```
    Constraints: Not nullable, Precision: 3, Scale: 1
    
    Returns:
    
    Percentage (based on the order quantity) up to which an underdelivery of this item will be accepted.
  - getUnlimitedOverdeliveryIsAllowed
```
@Nullable
public Boolean getUnlimitedOverdeliveryIsAllowed()
```
    Constraints: none
    
    Returns:
    
    Indicator that specifies whether unlimited overdelivery can be accepted for the item.
  - getVarblShipgProcgDurationInDays
```
@Nullable
public BigDecimal getVarblShipgProcgDurationInDays()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    The system uses the variable during capacity planning for deliveries. The variable is determined from shipping information stored in the material master record. The system calculates the variable using the following formula: Variable = (Confirmed quantity x Processing time) divided by the base quantity You specify in a material master record that the processing time for shipping the material is 1 hour (processing time) for every 100 pieces (the base quantity). During delivery processing, you ship a delivery item of 300 pieces (the confirmed quantity). In this example, the variable equals 3 hours.
    
    Returns:
    
    The variable that represents the processing time required for shipping a particular quantity of an item.
  - getWarehouse
```
@Nullable
public String getWarehouse()
```
    Constraints: Not nullable, Maximum length: 3
    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.
  - getWarehouseActivityStatus
```
@Nullable
public String getWarehouseActivityStatus()
```
    Constraints: Not nullable, Maximum length: 1
    If your delivery processing includes the SAP Warehouse Management (WM) system, the system automatically indicates the WM status for each item in a delivery.
    
    Returns:
    
    Indicates the warehouse management status of the delivery item.
  - getWarehouseStagingArea
```
@Nullable
public String getWarehouseStagingArea()
```
    Constraints: Not nullable, Maximum length: 10
    Staging areas can be used for different purposes (at the same time, if necessary): o Goods issue o Goods receipt o Cross-docking processes o Direct distribution
    
    Returns:
    
    Organizational unit that is on a hierarchical level below a warehouse.
  - getWarehouseStockCategory
```
@Nullable
public String getWarehouseStockCategory()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Uniquely identifies a specific warehouse stock of a material, for example, quality inspection stock, returned stock, and so on.
  - getWarehouseStorageBin
```
@Nullable
public String getWarehouseStorageBin()
```
    Constraints: Not nullable, Maximum length: 10
    This storage bin is only significant if you do not use SAP warehouse management. It appears on goods receipt/issue slips. However, if the warehouse management system is active, this value is merely for information.
    
    Returns:
    
    Identifies the storage bin within a storage location where the material is stored.
  - 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.
  - setActualDeliveredQtyInBaseUnit
```
public void setActualDeliveredQtyInBaseUnit(@Nullable
                                            BigDecimal actualDeliveredQtyInBaseUnit)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Parameters:
    
    actualDeliveredQtyInBaseUnit -
  - setDeliveryVersion
```
public void setDeliveryVersion(@Nullable
                               String deliveryVersion)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    deliveryVersion -
  - setActualDeliveryQuantity
```
public void setActualDeliveryQuantity(@Nullable
                                      BigDecimal actualDeliveryQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    The delivery quantity may be proposed from a sales order item. You can change the quantity in the delivery, subject to any limitations that apply to over- and underdeliveries. If the delivery does not refer to a sales order, you can enter a delivery quantity manually.
    
    Parameters:
    
    actualDeliveryQuantity -
  - setAdditionalCustomerGroup1
```
public void setAdditionalCustomerGroup1(@Nullable
                                        String additionalCustomerGroup1)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup1 -
  - setAdditionalCustomerGroup2
```
public void setAdditionalCustomerGroup2(@Nullable
                                        String additionalCustomerGroup2)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup2 -
  - setAdditionalCustomerGroup3
```
public void setAdditionalCustomerGroup3(@Nullable
                                        String additionalCustomerGroup3)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup3 -
  - setAdditionalCustomerGroup4
```
public void setAdditionalCustomerGroup4(@Nullable
                                        String additionalCustomerGroup4)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup4 -
  - setAdditionalCustomerGroup5
```
public void setAdditionalCustomerGroup5(@Nullable
                                        String additionalCustomerGroup5)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup5 -
  - setAdditionalMaterialGroup1
```
public void setAdditionalMaterialGroup1(@Nullable
                                        String additionalMaterialGroup1)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup1 -
  - setAdditionalMaterialGroup2
```
public void setAdditionalMaterialGroup2(@Nullable
                                        String additionalMaterialGroup2)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup2 -
  - setAdditionalMaterialGroup3
```
public void setAdditionalMaterialGroup3(@Nullable
                                        String additionalMaterialGroup3)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup3 -
  - setAdditionalMaterialGroup4
```
public void setAdditionalMaterialGroup4(@Nullable
                                        String additionalMaterialGroup4)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup4 -
  - setAdditionalMaterialGroup5
```
public void setAdditionalMaterialGroup5(@Nullable
                                        String additionalMaterialGroup5)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup5 -
  - setAlternateProductNumber
```
public void setAlternateProductNumber(@Nullable
                                      String alternateProductNumber)
```
    Constraints: Not nullable, Maximum length: 40
    It does not need to be created as its own material master in the ERP system. Within Logistics Execution in the ERP system, it is stored without validation. The translation to the internal material number needs to be provided in the external system or within an implementation of a Business Add-In (BAdI).
    
    Parameters:
    
    alternateProductNumber -
  - setBaseUnit
```
public void setBaseUnit(@Nullable
                        String baseUnit)
```
    Constraints: Not nullable, Maximum length: 3
    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 Management In Inventory Management, the base unit of measure is the same as the stockkeeping unit. Services Services have units of measure of their own, including the following: Service unit Unit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level. Blanket Unit 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 -
  - setBatch
```
public void setBatch(@Nullable
                     String batch)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    batch -
  - setBatchBySupplier
```
public void setBatchBySupplier(@Nullable
                               String batchBySupplier)
```
    Constraints: Not nullable, Maximum length: 15
    
    Parameters:
    
    batchBySupplier -
  - setBatchClassification
```
public void setBatchClassification(@Nullable
                                   String batchClassification)
```
    Constraints: Not nullable, Maximum length: 18
    You are required by the authorities (for example, the Food and Drug Authority in the USA) to keep a record of the selection values used to locate a particular batch so that you are always able to compare these values with the original specifications. This internal number enables you to meet this requirement.
    
    Parameters:
    
    batchClassification -
  - setBOMExplosion
```
public void setBOMExplosion(@Nullable
                            String bOMExplosion)
```
    Constraints: Not nullable, Maximum length: 8
    
    Parameters:
    
    bOMExplosion -
  - setBusinessArea
```
public void setBusinessArea(@Nullable
                            String businessArea)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    businessArea -
  - setConsumptionPosting
```
public void setConsumptionPosting(@Nullable
                                  String consumptionPosting)
```
    Constraints: Not nullable, Maximum length: 1
    The indicator is used in the case of goods receipts for purchase orders and is derived from the account assignment category of the purchase order.
    
    Parameters:
    
    consumptionPosting -
  - setControllingArea
```
public void setControllingArea(@Nullable
                               String controllingArea)
```
    Constraints: Not nullable, Maximum length: 4
    The controlling area is the highest organizational unit in Controlling. Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
    
    Parameters:
    
    controllingArea -
  - setCostCenter
```
public void setCostCenter(@Nullable
                          String costCenter)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    costCenter -
  - setCreatedByUser
```
public void setCreatedByUser(@Nullable
                             String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    
    Parameters:
    
    createdByUser -
  - setCreationDate
```
public void setCreationDate(@Nullable
                            Calendar creationDate)
```
    Constraints: Not nullable, Precision: 7
    
    Parameters:
    
    creationDate -
  - setCreationTime
```
public void setCreationTime(@Nullable
                            Calendar creationTime)
```
    Constraints: Not nullable, Precision: 0
    
    Parameters:
    
    creationTime -
  - setCustEngineeringChgStatus
```
public void setCustEngineeringChgStatus(@Nullable
                                        String custEngineeringChgStatus)
```
    Constraints: Not nullable, Maximum length: 17
    The customer sends this number in with a material number to request an engineering change to take effect as of a certain delivery date or cumulative quantity.
    
    Parameters:
    
    custEngineeringChgStatus -
  - setDeliveryDocument
```
public void setDeliveryDocument(@Nullable
                                String deliveryDocument)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    deliveryDocument -
  - setDeliveryDocumentItem
```
public void setDeliveryDocumentItem(@Nullable
                                    String deliveryDocumentItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    deliveryDocumentItem -
  - setDeliveryDocumentItemCategory
```
public void setDeliveryDocumentItemCategory(@Nullable
                                            String deliveryDocumentItemCategory)
```
    Constraints: Not nullable, Maximum length: 4
    The delivery item category determines how the system processes an item. If, for example, you identify an item as a return item, you tell the system, in this case, that the item is not relevant for picking. The system proposes a delivery item category.
    
    Parameters:
    
    deliveryDocumentItemCategory -
  - setDeliveryDocumentItemText
```
public void setDeliveryDocumentItemText(@Nullable
                                        String deliveryDocumentItemText)
```
    Constraints: Not nullable, Maximum length: 40
    Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations. The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
    
    Parameters:
    
    deliveryDocumentItemText -
  - setDeliveryGroup
```
public void setDeliveryGroup(@Nullable
                             String deliveryGroup)
```
    Constraints: Not nullable, Maximum length: 3
    The system uses delivery groups to check the availability of items that should be delivered together. The delivery date of the latest schedule line in the delivery group is taken as the general date for the whole group. During sales order processing, you can enter a number (up to three digits) that identifies a delivery group. The number is freely definable. If necessary, the system adjusts requirements that have already been created and changes the material availability dates for individual items to the delivery date that it has determined for the group. If a typewriter is usually delivered with a case, you can define the two items as a delivery group. If an item has more than one schedule line with a confirmed quantity, then the system deletes all undelivered schedule lines up to the last one. The system automatically carries over the quantities from the deleted schedule lines into the last one. If necessary, the system changes the delivery date of the last schedule line to that of the delivery group.
    
    Parameters:
    
    deliveryGroup -
  - setDeliveryQuantityUnit
```
public void setDeliveryQuantityUnit(@Nullable
                                    String deliveryQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    deliveryQuantityUnit -
  - setDeliveryRelatedBillingStatus
```
public void setDeliveryRelatedBillingStatus(@Nullable
                                            String deliveryRelatedBillingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you if the item is not yet billed, is partly billed, is completely billed, or is not relevant for billing.
    
    Parameters:
    
    deliveryRelatedBillingStatus -
  - setDeliveryToBaseQuantityDnmntr
```
public void setDeliveryToBaseQuantityDnmntr(@Nullable
                                            BigDecimal deliveryToBaseQuantityDnmntr)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Parameters:
    
    deliveryToBaseQuantityDnmntr -
  - setDeliveryToBaseQuantityNmrtr
```
public void setDeliveryToBaseQuantityNmrtr(@Nullable
                                           BigDecimal deliveryToBaseQuantityNmrtr)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Parameters:
    
    deliveryToBaseQuantityNmrtr -
  - setDepartmentClassificationByCust
```
public void setDepartmentClassificationByCust(@Nullable
                                              String departmentClassificationByCust)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    departmentClassificationByCust -
  - setDistributionChannel
```
public void setDistributionChannel(@Nullable
                                   String distributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel. You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel. For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Parameters:
    
    distributionChannel -
  - setDivision
```
public void setDivision(@Nullable
                        String division)
```
    Constraints: Not nullable, Maximum length: 2
    A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
    
    Parameters:
    
    division -
  - setFixedShipgProcgDurationInDays
```
public void setFixedShipgProcgDurationInDays(@Nullable
                                             BigDecimal fixedShipgProcgDurationInDays)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    
    Parameters:
    
    fixedShipgProcgDurationInDays -
  - setGLAccount
```
public void setGLAccount(@Nullable
                         String gLAccount)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    gLAccount -
  - setGoodsMovementReasonCode
```
public void setGoodsMovementReasonCode(@Nullable
                                       String goodsMovementReasonCode)
```
    Constraints: Not nullable, Maximum length: 4
    Please do not change the entry in this field. Any changes made could lead to program errors or terminations.
    
    Parameters:
    
    goodsMovementReasonCode -
  - setGoodsMovementStatus
```
public void setGoodsMovementStatus(@Nullable
                                   String goodsMovementStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status provides the following information: For an outbound delivery, the status informs you whether the item has already left the warehouse or company premises, or still being processed. For an inbound delivery, the system shows you whether the goods have already been received, or are waiting to be received. The status also informs you whether or not an item is relevant for delivery. A text item is not relevant, for example.
    
    Parameters:
    
    goodsMovementStatus -
  - setGoodsMovementType
```
public void setGoodsMovementType(@Nullable
                                 String goodsMovementType)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    goodsMovementType -
  - setHigherLevelItem
```
public void setHigherLevelItem(@Nullable
                               String higherLevelItem)
```
    Constraints: Not nullable, Maximum length: 6
    Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
    
    Parameters:
    
    higherLevelItem -
  - setInspectionLot
```
public void setInspectionLot(@Nullable
                             String inspectionLot)
```
    Constraints: Not nullable, Maximum length: 12
    The inspection lot number is assigned by the system.
    
    Parameters:
    
    inspectionLot -
  - setInspectionPartialLot
```
public void setInspectionPartialLot(@Nullable
                                    String inspectionPartialLot)
```
    Constraints: Not nullable, Maximum length: 6
    You can process partial lots by: Inspecting during production using inspection points Running a batch split for the delivery note
    
    Parameters:
    
    inspectionPartialLot -
  - setIntercompanyBillingStatus
```
public void setIntercompanyBillingStatus(@Nullable
                                         String intercompanyBillingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    intercompanyBillingStatus -
  - setInternationalArticleNumber
```
public void setInternationalArticleNumber(@Nullable
                                          String internationalArticleNumber)
```
    Constraints: Not nullable, Maximum length: 18
    
    Parameters:
    
    internationalArticleNumber -
  - setInventorySpecialStockType
```
public void setInventorySpecialStockType(@Nullable
                                         String inventorySpecialStockType)
```
    Constraints: Not nullable, Maximum length: 1
    If you need to separately manage certain stock (for example, consignment stock) of a material, the stock type in question is defined using this indicator.
    
    Parameters:
    
    inventorySpecialStockType -
  - setInventoryValuationType
```
public void setInventoryValuationType(@Nullable
                                      String inventoryValuationType)
```
    Constraints: Not nullable, Maximum length: 10
    The valuation types allowed for a material are determined by the valuation category. If a material is valuated according to its origin (valuation category H), you can define the possible countries of origin as valuation types.
    
    Parameters:
    
    inventoryValuationType -
  - setIsCompletelyDelivered
```
public void setIsCompletelyDelivered(@Nullable
                                     Boolean isCompletelyDelivered)
```
    Constraints: none
    
    Parameters:
    
    isCompletelyDelivered -
  - setIsNotGoodsMovementsRelevant
```
public void setIsNotGoodsMovementsRelevant(@Nullable
                                           String isNotGoodsMovementsRelevant)
```
    Constraints: Not nullable, Maximum length: 1
    When this indicator is set, goods movement is not posted for this item - regardless of the movement type assigned to it.
    
    Parameters:
    
    isNotGoodsMovementsRelevant -
  - setIsSeparateValuation
```
public void setIsSeparateValuation(@Nullable
                                   Boolean isSeparateValuation)
```
    Constraints: none
    
    Parameters:
    
    isSeparateValuation -
  - setIssgOrRcvgBatch
```
public void setIssgOrRcvgBatch(@Nullable
                               String issgOrRcvgBatch)
```
    Constraints: Not nullable, Maximum length: 10
    The "receiving batch" is the number of the batch under which the quantity to be transferred is now to be recorded. The "issuing batch" (in the case of a reversal) is the number of the batch from which a quantity is to be deducted.
    
    Parameters:
    
    issgOrRcvgBatch -
  - setIssgOrRcvgMaterial
```
public void setIssgOrRcvgMaterial(@Nullable
                                  String issgOrRcvgMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    The "receiving material" is the material number under which the quantity to be transferred is now to be recorded. The "issuing material" (in the case of a reversal) is the material from whose stock a certain quantity is to be deducted. Note The value of the transfer posting is determined not by the material entered here but by the material specified in the Material field. Note the following with regard to the receiving/issuing material: The material must exist The material must be managed in the same stockkeeping unit as the issuing material
    
    Parameters:
    
    issgOrRcvgMaterial -
  - setIssgOrRcvgSpclStockInd
```
public void setIssgOrRcvgSpclStockInd(@Nullable
                                      String issgOrRcvgSpclStockInd)
```
    Constraints: Not nullable, Maximum length: 1
    This indicator is used, for example, in the case of the physical transfer of a consignment material and when consignment material is transferred from the supplier's stock to the company's own stock.
    
    Parameters:
    
    issgOrRcvgSpclStockInd -
  - setIssgOrRcvgStockCategory
```
public void setIssgOrRcvgStockCategory(@Nullable
                                       String issgOrRcvgStockCategory)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    issgOrRcvgStockCategory -
  - setIssgOrRcvgValuationType
```
public void setIssgOrRcvgValuationType(@Nullable
                                       String issgOrRcvgValuationType)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    issgOrRcvgValuationType -
  - setIssuingOrReceivingPlant
```
public void setIssuingOrReceivingPlant(@Nullable
                                       String issuingOrReceivingPlant)
```
    Constraints: Not nullable, Maximum length: 4
    The receiving plant is the plant or internal organizational unit that is to receive the goods. The issuing plant is the plant that issues the goods. Note The value of the transfer posting is determined not by the plant entered here but by the plant specified in the Plant field.
    
    Parameters:
    
    issuingOrReceivingPlant -
  - setIssuingOrReceivingStorageLoc
```
public void setIssuingOrReceivingStorageLoc(@Nullable
                                            String issuingOrReceivingStorageLoc)
```
    Constraints: Not nullable, Maximum length: 4
    The receiving storage location is the storage location that is to receive the goods. The issuing storage location is the storage location that issues the goods.
    
    Parameters:
    
    issuingOrReceivingStorageLoc -
  - setItemBillingBlockReason
```
public void setItemBillingBlockReason(@Nullable
                                      String itemBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    The system can automatically propose a billing block for sales documents that must be checked before billing (for example, returns, credit and debit memo requests). If the system proposes a block, you can change the block manually for each item. If the system does not propose a block, enter one of values predefined for your system. If the item has more than one schedule line, the block applies to each line. You can change the block for individual schedule lines.
    
    Parameters:
    
    itemBillingBlockReason -
  - setItemBillingIncompletionStatus
```
public void setItemBillingIncompletionStatus(@Nullable
                                             String itemBillingIncompletionStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you to what extent the information necessary for billing the item is complete. A sales order item, for example, is incomplete for billing if prices are missing. You cannot bill the item until you provide the missing information.
    
    Parameters:
    
    itemBillingIncompletionStatus -
  - setItemDeliveryIncompletionStatus
```
public void setItemDeliveryIncompletionStatus(@Nullable
                                              String itemDeliveryIncompletionStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you if delivery-related item information is complete. You must enter this information, if you want to process the item further. A sales order item is incomplete for delivery processing if, for example, you do not enter a shipping point. You cannot deliver the item until you provide this information.
    
    Parameters:
    
    itemDeliveryIncompletionStatus -
  - setItemGdsMvtIncompletionSts
```
public void setItemGdsMvtIncompletionSts(@Nullable
                                         String itemGdsMvtIncompletionSts)
```
    Constraints: Not nullable, Maximum length: 1
    The status provides information on how far the data required for billing the item is complete. A sales document item is incomplete for billing, for example, if price specifications are missing. You can only invoice the item if you have completed the missing data.
    
    Parameters:
    
    itemGdsMvtIncompletionSts -
  - setItemGeneralIncompletionStatus
```
public void setItemGeneralIncompletionStatus(@Nullable
                                             String itemGeneralIncompletionStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status line tells you if all item information, necessary for further processing this item, is complete.
    
    Parameters:
    
    itemGeneralIncompletionStatus -
  - setItemGrossWeight
```
public void setItemGrossWeight(@Nullable
                               BigDecimal itemGrossWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order. If there is no related sales order, the system uses the gross weight from the material master record. You can change the gross weight manually in the delivery document.
    
    Parameters:
    
    itemGrossWeight -
  - setItemIsBillingRelevant
```
public void setItemIsBillingRelevant(@Nullable
                                     String itemIsBillingRelevant)
```
    Constraints: Not nullable, Maximum length: 1
    A: Relevant for delivery-related billing Billing is based on the outbound delivery. The billing status is only updated in the outbound delivery. B: Relevant for order-related billing Billing is based on the sales document. The billing status depends on the requested delivery quantity. Item categories REN (returns) and BVN (cash sales items) are set up with billing relevance B in the standard system. C: Relevant for order-related billing Billing is based on the sales document. The billing status depends on the target quantity. Item categories G2N (credit memo) and L2N (debit memo) are set up with billing relevance C in the standard system. D: Relevant for pro forma To create a pro forma invoice, the billing relevance indicator must not be blank. Indicator D is also used as follows for cross-company-code business processing: If there are free-of-charge outbound deliveries, the company code that is responsible for the delivery should be granted an internal settlement. You can use indicator D to enable this for free-of-charge deliveries. F: Relevant for order-related billing - Status based on invoice receipt quantity Relevant for order-related billing based on the invoice receipt quantity (third-party business). The system does not transfer the order to the billing due list until the vendor invoice has been received and processed in the purchasing department. After each invoice receipt, a customer invoice is created for the quantity that appears on the vendor invoice. The order has status "Billed" until the next vendor invoice is received. Item category TAS (third-party business) is set up with billing relevance F in the standard system. This process can also be related to the goods receipt quantity. You can make the control setting as to whether the invoice receipt quantity or the goods receipt quantity is relevant for billing in the copy control for billing on the item level in the billing quantity field. G: Relevant for order-related billing of the delivery quantity The order is relevant for billing; more specifically, the cumulated quantity that has already been delivered is relevant. You can use this category to bill for multiple partial deliveries in one process. H: Relevant for delivery-related billing – no zero quantities You can use this category to prevent items with a value of zero from being included in billing. I: Relevant for order-related billing – billing plan Billing takes place using the billing plan and its status. The status of the order item can be understood as the overall status of the billing plan billing statuses. Item categories WVN (maintenance contract item), MVN (lease item), and TAO (milestone billing) are set up with billing relevance I in the standard system. J: Relevant for deliveries across EU countries The delivery is only relevant for billing if: The country of departure (country where plant is located) and destination country (country where ship-to party is located) are different EU countries. Item categories KBN (consignment fill-up), KAN (consignment pick-up), and NLN (standard stock transfer item) are set up with billing relevance J in the standard system. K: Relevant for delivery-related partial quantity billing You use this indicator if you want to select both items and partial quantities for billing.
    
    Parameters:
    
    itemIsBillingRelevant -
  - setItemNetWeight
```
public void setItemNetWeight(@Nullable
                             BigDecimal itemNetWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record. You can change the net weight manually in the delivery document.
    
    Parameters:
    
    itemNetWeight -
  - setItemPackingIncompletionStatus
```
public void setItemPackingIncompletionStatus(@Nullable
                                             String itemPackingIncompletionStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status indicates the degree to which the data required for billing the item are complete. For example, a sales order item is incomplete for billing if prices are missing. You cannot bill the item unless you have entered the missing data.
    
    Parameters:
    
    itemPackingIncompletionStatus -
  - setItemPickingIncompletionStatus
```
public void setItemPickingIncompletionStatus(@Nullable
                                             String itemPickingIncompletionStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status indicates whether the delivery-related item data is complete. You must enter these data if you want to further process the item. For example, a sales order item is incomplete for delivery processing if you do not specify a shipping point. You cannot deliver the item unless you have entered these data.
    
    Parameters:
    
    itemPickingIncompletionStatus -
  - setItemVolume
```
public void setItemVolume(@Nullable
                          BigDecimal itemVolume)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order. If there is no related sales order, the system uses the volume from the material master record. You can change the volume manually in the delivery document.
    
    Parameters:
    
    itemVolume -
  - setItemVolumeUnit
```
public void setItemVolumeUnit(@Nullable
                              String itemVolumeUnit)
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a volume, you have to enter the corresponding volume unit here.
    
    Parameters:
    
    itemVolumeUnit -
  - setItemWeightUnit
```
public void setItemWeightUnit(@Nullable
                              String itemWeightUnit)
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a weight, you must enter the corresponding unit of weight here.
    
    Parameters:
    
    itemWeightUnit -
  - setLastChangeDate
```
public void setLastChangeDate(@Nullable
                              Calendar lastChangeDate)
```
    Constraints: Not nullable, Precision: 7
    
    Parameters:
    
    lastChangeDate -
  - setLoadingGroup
```
public void setLoadingGroup(@Nullable
                            String loadingGroup)
```
    Constraints: Not nullable, Maximum length: 4
    The system uses the loading group as well as the Shipping conditions and Delivering plant to automatically determine the shipping point for the item. Different loading groups could consist, for example, of materials that require the same: Equipment during loading (for example, a fork-lift truck) Amount of time for loading Loading point (for example, loading bay #6)
    
    Parameters:
    
    loadingGroup -
  - setManufactureDate
```
public void setManufactureDate(@Nullable
                               Calendar manufactureDate)
```
    Constraints: Not nullable, Precision: 7
    
    Parameters:
    
    manufactureDate -
  - setMaterial
```
public void setMaterial(@Nullable
                        String material)
```
    Constraints: Not nullable, Maximum length: 40
    
    Parameters:
    
    material -
  - setMaterialByCustomer
```
public void setMaterialByCustomer(@Nullable
                                  String materialByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    The customer's own identifier for a material can be stored in a customer-material info record and can be used to enter data during sales order processing.
    
    Parameters:
    
    materialByCustomer -
  - setMaterialFreightGroup
```
public void setMaterialFreightGroup(@Nullable
                                    String materialFreightGroup)
```
    Constraints: Not nullable, Maximum length: 8
    Freight codes and classes in a freight code set are determined by the material freight group. The freight code set is used to determine freight costs and for communication with service agents. Maintain the corresponding group for the material.
    
    Parameters:
    
    materialFreightGroup -
  - setMaterialGroup
```
public void setMaterialGroup(@Nullable
                             String materialGroup)
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Parameters:
    
    materialGroup -
  - setMaterialIsBatchManaged
```
public void setMaterialIsBatchManaged(@Nullable
                                      Boolean materialIsBatchManaged)
```
    Constraints: none
    This indicator can be set in the material master record manually or, if batches are valuated individually, it is set automatically for the plants concerned, in which case it cannot be changed. The indicator cannot be changed if stocks exist in either the current period or in the previous period. The reason for checking the previous period is because stocks can be posted to this period when goods movements are entered.
    
    Parameters:
    
    materialIsBatchManaged -
  - setMaterialIsIntBatchManaged
```
public void setMaterialIsIntBatchManaged(@Nullable
                                         Boolean materialIsIntBatchManaged)
```
    Constraints: none
    
    Parameters:
    
    materialIsIntBatchManaged -
  - setNumberOfSerialNumbers
```
public void setNumberOfSerialNumbers(@Nullable
                                     Integer numberOfSerialNumbers)
```
    Constraints: none
    
    Parameters:
    
    numberOfSerialNumbers -
  - setOrderID
```
public void setOrderID(@Nullable
                       String orderID)
```
    Constraints: Not nullable, Maximum length: 12
    
    Parameters:
    
    orderID -
  - setOrderItem
```
public void setOrderItem(@Nullable
                         String orderItem)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    orderItem -
  - setOriginalDeliveryQuantity
```
public void setOriginalDeliveryQuantity(@Nullable
                                        BigDecimal originalDeliveryQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    When creating the inbound delivery, the notified quantity is transferred as the original quantity. Should you want to change the notified quantity at a later point in time, because the actual quantity delivered is different, you can decide whether or not you want this change to be displayed in the Original Quantity field. Should you want to change the delivery quantity in an inbound delivery that already exists in the system, then you will receive a dialog box with the following choices: If you choose Yes, the delivery quantity will be changed and the originally/previously notified quantity will continue to be displayed in the Original Quantity field. This will then document in the system that the vendor actually delivered a different quantity than that originally notified. If you choose No, the delivery quantity will be changed and the previously notified quantity shown in the Original Quantity field will be overwritten with the new delivery quantity. In this case, the delivery quantity that was changed by the vendor will not be documented in the system. In the confirmation overview of the scheduling agreement, the fields Quantity and Original Quantity show you whether or not the vendor actually delivered the quantity he originally notified you of. In a shipping notification, your vendor notifies you of the impending delivery of 450 pc Steel_01. When the inbound delivery is created, the 450 pc are recorded as delivery quantity and original quantity. However, you vendor actually delivers 500 pc. You therefore change the delivery quantity in the inbound delivery. A dialog box then appears, offering you the following options: Yes - Document originally notified quantity Result The delivery quantity is changed to 500 pc and the quantity variance is documented, i.e. the originally notified quantity of 450 pc continues to be shown in the Original Quantity field. No - Do not document originally notified quantity Result The delivery quantity is changed to 500 pc and the quantity variance is not documented, i.e. the originally notified quantity of 450 pc shown in the Original Quantity field is replaced by the quantity 500 pc actually delivered. Note If you use this function, then the GR assignment should be set in Customizing for Purchasing, in the confirmation control for the used confirmation categories.
    
    Parameters:
    
    originalDeliveryQuantity -
  - setOriginallyRequestedMaterial
```
public void setOriginallyRequestedMaterial(@Nullable
                                           String originallyRequestedMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
    
    Parameters:
    
    originallyRequestedMaterial -
  - setOverdelivTolrtdLmtRatioInPct
```
public void setOverdelivTolrtdLmtRatioInPct(@Nullable
                                            BigDecimal overdelivTolrtdLmtRatioInPct)
```
    Constraints: Not nullable, Precision: 3, Scale: 1
    If you have set the indicator in the Partial delivery/Item field to 'D' (partial delivery allowed), this takes priority. It makes no sense to define a tolerance limit for overdelivery in such case.
    
    Parameters:
    
    overdelivTolrtdLmtRatioInPct -
  - setPackingStatus
```
public void setPackingStatus(@Nullable
                             String packingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    packingStatus -
  - setPartialDeliveryIsAllowed
```
public void setPartialDeliveryIsAllowed(@Nullable
                                        String partialDeliveryIsAllowed)
```
    Constraints: Not nullable, Maximum length: 1
    You use this field to control partial deliveries at the item level. If the customer allows partial delivery, you can choose from different partial delivery options. For example, you can specify whether the customer allows you to make one delivery attempt only on the requested delivery date or whether unlimited delivery attempts are possible. When partial delivery indicator 'D' is set, the order can never have status 'fully delivered'. You must complete each item by entering a reason for rejection. This could be applied to scheduling agreements, for example. You can enter a value in this field only if the customer allows partial deliveries for the entire sales document.
    
    Parameters:
    
    partialDeliveryIsAllowed -
  - setPaymentGuaranteeForm
```
public void setPaymentGuaranteeForm(@Nullable
                                    String paymentGuaranteeForm)
```
    Constraints: Not nullable, Maximum length: 2
    The form of payment guarantee specifies how a sales document item is guaranteed. Payment cards Letter of credit Standby letter of credit Bank guarantee
    
    Parameters:
    
    paymentGuaranteeForm -
  - setPickingConfirmationStatus
```
public void setPickingConfirmationStatus(@Nullable
                                         String pickingConfirmationStatus)
```
    Constraints: Not nullable, Maximum length: 1
    When you create a delivery with an item subject to pick/putaway confirmation, the item is assigned the status A (Subject to confirmation but not yet confirmed). Once you confirm the pick/putaway, the system assigns either status B (Partially confirmed) or C (Fully confirmed). Goods movement cannot be posted for items subject to pick/putaway confirmation until the pick/putaway quantities for the items have been fully confirmed.
    
    Parameters:
    
    pickingConfirmationStatus -
  - setPickingControl
```
public void setPickingControl(@Nullable
                              String pickingControl)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    pickingControl -
  - setPickingStatus
```
public void setPickingStatus(@Nullable
                             String pickingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status message tells you whether the item is relevant for delivery. If the item is relevant for delivery, the status indicates whether picking/putaway has: Begun Been partially carried out Been completed Picking/putaway is not relevant for some items, for example, text items or service items.
    
    Parameters:
    
    pickingStatus -
  - setPlant
```
public void setPlant(@Nullable
                     String plant)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    plant -
  - setPrimaryPostingSwitch
```
public void setPrimaryPostingSwitch(@Nullable
                                    String primaryPostingSwitch)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    primaryPostingSwitch -
  - setProductAvailabilityDate
```
public void setProductAvailabilityDate(@Nullable
                                       Calendar productAvailabilityDate)
```
    Constraints: Not nullable, Precision: 7
    The system uses the material availability date to generate automatic production and purchasing requirements. The system calculates the material availability date by working backwards from the customer's requested delivery date, taking into account how much time is needed for delivery-related procedures, such as picking, packing, loading, and transportation. The system proposes the material availability date. You can change the date manually in the sales document. The picking date is the same as the material availability date.
    
    Parameters:
    
    productAvailabilityDate -
  - setProductAvailabilityTime
```
public void setProductAvailabilityTime(@Nullable
                                       Calendar productAvailabilityTime)
```
    Constraints: Not nullable, Precision: 0
    
    Parameters:
    
    productAvailabilityTime -
  - setProductConfiguration
```
public void setProductConfiguration(@Nullable
                                    String productConfiguration)
```
    Constraints: Not nullable, Maximum length: 18
    This number clearly identifies one particular configuration of a standard product.
    
    Parameters:
    
    productConfiguration -
  - setProductHierarchyNode
```
public void setProductHierarchyNode(@Nullable
                                    String productHierarchyNode)
```
    Constraints: Not nullable, Maximum length: 18
    In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters. Level Number of characters allowed 1 5 2 5 3 8 You define a product hierarchy with the following levels: Level Example Description 1 00005 Electrical goods 2 00003 Wet appliances 3 00000001 Washing machine In this case, a washing machine belongs to the product hierarchy 000050000300000001.
    
    Parameters:
    
    productHierarchyNode -
  - setProfitabilitySegment
```
public void setProfitabilitySegment(@Nullable
                                    String profitabilitySegment)
```
    Constraints: Not nullable, Maximum length: 10
    Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
    
    Parameters:
    
    profitabilitySegment -
  - setProfitCenter
```
public void setProfitCenter(@Nullable
                            String profitCenter)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    profitCenter -
  - setProofOfDeliveryRelevanceCode
```
public void setProofOfDeliveryRelevanceCode(@Nullable
                                            String proofOfDeliveryRelevanceCode)
```
    Constraints: Not nullable, Maximum length: 1
    The indicator can have the following settings: ' ': not POD relevant 'A' : always POD relevant 'B' : only POD relevant when there are quantity differences The indicator is copied from the purchasing or sales document into the delivery, if control of POD relevance in the delivery item category is set to "Copy POD relevance from preceding document".
    
    Parameters:
    
    proofOfDeliveryRelevanceCode -
  - setProofOfDeliveryStatus
```
public void setProofOfDeliveryStatus(@Nullable
                                     String proofOfDeliveryStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The status message informs you whether the ship-to party reported a proof of delivery for this item. This status may have the following values for a delivery item: ' ' Not relevant for the POD process 'A' Relevant for the POD process 'B' Differences were reported 'C' Quantities were verified and confirmed
    
    Parameters:
    
    proofOfDeliveryStatus -
  - setQuantityIsFixed
```
public void setQuantityIsFixed(@Nullable
                               Boolean quantityIsFixed)
```
    Constraints: none
    Set this indicator if the quantity in a relational system does not change. If an item of a BOM is marked as being fixed and the quantity of the finished product to be manufactured is changed, the quantity of this item does not change. If a "materials to be provided" item is not marked as being fixed, and the quantity of the subcontracted item is changed, the quantity of the material to be provided to the subcontractor changes proportionately.
    
    Parameters:
    
    quantityIsFixed -
  - setReceivingPoint
```
public void setReceivingPoint(@Nullable
                              String receivingPoint)
```
    Constraints: Not nullable, Maximum length: 25
    Several receiving points can be defined for each plant. The receiving points can then be assigned to individual departments. The receiving point can be printed on delivery documents (SD function).
    
    Parameters:
    
    receivingPoint -
  - setReferenceDocumentLogicalSystem
```
public void setReferenceDocumentLogicalSystem(@Nullable
                                              String referenceDocumentLogicalSystem)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    referenceDocumentLogicalSystem -
  - setReferenceSDDocument
```
public void setReferenceSDDocument(@Nullable
                                   String referenceSDDocument)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    referenceSDDocument -
  - setReferenceSDDocumentCategory
```
public void setReferenceSDDocumentCategory(@Nullable
                                           String referenceSDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    referenceSDDocumentCategory -
  - setReferenceSDDocumentItem
```
public void setReferenceSDDocumentItem(@Nullable
                                       String referenceSDDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    referenceSDDocumentItem -
  - setRetailPromotion
```
public void setRetailPromotion(@Nullable
                               String retailPromotion)
```
    Constraints: Not nullable, Maximum length: 10
    For each item of a purchasing document, you can specify the promotion to which the item belongs. Depending on your system settings, special prices and conditions that are maintained in the IS-R system (Retail) for this promotion are applied when a promotion number is entered. This field also allows you to create purchasing documents on a selective basis for a certain promotion. For example, you can create a purchase order containing only those items that are to be procured for one promotion.
    
    Parameters:
    
    retailPromotion -
  - setSalesDocumentItemType
```
public void setSalesDocumentItemType(@Nullable
                                     String salesDocumentItemType)
```
    Constraints: Not nullable, Maximum length: 1
    The system processes items that refer to a specific material differently than items that do not refer to a material. For example, text items do not require processing for pricing, taxes, and weight calculations.
    
    Parameters:
    
    salesDocumentItemType -
  - setSalesGroup
```
public void setSalesGroup(@Nullable
                          String salesGroup)
```
    Constraints: Not nullable, Maximum length: 3
    By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria. If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market. You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
    
    Parameters:
    
    salesGroup -
  - setSalesOffice
```
public void setSalesOffice(@Nullable
                           String salesOffice)
```
    Constraints: Not nullable, Maximum length: 4
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Parameters:
    
    salesOffice -
  - setSDDocumentCategory
```
public void setSDDocumentCategory(@Nullable
                                  String sDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
    
    Parameters:
    
    sDDocumentCategory -
  - setSDProcessStatus
```
public void setSDProcessStatus(@Nullable
                               String sDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
    
    Parameters:
    
    sDProcessStatus -
  - setShelfLifeExpirationDate
```
public void setShelfLifeExpirationDate(@Nullable
                                       Calendar shelfLifeExpirationDate)
```
    Constraints: Not nullable, Precision: 7
    You enter it yourself. You enter a date of production, and the system calculates the shelf life expiration date from the date of production plus the shelf life in days (from the material master record). Note This date can still be changed upon receipt of the usage decision for an inspection lot.
    
    Parameters:
    
    shelfLifeExpirationDate -
  - setStatisticsDate
```
public void setStatisticsDate(@Nullable
                              Calendar statisticsDate)
```
    Constraints: Not nullable, Precision: 7
    Write a user-exit if you require the system to copy the statistics date to the billing document. The field definition may change depending on the user-exit.
    
    Parameters:
    
    statisticsDate -
  - setStockType
```
public void setStockType(@Nullable
                         String stockType)
```
    Constraints: Not nullable, Maximum length: 1
    Possible stocks are: unrestricted-use stock (blank, F) stock in quality inspection (X, 2) blocked stock (S, 3) Select the corresponding indicator for the stock type required. It is due to earlier release levels that there are two valid values for each stock type. Each value has the same effect.
    
    Parameters:
    
    stockType -
  - setStorageBin
```
public void setStorageBin(@Nullable
                          String storageBin)
```
    Constraints: Not nullable, Maximum length: 10
    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 -
  - setStorageLocation
```
public void setStorageLocation(@Nullable
                               String storageLocation)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    storageLocation -
  - setStorageType
```
public void setStorageType(@Nullable
                           String storageType)
```
    Constraints: Not nullable, Maximum length: 3
    A typical warehouse could have the following storage types: Goods receipt area Picking area High-rack storage area Bulk storage area Open storage area Goods issue area
    
    Parameters:
    
    storageType -
  - setSubsequentMovementType
```
public void setSubsequentMovementType(@Nullable
                                      String subsequentMovementType)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    subsequentMovementType -
  - setTransportationGroup
```
public void setTransportationGroup(@Nullable
                                   String transportationGroup)
```
    Constraints: Not nullable, Maximum length: 4
    Transportation groups are used for automatic route scheduling during sales order and delivery note processing. Suppose that you sell food products, some of which are perishable and require refrigeration. You create a transportation group that includes all the products that need refrigerated trucks for delivery.
    
    Parameters:
    
    transportationGroup -
  - setUnderdelivTolrtdLmtRatioInPct
```
public void setUnderdelivTolrtdLmtRatioInPct(@Nullable
                                             BigDecimal underdelivTolrtdLmtRatioInPct)
```
    Constraints: Not nullable, Precision: 3, Scale: 1
    
    Parameters:
    
    underdelivTolrtdLmtRatioInPct -
  - setUnlimitedOverdeliveryIsAllowed
```
public void setUnlimitedOverdeliveryIsAllowed(@Nullable
                                              Boolean unlimitedOverdeliveryIsAllowed)
```
    Constraints: none
    
    Parameters:
    
    unlimitedOverdeliveryIsAllowed -
  - setVarblShipgProcgDurationInDays
```
public void setVarblShipgProcgDurationInDays(@Nullable
                                             BigDecimal varblShipgProcgDurationInDays)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    The system uses the variable during capacity planning for deliveries. The variable is determined from shipping information stored in the material master record. The system calculates the variable using the following formula: Variable = (Confirmed quantity x Processing time) divided by the base quantity You specify in a material master record that the processing time for shipping the material is 1 hour (processing time) for every 100 pieces (the base quantity). During delivery processing, you ship a delivery item of 300 pieces (the confirmed quantity). In this example, the variable equals 3 hours.
    
    Parameters:
    
    varblShipgProcgDurationInDays -
  - setWarehouse
```
public void setWarehouse(@Nullable
                         String warehouse)
```
    Constraints: Not nullable, Maximum length: 3
    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 -
  - setWarehouseActivityStatus
```
public void setWarehouseActivityStatus(@Nullable
                                       String warehouseActivityStatus)
```
    Constraints: Not nullable, Maximum length: 1
    If your delivery processing includes the SAP Warehouse Management (WM) system, the system automatically indicates the WM status for each item in a delivery.
    
    Parameters:
    
    warehouseActivityStatus -
  - setWarehouseStagingArea
```
public void setWarehouseStagingArea(@Nullable
                                    String warehouseStagingArea)
```
    Constraints: Not nullable, Maximum length: 10
    Staging areas can be used for different purposes (at the same time, if necessary): o Goods issue o Goods receipt o Cross-docking processes o Direct distribution
    
    Parameters:
    
    warehouseStagingArea -
  - setWarehouseStockCategory
```
public void setWarehouseStockCategory(@Nullable
                                      String warehouseStockCategory)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    warehouseStockCategory -
  - setWarehouseStorageBin
```
public void setWarehouseStorageBin(@Nullable
                                   String warehouseStorageBin)
```
    Constraints: Not nullable, Maximum length: 10
    This storage bin is only significant if you do not use SAP warehouse management. It appears on goods receipt/issue slips. However, if the warehouse management system is active, this value is merely for information.
    
    Parameters:
    
    warehouseStorageBin -
  - setErpConfigContext
```
public void setErpConfigContext(@Nullable
                                ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Parameters:
    
    erpConfigContext -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<OutbDeliveryItem>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<OutbDeliveryItem>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<OutbDeliveryItem>

Class OutbDeliveryItem

Nested Class Summary

Field Summary

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

ACTUAL_DELIVERED_QTY_IN_BASE_UNIT

DELIVERY_VERSION

ACTUAL_DELIVERY_QUANTITY

ADDITIONAL_CUSTOMER_GROUP1

ADDITIONAL_CUSTOMER_GROUP2

ADDITIONAL_CUSTOMER_GROUP3

ADDITIONAL_CUSTOMER_GROUP4

ADDITIONAL_CUSTOMER_GROUP5

ADDITIONAL_MATERIAL_GROUP1

ADDITIONAL_MATERIAL_GROUP2

ADDITIONAL_MATERIAL_GROUP3

ADDITIONAL_MATERIAL_GROUP4

ADDITIONAL_MATERIAL_GROUP5

ALTERNATE_PRODUCT_NUMBER

BASE_UNIT

BATCH

BATCH_BY_SUPPLIER

BATCH_CLASSIFICATION

BOM_EXPLOSION

BUSINESS_AREA

CONSUMPTION_POSTING

CONTROLLING_AREA

COST_CENTER

CREATED_BY_USER

CREATION_DATE

CREATION_TIME

CUST_ENGINEERING_CHG_STATUS

DELIVERY_DOCUMENT

DELIVERY_DOCUMENT_ITEM

DELIVERY_DOCUMENT_ITEM_CATEGORY

DELIVERY_DOCUMENT_ITEM_TEXT

DELIVERY_GROUP

DELIVERY_QUANTITY_UNIT

DELIVERY_RELATED_BILLING_STATUS

DELIVERY_TO_BASE_QUANTITY_DNMNTR

DELIVERY_TO_BASE_QUANTITY_NMRTR

DEPARTMENT_CLASSIFICATION_BY_CUST

DISTRIBUTION_CHANNEL

DIVISION

FIXED_SHIPG_PROCG_DURATION_IN_DAYS

GL_ACCOUNT

GOODS_MOVEMENT_REASON_CODE

GOODS_MOVEMENT_STATUS

GOODS_MOVEMENT_TYPE

HIGHER_LEVEL_ITEM

INSPECTION_LOT

INSPECTION_PARTIAL_LOT

INTERCOMPANY_BILLING_STATUS

INTERNATIONAL_ARTICLE_NUMBER

INVENTORY_SPECIAL_STOCK_TYPE

INVENTORY_VALUATION_TYPE

IS_COMPLETELY_DELIVERED

IS_NOT_GOODS_MOVEMENTS_RELEVANT

IS_SEPARATE_VALUATION

ISSG_OR_RCVG_BATCH

ISSG_OR_RCVG_MATERIAL

ISSG_OR_RCVG_SPCL_STOCK_IND

ISSG_OR_RCVG_STOCK_CATEGORY

ISSG_OR_RCVG_VALUATION_TYPE

ISSUING_OR_RECEIVING_PLANT

ISSUING_OR_RECEIVING_STORAGE_LOC

ITEM_BILLING_BLOCK_REASON

ITEM_BILLING_INCOMPLETION_STATUS

ITEM_DELIVERY_INCOMPLETION_STATUS

ITEM_GDS_MVT_INCOMPLETION_STS

ITEM_GENERAL_INCOMPLETION_STATUS

ITEM_GROSS_WEIGHT

ITEM_IS_BILLING_RELEVANT

ITEM_NET_WEIGHT

ITEM_PACKING_INCOMPLETION_STATUS