public static class ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem extends Object
Constructor and Description |
---|
ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem() |
public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ACTUAL_DELIVERED_QTY_IN_BASE_UNIT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ActualDeliveredQtyInBaseUnit field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_VERSION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryVersion field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ACTUAL_DELIVERY_QUANTITY
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ActualDeliveryQuantity field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_CUSTOMER_GROUP1
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalCustomerGroup1 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_CUSTOMER_GROUP2
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalCustomerGroup2 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_CUSTOMER_GROUP3
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalCustomerGroup3 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_CUSTOMER_GROUP4
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalCustomerGroup4 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_CUSTOMER_GROUP5
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalCustomerGroup5 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_MATERIAL_GROUP1
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalMaterialGroup1 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_MATERIAL_GROUP2
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalMaterialGroup2 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_MATERIAL_GROUP3
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalMaterialGroup3 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_MATERIAL_GROUP4
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalMaterialGroup4 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ADDITIONAL_MATERIAL_GROUP5
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AdditionalMaterialGroup5 field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ALTERNATE_PRODUCT_NUMBER
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the AlternateProductNumber field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> BASE_UNIT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the BaseUnit field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> BATCH
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the Batch field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> BATCH_BY_SUPPLIER
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the BatchBySupplier field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> BATCH_CLASSIFICATION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the BatchClassification field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> B_O_M_EXPLOSION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the BOMExplosion field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> BUSINESS_AREA
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the BusinessArea field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> CONSUMPTION_POSTING
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ConsumptionPosting field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> CONTROLLING_AREA
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ControllingArea field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> COST_CENTER
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the CostCenter field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> CREATED_BY_USER
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the CreatedByUser field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> CREATION_DATE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the CreationDate field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> CREATION_TIME
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the CreationTime field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> CUST_ENGINEERING_CHG_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the CustEngineeringChgStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_DOCUMENT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryDocument field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_DOCUMENT_ITEM
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryDocumentItem field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_DOCUMENT_ITEM_CATEGORY
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryDocumentItemCategory field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_DOCUMENT_ITEM_TEXT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryDocumentItemText field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_GROUP
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryGroup field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_QUANTITY_UNIT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryQuantityUnit field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_RELATED_BILLING_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryRelatedBillingStatus field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_TO_BASE_QUANTITY_DNMNTR
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryToBaseQuantityDnmntr field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DELIVERY_TO_BASE_QUANTITY_NMRTR
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DeliveryToBaseQuantityNmrtr field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DEPARTMENT_CLASSIFICATION_BY_CUST
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DepartmentClassificationByCust field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DISTRIBUTION_CHANNEL
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the DistributionChannel field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> DIVISION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the Division field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> FIXED_SHIPG_PROCG_DURATION_IN_DAYS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the FixedShipgProcgDurationInDays field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> G_L_ACCOUNT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the GLAccount field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> GOODS_MOVEMENT_REASON_CODE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the GoodsMovementReasonCode field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> GOODS_MOVEMENT_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the GoodsMovementStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> GOODS_MOVEMENT_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the GoodsMovementType field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> HIGHER_LEVEL_ITEM
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the HigherLevelItem field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> INSPECTION_LOT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the InspectionLot field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> INSPECTION_PARTIAL_LOT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the InspectionPartialLot field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> INTERCOMPANY_BILLING_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IntercompanyBillingStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> INTERNATIONAL_ARTICLE_NUMBER
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the InternationalArticleNumber field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> INVENTORY_SPECIAL_STOCK_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the InventorySpecialStockType field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> INVENTORY_VALUATION_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the InventoryValuationType field to query operations.public static EntityField<Boolean,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> IS_COMPLETELY_DELIVERED
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IsCompletelyDelivered field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> IS_NOT_GOODS_MOVEMENTS_RELEVANT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IsNotGoodsMovementsRelevant field to query operations.public static EntityField<Boolean,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> IS_SEPARATE_VALUATION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IsSeparateValuation field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ISSG_OR_RCVG_BATCH
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IssgOrRcvgBatch field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ISSG_OR_RCVG_MATERIAL
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IssgOrRcvgMaterial field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ISSG_OR_RCVG_SPCL_STOCK_IND
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IssgOrRcvgSpclStockInd field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ISSG_OR_RCVG_STOCK_CATEGORY
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IssgOrRcvgStockCategory field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ISSG_OR_RCVG_VALUATION_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IssgOrRcvgValuationType field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ISSUING_OR_RECEIVING_PLANT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IssuingOrReceivingPlant field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ISSUING_OR_RECEIVING_STORAGE_LOC
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the IssuingOrReceivingStorageLoc field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_BILLING_BLOCK_REASON
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemBillingBlockReason field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_BILLING_INCOMPLETION_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemBillingIncompletionStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_DELIVERY_INCOMPLETION_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemDeliveryIncompletionStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_GDS_MVT_INCOMPLETION_STS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemGdsMvtIncompletionSts field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_GENERAL_INCOMPLETION_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemGeneralIncompletionStatus field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_GROSS_WEIGHT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemGrossWeight field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_IS_BILLING_RELEVANT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemIsBillingRelevant field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_NET_WEIGHT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemNetWeight field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_PACKING_INCOMPLETION_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemPackingIncompletionStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_PICKING_INCOMPLETION_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemPickingIncompletionStatus field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_VOLUME
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemVolume field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_VOLUME_UNIT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemVolumeUnit field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ITEM_WEIGHT_UNIT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ItemWeightUnit field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> LAST_CHANGE_DATE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the LastChangeDate field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> LOADING_GROUP
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the LoadingGroup field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> MANUFACTURE_DATE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ManufactureDate field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> MATERIAL
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the Material field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> MATERIAL_BY_CUSTOMER
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the MaterialByCustomer field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> MATERIAL_FREIGHT_GROUP
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the MaterialFreightGroup field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> MATERIAL_GROUP
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the MaterialGroup field to query operations.public static EntityField<Boolean,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> MATERIAL_IS_BATCH_MANAGED
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the MaterialIsBatchManaged field to query operations.public static EntityField<Boolean,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> MATERIAL_IS_INT_BATCH_MANAGED
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the MaterialIsIntBatchManaged field to query operations.public static EntityField<Integer,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> NUMBER_OF_SERIAL_NUMBERS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the NumberOfSerialNumbers field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ORDER_I_D
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the OrderID field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ORDER_ITEM
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the OrderItem field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ORIGINAL_DELIVERY_QUANTITY
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the OriginalDeliveryQuantity field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> ORIGINALLY_REQUESTED_MATERIAL
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the OriginallyRequestedMaterial field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> OVERDELIV_TOLRTD_LMT_RATIO_IN_PCT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the OverdelivTolrtdLmtRatioInPct field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PACKING_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the PackingStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PARTIAL_DELIVERY_IS_ALLOWED
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the PartialDeliveryIsAllowed field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PAYMENT_GUARANTEE_FORM
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the PaymentGuaranteeForm field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PICKING_CONFIRMATION_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the PickingConfirmationStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PICKING_CONTROL
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the PickingControl field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PICKING_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the PickingStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PLANT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the Plant field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PRIMARY_POSTING_SWITCH
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the PrimaryPostingSwitch field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PRODUCT_AVAILABILITY_DATE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProductAvailabilityDate field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PRODUCT_AVAILABILITY_TIME
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProductAvailabilityTime field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PRODUCT_CONFIGURATION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProductConfiguration field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PRODUCT_HIERARCHY_NODE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProductHierarchyNode field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PROFITABILITY_SEGMENT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProfitabilitySegment field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PROFIT_CENTER
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProfitCenter field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PROOF_OF_DELIVERY_RELEVANCE_CODE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProofOfDeliveryRelevanceCode field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> PROOF_OF_DELIVERY_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ProofOfDeliveryStatus field to query operations.public static EntityField<Boolean,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> QUANTITY_IS_FIXED
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the QuantityIsFixed field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> RECEIVING_POINT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ReceivingPoint field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> REFERENCE_DOCUMENT_LOGICAL_SYSTEM
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ReferenceDocumentLogicalSystem field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> REFERENCE_S_D_DOCUMENT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ReferenceSDDocument field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> REFERENCE_S_D_DOCUMENT_CATEGORY
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ReferenceSDDocumentCategory field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> REFERENCE_S_D_DOCUMENT_ITEM
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ReferenceSDDocumentItem field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> RETAIL_PROMOTION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the RetailPromotion field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> SALES_DOCUMENT_ITEM_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the SalesDocumentItemType field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> SALES_GROUP
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the SalesGroup field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> SALES_OFFICE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the SalesOffice field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> S_D_DOCUMENT_CATEGORY
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the SDDocumentCategory field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> S_D_PROCESS_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the SDProcessStatus field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> SHELF_LIFE_EXPIRATION_DATE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the ShelfLifeExpirationDate field to query operations.public static EntityField<Calendar,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> STATISTICS_DATE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the StatisticsDate field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> STOCK_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the StockType field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> STORAGE_BIN
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the StorageBin field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> STORAGE_LOCATION
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the StorageLocation field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> STORAGE_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the StorageType field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> SUBSEQUENT_MOVEMENT_TYPE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the SubsequentMovementType field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> TRANSPORTATION_GROUP
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the TransportationGroup field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> UNDERDELIV_TOLRTD_LMT_RATIO_IN_PCT
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the UnderdelivTolrtdLmtRatioInPct field to query operations.public static EntityField<Boolean,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> UNLIMITED_OVERDELIVERY_IS_ALLOWED
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the UnlimitedOverdeliveryIsAllowed field to query operations.public static EntityField<BigDecimal,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> VARBL_SHIPG_PROCG_DURATION_IN_DAYS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the VarblShipgProcgDurationInDays field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> WAREHOUSE
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the Warehouse field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> WAREHOUSE_ACTIVITY_STATUS
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the WarehouseActivityStatus field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> WAREHOUSE_STAGING_AREA
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the WarehouseStagingArea field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> WAREHOUSE_STOCK_CATEGORY
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the WarehouseStockCategory field to query operations.public static EntityField<String,ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem> WAREHOUSE_STORAGE_BIN
OutbDeliveryItemFluentHelper
and OutbDeliveryItemByKeyFluentHelper
to apply the WarehouseStorageBin field to query operations.@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem()
public List<ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryDocFlow> fetchDocumentFlow() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
com.sap.cloud.sdk.odatav2.connectivity.ODataException
public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.SerialNmbrDelivery fetchSerialDeliveryItem() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
com.sap.cloud.sdk.odatav2.connectivity.ODataException
@Generated(value="lombok") public String toString()
@Generated(value="lombok") public boolean equals(Object o)
@Generated(value="lombok") public int hashCode()
@Generated(value="lombok") public BigDecimal getActualDeliveredQtyInBaseUnit()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setActualDeliveredQtyInBaseUnit(BigDecimal actualDeliveredQtyInBaseUnit)
actualDeliveredQtyInBaseUnit
- @Generated(value="lombok") public String getDeliveryVersion()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryVersion(String deliveryVersion)
deliveryVersion
- @Generated(value="lombok") public BigDecimal getActualDeliveryQuantity()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setActualDeliveryQuantity(BigDecimal actualDeliveryQuantity)
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.
actualDeliveryQuantity
- @Generated(value="lombok") public String getAdditionalCustomerGroup1()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalCustomerGroup1(String additionalCustomerGroup1)
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.
additionalCustomerGroup1
- @Generated(value="lombok") public String getAdditionalCustomerGroup2()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalCustomerGroup2(String additionalCustomerGroup2)
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.
additionalCustomerGroup2
- @Generated(value="lombok") public String getAdditionalCustomerGroup3()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalCustomerGroup3(String additionalCustomerGroup3)
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.
additionalCustomerGroup3
- @Generated(value="lombok") public String getAdditionalCustomerGroup4()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalCustomerGroup4(String additionalCustomerGroup4)
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.
additionalCustomerGroup4
- @Generated(value="lombok") public String getAdditionalCustomerGroup5()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalCustomerGroup5(String additionalCustomerGroup5)
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.
additionalCustomerGroup5
- @Generated(value="lombok") public String getAdditionalMaterialGroup1()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalMaterialGroup1(String additionalMaterialGroup1)
additionalMaterialGroup1
- @Generated(value="lombok") public String getAdditionalMaterialGroup2()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalMaterialGroup2(String additionalMaterialGroup2)
additionalMaterialGroup2
- @Generated(value="lombok") public String getAdditionalMaterialGroup3()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalMaterialGroup3(String additionalMaterialGroup3)
additionalMaterialGroup3
- @Generated(value="lombok") public String getAdditionalMaterialGroup4()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalMaterialGroup4(String additionalMaterialGroup4)
additionalMaterialGroup4
- @Generated(value="lombok") public String getAdditionalMaterialGroup5()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAdditionalMaterialGroup5(String additionalMaterialGroup5)
additionalMaterialGroup5
- @Generated(value="lombok") public String getAlternateProductNumber()
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).
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setAlternateProductNumber(String alternateProductNumber)
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).
alternateProductNumber
- @Generated(value="lombok") public String getBaseUnit()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setBaseUnit(String baseUnit)
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record. Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following: The base unit of measure is the unit satisfying the highest necessary requirement for precision. The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...). Inventory 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.
baseUnit
- @Generated(value="lombok") public String getBatch()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setBatch(String batch)
batch
- @Generated(value="lombok") public String getBatchBySupplier()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setBatchBySupplier(String batchBySupplier)
batchBySupplier
- @Generated(value="lombok") public String getBatchClassification()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setBatchClassification(String batchClassification)
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.
batchClassification
- @Generated(value="lombok") public String getBOMExplosion()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setBOMExplosion(String bOMExplosion)
bOMExplosion
- @Generated(value="lombok") public String getBusinessArea()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setBusinessArea(String businessArea)
businessArea
- @Generated(value="lombok") public String getConsumptionPosting()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setConsumptionPosting(String consumptionPosting)
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.
consumptionPosting
- @Generated(value="lombok") public String getControllingArea()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setControllingArea(String controllingArea)
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.
controllingArea
- @Generated(value="lombok") public String getCostCenter()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setCostCenter(String costCenter)
costCenter
- @Generated(value="lombok") public String getCreatedByUser()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setCreatedByUser(String createdByUser)
createdByUser
- @Generated(value="lombok") public Calendar getCreationDate()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setCreationDate(Calendar creationDate)
creationDate
- @Generated(value="lombok") public Calendar getCreationTime()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setCreationTime(Calendar creationTime)
creationTime
- @Generated(value="lombok") public String getCustEngineeringChgStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setCustEngineeringChgStatus(String custEngineeringChgStatus)
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.
custEngineeringChgStatus
- @Generated(value="lombok") public String getDeliveryDocument()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryDocument(String deliveryDocument)
deliveryDocument
- @Generated(value="lombok") public String getDeliveryDocumentItem()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryDocumentItem(String deliveryDocumentItem)
deliveryDocumentItem
- @Generated(value="lombok") public String getDeliveryDocumentItemCategory()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryDocumentItemCategory(String deliveryDocumentItemCategory)
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.
deliveryDocumentItemCategory
- @Generated(value="lombok") public String getDeliveryDocumentItemText()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryDocumentItemText(String deliveryDocumentItemText)
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.
deliveryDocumentItemText
- @Generated(value="lombok") public String getDeliveryGroup()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryGroup(String deliveryGroup)
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.
deliveryGroup
- @Generated(value="lombok") public String getDeliveryQuantityUnit()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryQuantityUnit(String deliveryQuantityUnit)
deliveryQuantityUnit
- @Generated(value="lombok") public String getDeliveryRelatedBillingStatus()
The status line tells you if the item is not yet billed, is partly billed, is completely billed, or is not relevant for billing.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryRelatedBillingStatus(String deliveryRelatedBillingStatus)
The status line tells you if the item is not yet billed, is partly billed, is completely billed, or is not relevant for billing.
deliveryRelatedBillingStatus
- @Generated(value="lombok") public BigDecimal getDeliveryToBaseQuantityDnmntr()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryToBaseQuantityDnmntr(BigDecimal deliveryToBaseQuantityDnmntr)
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.
deliveryToBaseQuantityDnmntr
- @Generated(value="lombok") public BigDecimal getDeliveryToBaseQuantityNmrtr()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDeliveryToBaseQuantityNmrtr(BigDecimal deliveryToBaseQuantityNmrtr)
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.
deliveryToBaseQuantityNmrtr
- @Generated(value="lombok") public String getDepartmentClassificationByCust()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDepartmentClassificationByCust(String departmentClassificationByCust)
departmentClassificationByCust
- @Generated(value="lombok") public String getDistributionChannel()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDistributionChannel(String distributionChannel)
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.
distributionChannel
- @Generated(value="lombok") public String getDivision()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setDivision(String division)
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.
division
- @Generated(value="lombok") public BigDecimal getFixedShipgProcgDurationInDays()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setFixedShipgProcgDurationInDays(BigDecimal fixedShipgProcgDurationInDays)
fixedShipgProcgDurationInDays
- @Generated(value="lombok") public String getGLAccount()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setGLAccount(String gLAccount)
gLAccount
- @Generated(value="lombok") public String getGoodsMovementReasonCode()
Please do not change the entry in this field. Any changes made could lead to program errors or terminations.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setGoodsMovementReasonCode(String goodsMovementReasonCode)
Please do not change the entry in this field. Any changes made could lead to program errors or terminations.
goodsMovementReasonCode
- @Generated(value="lombok") public String getGoodsMovementStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setGoodsMovementStatus(String goodsMovementStatus)
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.
goodsMovementStatus
- @Generated(value="lombok") public String getGoodsMovementType()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setGoodsMovementType(String goodsMovementType)
goodsMovementType
- @Generated(value="lombok") public String getHigherLevelItem()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setHigherLevelItem(String higherLevelItem)
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.
higherLevelItem
- @Generated(value="lombok") public String getInspectionLot()
The inspection lot number is assigned by the system.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setInspectionLot(String inspectionLot)
The inspection lot number is assigned by the system.
inspectionLot
- @Generated(value="lombok") public String getInspectionPartialLot()
You can process partial lots by: Inspecting during production using inspection points Running a batch split for the delivery note
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setInspectionPartialLot(String inspectionPartialLot)
You can process partial lots by: Inspecting during production using inspection points Running a batch split for the delivery note
inspectionPartialLot
- @Generated(value="lombok") public String getIntercompanyBillingStatus()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIntercompanyBillingStatus(String intercompanyBillingStatus)
intercompanyBillingStatus
- @Generated(value="lombok") public String getInternationalArticleNumber()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setInternationalArticleNumber(String internationalArticleNumber)
internationalArticleNumber
- @Generated(value="lombok") public String getInventorySpecialStockType()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setInventorySpecialStockType(String inventorySpecialStockType)
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.
inventorySpecialStockType
- @Generated(value="lombok") public String getInventoryValuationType()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setInventoryValuationType(String inventoryValuationType)
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.
inventoryValuationType
- @Generated(value="lombok") public Boolean getIsCompletelyDelivered()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIsCompletelyDelivered(Boolean isCompletelyDelivered)
isCompletelyDelivered
- @Generated(value="lombok") public String getIsNotGoodsMovementsRelevant()
When this indicator is set, goods movement is not posted for this item - regardless of the movement type assigned to it.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIsNotGoodsMovementsRelevant(String isNotGoodsMovementsRelevant)
When this indicator is set, goods movement is not posted for this item - regardless of the movement type assigned to it.
isNotGoodsMovementsRelevant
- @Generated(value="lombok") public Boolean getIsSeparateValuation()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIsSeparateValuation(Boolean isSeparateValuation)
isSeparateValuation
- @Generated(value="lombok") public String getIssgOrRcvgBatch()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIssgOrRcvgBatch(String issgOrRcvgBatch)
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.
issgOrRcvgBatch
- @Generated(value="lombok") public String getIssgOrRcvgMaterial()
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
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIssgOrRcvgMaterial(String issgOrRcvgMaterial)
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
issgOrRcvgMaterial
- @Generated(value="lombok") public String getIssgOrRcvgSpclStockInd()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIssgOrRcvgSpclStockInd(String issgOrRcvgSpclStockInd)
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.
issgOrRcvgSpclStockInd
- @Generated(value="lombok") public String getIssgOrRcvgStockCategory()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIssgOrRcvgStockCategory(String issgOrRcvgStockCategory)
issgOrRcvgStockCategory
- @Generated(value="lombok") public String getIssgOrRcvgValuationType()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIssgOrRcvgValuationType(String issgOrRcvgValuationType)
issgOrRcvgValuationType
- @Generated(value="lombok") public String getIssuingOrReceivingPlant()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIssuingOrReceivingPlant(String issuingOrReceivingPlant)
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.
issuingOrReceivingPlant
- @Generated(value="lombok") public String getIssuingOrReceivingStorageLoc()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setIssuingOrReceivingStorageLoc(String issuingOrReceivingStorageLoc)
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.
issuingOrReceivingStorageLoc
- @Generated(value="lombok") public String getItemBillingBlockReason()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemBillingBlockReason(String itemBillingBlockReason)
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.
itemBillingBlockReason
- @Generated(value="lombok") public String getItemBillingIncompletionStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemBillingIncompletionStatus(String itemBillingIncompletionStatus)
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.
itemBillingIncompletionStatus
- @Generated(value="lombok") public String getItemDeliveryIncompletionStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemDeliveryIncompletionStatus(String itemDeliveryIncompletionStatus)
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.
itemDeliveryIncompletionStatus
- @Generated(value="lombok") public String getItemGdsMvtIncompletionSts()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemGdsMvtIncompletionSts(String itemGdsMvtIncompletionSts)
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.
itemGdsMvtIncompletionSts
- @Generated(value="lombok") public String getItemGeneralIncompletionStatus()
The status line tells you if all item information, necessary for further processing this item, is complete.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemGeneralIncompletionStatus(String itemGeneralIncompletionStatus)
The status line tells you if all item information, necessary for further processing this item, is complete.
itemGeneralIncompletionStatus
- @Generated(value="lombok") public BigDecimal getItemGrossWeight()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemGrossWeight(BigDecimal itemGrossWeight)
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.
itemGrossWeight
- @Generated(value="lombok") public String getItemIsBillingRelevant()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemIsBillingRelevant(String itemIsBillingRelevant)
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.
itemIsBillingRelevant
- @Generated(value="lombok") public BigDecimal getItemNetWeight()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemNetWeight(BigDecimal itemNetWeight)
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.
itemNetWeight
- @Generated(value="lombok") public String getItemPackingIncompletionStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemPackingIncompletionStatus(String itemPackingIncompletionStatus)
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.
itemPackingIncompletionStatus
- @Generated(value="lombok") public String getItemPickingIncompletionStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemPickingIncompletionStatus(String itemPickingIncompletionStatus)
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.
itemPickingIncompletionStatus
- @Generated(value="lombok") public BigDecimal getItemVolume()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemVolume(BigDecimal itemVolume)
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.
itemVolume
- @Generated(value="lombok") public String getItemVolumeUnit()
If you specify a volume, you have to enter the corresponding volume unit here.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemVolumeUnit(String itemVolumeUnit)
If you specify a volume, you have to enter the corresponding volume unit here.
itemVolumeUnit
- @Generated(value="lombok") public String getItemWeightUnit()
If you specify a weight, you must enter the corresponding unit of weight here.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setItemWeightUnit(String itemWeightUnit)
If you specify a weight, you must enter the corresponding unit of weight here.
itemWeightUnit
- @Generated(value="lombok") public Calendar getLastChangeDate()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setLastChangeDate(Calendar lastChangeDate)
lastChangeDate
- @Generated(value="lombok") public String getLoadingGroup()
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)
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setLoadingGroup(String loadingGroup)
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)
loadingGroup
- @Generated(value="lombok") public Calendar getManufactureDate()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setManufactureDate(Calendar manufactureDate)
manufactureDate
- @Generated(value="lombok") public String getMaterial()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setMaterial(String material)
material
- @Generated(value="lombok") public String getMaterialByCustomer()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setMaterialByCustomer(String materialByCustomer)
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.
materialByCustomer
- @Generated(value="lombok") public String getMaterialFreightGroup()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setMaterialFreightGroup(String materialFreightGroup)
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.
materialFreightGroup
- @Generated(value="lombok") public String getMaterialGroup()
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setMaterialGroup(String materialGroup)
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
materialGroup
- @Generated(value="lombok") public Boolean getMaterialIsBatchManaged()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setMaterialIsBatchManaged(Boolean materialIsBatchManaged)
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.
materialIsBatchManaged
- @Generated(value="lombok") public Boolean getMaterialIsIntBatchManaged()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setMaterialIsIntBatchManaged(Boolean materialIsIntBatchManaged)
materialIsIntBatchManaged
- @Generated(value="lombok") public Integer getNumberOfSerialNumbers()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setNumberOfSerialNumbers(Integer numberOfSerialNumbers)
numberOfSerialNumbers
- @Generated(value="lombok") public String getOrderID()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setOrderID(String orderID)
orderID
- @Generated(value="lombok") public String getOrderItem()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setOrderItem(String orderItem)
orderItem
- @Generated(value="lombok") public BigDecimal getOriginalDeliveryQuantity()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setOriginalDeliveryQuantity(BigDecimal originalDeliveryQuantity)
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.
originalDeliveryQuantity
- @Generated(value="lombok") public String getOriginallyRequestedMaterial()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setOriginallyRequestedMaterial(String originallyRequestedMaterial)
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.
originallyRequestedMaterial
- @Generated(value="lombok") public BigDecimal getOverdelivTolrtdLmtRatioInPct()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setOverdelivTolrtdLmtRatioInPct(BigDecimal overdelivTolrtdLmtRatioInPct)
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.
overdelivTolrtdLmtRatioInPct
- @Generated(value="lombok") public String getPackingStatus()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPackingStatus(String packingStatus)
packingStatus
- @Generated(value="lombok") public String getPartialDeliveryIsAllowed()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPartialDeliveryIsAllowed(String partialDeliveryIsAllowed)
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.
partialDeliveryIsAllowed
- @Generated(value="lombok") public String getPaymentGuaranteeForm()
The form of payment guarantee specifies how a sales document item is guaranteed. Payment cards Letter of credit Standby letter of credit Bank guarantee
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPaymentGuaranteeForm(String paymentGuaranteeForm)
The form of payment guarantee specifies how a sales document item is guaranteed. Payment cards Letter of credit Standby letter of credit Bank guarantee
paymentGuaranteeForm
- @Generated(value="lombok") public String getPickingConfirmationStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPickingConfirmationStatus(String pickingConfirmationStatus)
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.
pickingConfirmationStatus
- @Generated(value="lombok") public String getPickingControl()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPickingControl(String pickingControl)
pickingControl
- @Generated(value="lombok") public String getPickingStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPickingStatus(String pickingStatus)
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.
pickingStatus
- @Generated(value="lombok") public String getPlant()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPlant(String plant)
plant
- @Generated(value="lombok") public String getPrimaryPostingSwitch()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setPrimaryPostingSwitch(String primaryPostingSwitch)
primaryPostingSwitch
- @Generated(value="lombok") public Calendar getProductAvailabilityDate()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProductAvailabilityDate(Calendar productAvailabilityDate)
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.
productAvailabilityDate
- @Generated(value="lombok") public Calendar getProductAvailabilityTime()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProductAvailabilityTime(Calendar productAvailabilityTime)
productAvailabilityTime
- @Generated(value="lombok") public String getProductConfiguration()
This number clearly identifies one particular configuration of a standard product.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProductConfiguration(String productConfiguration)
This number clearly identifies one particular configuration of a standard product.
productConfiguration
- @Generated(value="lombok") public String getProductHierarchyNode()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProductHierarchyNode(String productHierarchyNode)
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.
productHierarchyNode
- @Generated(value="lombok") public String getProfitabilitySegment()
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
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProfitabilitySegment(String profitabilitySegment)
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
profitabilitySegment
- @Generated(value="lombok") public String getProfitCenter()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProfitCenter(String profitCenter)
profitCenter
- @Generated(value="lombok") public String getProofOfDeliveryRelevanceCode()
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".
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProofOfDeliveryRelevanceCode(String proofOfDeliveryRelevanceCode)
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".
proofOfDeliveryRelevanceCode
- @Generated(value="lombok") public String getProofOfDeliveryStatus()
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
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setProofOfDeliveryStatus(String proofOfDeliveryStatus)
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
proofOfDeliveryStatus
- @Generated(value="lombok") public Boolean getQuantityIsFixed()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setQuantityIsFixed(Boolean quantityIsFixed)
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.
quantityIsFixed
- @Generated(value="lombok") public String getReceivingPoint()
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).
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setReceivingPoint(String receivingPoint)
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).
receivingPoint
- @Generated(value="lombok") public String getReferenceDocumentLogicalSystem()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setReferenceDocumentLogicalSystem(String referenceDocumentLogicalSystem)
referenceDocumentLogicalSystem
- @Generated(value="lombok") public String getReferenceSDDocument()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setReferenceSDDocument(String referenceSDDocument)
referenceSDDocument
- @Generated(value="lombok") public String getReferenceSDDocumentCategory()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setReferenceSDDocumentCategory(String referenceSDDocumentCategory)
referenceSDDocumentCategory
- @Generated(value="lombok") public String getReferenceSDDocumentItem()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setReferenceSDDocumentItem(String referenceSDDocumentItem)
referenceSDDocumentItem
- @Generated(value="lombok") public String getRetailPromotion()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setRetailPromotion(String retailPromotion)
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.
retailPromotion
- @Generated(value="lombok") public String getSalesDocumentItemType()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setSalesDocumentItemType(String salesDocumentItemType)
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.
salesDocumentItemType
- @Generated(value="lombok") public String getSalesGroup()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setSalesGroup(String salesGroup)
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.
salesGroup
- @Generated(value="lombok") public String getSalesOffice()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setSalesOffice(String salesOffice)
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.
salesOffice
- @Generated(value="lombok") public String getSDDocumentCategory()
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).
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setSDDocumentCategory(String sDDocumentCategory)
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).
sDDocumentCategory
- @Generated(value="lombok") public String getSDProcessStatus()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setSDProcessStatus(String sDProcessStatus)
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.
sDProcessStatus
- @Generated(value="lombok") public Calendar getShelfLifeExpirationDate()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setShelfLifeExpirationDate(Calendar shelfLifeExpirationDate)
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.
shelfLifeExpirationDate
- @Generated(value="lombok") public Calendar getStatisticsDate()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setStatisticsDate(Calendar statisticsDate)
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.
statisticsDate
- @Generated(value="lombok") public String getStockType()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setStockType(String stockType)
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.
stockType
- @Generated(value="lombok") public String getStorageBin()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setStorageBin(String storageBin)
A storage bin can be further sub-divided into bin sections. Several different materials (quants) can be stored in one bin at the same time.
storageBin
- @Generated(value="lombok") public String getStorageLocation()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setStorageLocation(String storageLocation)
storageLocation
- @Generated(value="lombok") public String getStorageType()
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
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setStorageType(String storageType)
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
storageType
- @Generated(value="lombok") public String getSubsequentMovementType()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setSubsequentMovementType(String subsequentMovementType)
subsequentMovementType
- @Generated(value="lombok") public String getTransportationGroup()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setTransportationGroup(String transportationGroup)
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.
transportationGroup
- @Generated(value="lombok") public BigDecimal getUnderdelivTolrtdLmtRatioInPct()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setUnderdelivTolrtdLmtRatioInPct(BigDecimal underdelivTolrtdLmtRatioInPct)
underdelivTolrtdLmtRatioInPct
- @Generated(value="lombok") public Boolean getUnlimitedOverdeliveryIsAllowed()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setUnlimitedOverdeliveryIsAllowed(Boolean unlimitedOverdeliveryIsAllowed)
unlimitedOverdeliveryIsAllowed
- @Generated(value="lombok") public BigDecimal getVarblShipgProcgDurationInDays()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setVarblShipgProcgDurationInDays(BigDecimal varblShipgProcgDurationInDays)
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.
varblShipgProcgDurationInDays
- @Generated(value="lombok") public String getWarehouse()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setWarehouse(String warehouse)
All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
warehouse
- @Generated(value="lombok") public String getWarehouseActivityStatus()
If your delivery processing includes the SAP Warehouse Management (WM) system, the system automatically indicates the WM status for each item in a delivery.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setWarehouseActivityStatus(String warehouseActivityStatus)
If your delivery processing includes the SAP Warehouse Management (WM) system, the system automatically indicates the WM status for each item in a delivery.
warehouseActivityStatus
- @Generated(value="lombok") public String getWarehouseStagingArea()
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
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setWarehouseStagingArea(String warehouseStagingArea)
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
warehouseStagingArea
- @Generated(value="lombok") public String getWarehouseStockCategory()
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setWarehouseStockCategory(String warehouseStockCategory)
warehouseStockCategory
- @Generated(value="lombok") public String getWarehouseStorageBin()
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.
@Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setWarehouseStorageBin(String warehouseStorageBin)
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.
warehouseStorageBin
- @Generated(value="lombok") public ReadCreateUpdateAndDeleteOutboundDeliveriesNamespace.OutbDeliveryItem setErpConfigContext(ErpConfigContext erpConfigContext)
Copyright © 2017 SAP SE. All rights reserved.