public class OutbDeliveryHeader extends VdmEntity<OutbDeliveryHeader>
Original entity name from the Odata EDM: A_OutbDeliveryHeaderType
| Modifier and Type | Class and Description |
|---|---|
static class |
OutbDeliveryHeader.OutbDeliveryHeaderBuilder
Helper class to allow for fluent creation of OutbDeliveryHeader instances.
|
| Modifier and Type | Field and Description |
|---|---|
static OutbDeliveryHeaderField<String> |
ACTUAL_DELIVERY_ROUTE
Use with available fluent helpers to apply the ActualDeliveryRoute field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
ACTUAL_GOODS_MOVEMENT_DATE
Use with available fluent helpers to apply the ActualGoodsMovementDate field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
ACTUAL_GOODS_MOVEMENT_TIME
Use with available fluent helpers to apply the ActualGoodsMovementTime field to query operations.
|
static OutbDeliveryHeaderSelectable |
ALL_FIELDS
Selector for all available fields of OutbDeliveryHeader.
|
static OutbDeliveryHeaderField<String> |
BILL_OF_LADING
Use with available fluent helpers to apply the BillOfLading field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
BILLING_DOCUMENT_DATE
Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
|
static OutbDeliveryHeaderField<Boolean> |
COMPLETE_DELIVERY_IS_DEFINED
Use with available fluent helpers to apply the CompleteDeliveryIsDefined field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
CONFIRMATION_TIME
Use with available fluent helpers to apply the ConfirmationTime field to query operations.
|
static OutbDeliveryHeaderField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static OutbDeliveryHeaderField<String> |
CUSTOMER_GROUP
Use with available fluent helpers to apply the CustomerGroup field to query operations.
|
static OutbDeliveryHeaderField<String> |
DELIVERY_BLOCK_REASON
Use with available fluent helpers to apply the DeliveryBlockReason field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
DELIVERY_DATE
Use with available fluent helpers to apply the DeliveryDate field to query operations.
|
static OutbDeliveryHeaderField<String> |
DELIVERY_DOCUMENT
Use with available fluent helpers to apply the DeliveryDocument field to query operations.
|
static OutbDeliveryHeaderField<String> |
DELIVERY_DOCUMENT_BY_SUPPLIER
Use with available fluent helpers to apply the DeliveryDocumentBySupplier field to query operations.
|
static OutbDeliveryHeaderField<String> |
DELIVERY_DOCUMENT_TYPE
Use with available fluent helpers to apply the DeliveryDocumentType field to query operations.
|
static OutbDeliveryHeaderField<Boolean> |
DELIVERY_IS_IN_PLANT
Use with available fluent helpers to apply the DeliveryIsInPlant field to query operations.
|
static OutbDeliveryHeaderField<String> |
DELIVERY_PRIORITY
Use with available fluent helpers to apply the DeliveryPriority field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
DELIVERY_TIME
Use with available fluent helpers to apply the DeliveryTime field to query operations.
|
static OutbDeliveryHeaderField<String> |
DELIVERY_VERSION
Use with available fluent helpers to apply the DeliveryVersion field to query operations.
|
static OutbDeliveryHeaderField<BigDecimal> |
DEPRECIATION_PERCENTAGE
Use with available fluent helpers to apply the DepreciationPercentage field to query operations.
|
static OutbDeliveryHeaderField<String> |
DISTR_STATUS_BY_DECENTRALIZED_WRHS
Use with available fluent helpers to apply the DistrStatusByDecentralizedWrhs field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
DOCUMENT_DATE
Use with available fluent helpers to apply the DocumentDate field to query operations.
|
static OutbDeliveryHeaderField<String> |
EXTERNAL_IDENTIFICATION_TYPE
Use with available fluent helpers to apply the ExternalIdentificationType field to query operations.
|
static OutbDeliveryHeaderField<String> |
EXTERNAL_TRANSPORT_SYSTEM
Use with available fluent helpers to apply the ExternalTransportSystem field to query operations.
|
static OutbDeliveryHeaderField<String> |
FACTORY_CALENDAR_BY_CUSTOMER
Use with available fluent helpers to apply the FactoryCalendarByCustomer field to query operations.
|
static OutbDeliveryHeaderField<String> |
GOODS_ISSUE_OR_RECEIPT_SLIP_NUMBER
Use with available fluent helpers to apply the GoodsIssueOrReceiptSlipNumber field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
GOODS_ISSUE_TIME
Use with available fluent helpers to apply the GoodsIssueTime field to query operations.
|
static OutbDeliveryHeaderField<String> |
HANDLING_UNIT_IN_STOCK
Use with available fluent helpers to apply the HandlingUnitInStock field to query operations.
|
static OutbDeliveryHeaderField<String> |
HDR_GENERAL_INCOMPLETION_STATUS
Use with available fluent helpers to apply the HdrGeneralIncompletionStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
HDR_GOODS_MVT_INCOMPLETION_STATUS
Use with available fluent helpers to apply the HdrGoodsMvtIncompletionStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
HEADER_BILLG_INCOMPLETION_STATUS
Use with available fluent helpers to apply the HeaderBillgIncompletionStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
HEADER_BILLING_BLOCK_REASON
Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
|
static OutbDeliveryHeaderField<String> |
HEADER_DELIV_INCOMPLETION_STATUS
Use with available fluent helpers to apply the HeaderDelivIncompletionStatus field to query operations.
|
static OutbDeliveryHeaderField<BigDecimal> |
HEADER_GROSS_WEIGHT
Use with available fluent helpers to apply the HeaderGrossWeight field to query operations.
|
static OutbDeliveryHeaderField<BigDecimal> |
HEADER_NET_WEIGHT
Use with available fluent helpers to apply the HeaderNetWeight field to query operations.
|
static OutbDeliveryHeaderField<String> |
HEADER_PACKING_INCOMPLETION_STS
Use with available fluent helpers to apply the HeaderPackingIncompletionSts field to query operations.
|
static OutbDeliveryHeaderField<String> |
HEADER_PICKG_INCOMPLETION_STATUS
Use with available fluent helpers to apply the HeaderPickgIncompletionStatus field to query operations.
|
static OutbDeliveryHeaderField<BigDecimal> |
HEADER_VOLUME
Use with available fluent helpers to apply the HeaderVolume field to query operations.
|
static OutbDeliveryHeaderField<String> |
HEADER_VOLUME_UNIT
Use with available fluent helpers to apply the HeaderVolumeUnit field to query operations.
|
static OutbDeliveryHeaderField<String> |
HEADER_WEIGHT_UNIT
Use with available fluent helpers to apply the HeaderWeightUnit field to query operations.
|
static OutbDeliveryHeaderField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static OutbDeliveryHeaderField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
INTERCOMPANY_BILLING_DATE
Use with available fluent helpers to apply the IntercompanyBillingDate field to query operations.
|
static OutbDeliveryHeaderField<String> |
INTERNAL_FINANCIAL_DOCUMENT
Use with available fluent helpers to apply the InternalFinancialDocument field to query operations.
|
static OutbDeliveryHeaderField<String> |
IS_DELIVERY_FOR_SINGLE_WAREHOUSE
Use with available fluent helpers to apply the IsDeliveryForSingleWarehouse field to query operations.
|
static OutbDeliveryHeaderField<String> |
IS_EXPORT_DELIVERY
Use with available fluent helpers to apply the IsExportDelivery field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static OutbDeliveryHeaderField<String> |
LAST_CHANGED_BY_USER
Use with available fluent helpers to apply the LastChangedByUser field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
LOADING_DATE
Use with available fluent helpers to apply the LoadingDate field to query operations.
|
static OutbDeliveryHeaderField<String> |
LOADING_POINT
Use with available fluent helpers to apply the LoadingPoint field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
LOADING_TIME
Use with available fluent helpers to apply the LoadingTime field to query operations.
|
static OutbDeliveryHeaderField<String> |
MEANS_OF_TRANSPORT
Use with available fluent helpers to apply the MeansOfTransport field to query operations.
|
static OutbDeliveryHeaderField<String> |
MEANS_OF_TRANSPORT_REF_MATERIAL
Use with available fluent helpers to apply the MeansOfTransportRefMaterial field to query operations.
|
static OutbDeliveryHeaderField<String> |
MEANS_OF_TRANSPORT_TYPE
Use with available fluent helpers to apply the MeansOfTransportType field to query operations.
|
static OutbDeliveryHeaderField<Boolean> |
ORDER_COMBINATION_IS_ALLOWED
Use with available fluent helpers to apply the OrderCombinationIsAllowed field to query operations.
|
static OutbDeliveryHeaderField<String> |
ORDER_ID
Use with available fluent helpers to apply the OrderID field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_DELIV_CONF_STATUS
Use with available fluent helpers to apply the OverallDelivConfStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_DELIV_RELTD_BILLG_STATUS
Use with available fluent helpers to apply the OverallDelivReltdBillgStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_GOODS_MOVEMENT_STATUS
Use with available fluent helpers to apply the OverallGoodsMovementStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_INTCO_BILLING_STATUS
Use with available fluent helpers to apply the OverallIntcoBillingStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_PACKING_STATUS
Use with available fluent helpers to apply the OverallPackingStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_PICKING_CONF_STATUS
Use with available fluent helpers to apply the OverallPickingConfStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_PICKING_STATUS
Use with available fluent helpers to apply the OverallPickingStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_PROOF_OF_DELIVERY_STATUS
Use with available fluent helpers to apply the OverallProofOfDeliveryStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_SD_PROCESS_STATUS
Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVERALL_WAREHOUSE_ACTIVITY_STATUS
Use with available fluent helpers to apply the OverallWarehouseActivityStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVRL_ITM_DELIV_INCOMPLETION_STS
Use with available fluent helpers to apply the OvrlItmDelivIncompletionSts field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVRL_ITM_GDS_MVT_INCOMPLETION_STS
Use with available fluent helpers to apply the OvrlItmGdsMvtIncompletionSts field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVRL_ITM_GENERAL_INCOMPLETION_STS
Use with available fluent helpers to apply the OvrlItmGeneralIncompletionSts field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVRL_ITM_PACKING_INCOMPLETION_STS
Use with available fluent helpers to apply the OvrlItmPackingIncompletionSts field to query operations.
|
static OutbDeliveryHeaderField<String> |
OVRL_ITM_PICKING_INCOMPLETION_STS
Use with available fluent helpers to apply the OvrlItmPickingIncompletionSts field to query operations.
|
static OutbDeliveryHeaderField<String> |
PAYMENT_GUARANTEE_PROCEDURE
Use with available fluent helpers to apply the PaymentGuaranteeProcedure field to query operations.
|
static OutbDeliveryHeaderField<String> |
PICKED_ITEMS_LOCATION
Use with available fluent helpers to apply the PickedItemsLocation field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
PICKING_DATE
Use with available fluent helpers to apply the PickingDate field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
PICKING_TIME
Use with available fluent helpers to apply the PickingTime field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
PLANNED_GOODS_ISSUE_DATE
Use with available fluent helpers to apply the PlannedGoodsIssueDate field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
PROOF_OF_DELIVERY_DATE
Use with available fluent helpers to apply the ProofOfDeliveryDate field to query operations.
|
static OutbDeliveryHeaderField<String> |
PROPOSED_DELIVERY_ROUTE
Use with available fluent helpers to apply the ProposedDeliveryRoute field to query operations.
|
static OutbDeliveryHeaderField<String> |
RECEIVING_PLANT
Use with available fluent helpers to apply the ReceivingPlant field to query operations.
|
static OutbDeliveryHeaderField<String> |
RECEIVINGLOCATIONTIMEZONE
Use with available fluent helpers to apply the Receivinglocationtimezone field to query operations.
|
static OutbDeliveryHeaderField<String> |
ROUTE_SCHEDULE
Use with available fluent helpers to apply the RouteSchedule field to query operations.
|
static OutbDeliveryHeaderField<String> |
SALES_DISTRICT
Use with available fluent helpers to apply the SalesDistrict field to query operations.
|
static OutbDeliveryHeaderField<String> |
SALES_OFFICE
Use with available fluent helpers to apply the SalesOffice field to query operations.
|
static OutbDeliveryHeaderField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static OutbDeliveryHeaderField<String> |
SD_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the SDDocumentCategory field to query operations.
|
static OutbDeliveryHeaderField<String> |
SHIP_TO_PARTY
Use with available fluent helpers to apply the ShipToParty field to query operations.
|
static OutbDeliveryHeaderField<String> |
SHIPMENT_BLOCK_REASON
Use with available fluent helpers to apply the ShipmentBlockReason field to query operations.
|
static OutbDeliveryHeaderField<String> |
SHIPPING_CONDITION
Use with available fluent helpers to apply the ShippingCondition field to query operations.
|
static OutbDeliveryHeaderField<String> |
SHIPPING_POINT
Use with available fluent helpers to apply the ShippingPoint field to query operations.
|
static OutbDeliveryHeaderField<String> |
SHIPPING_TYPE
Use with available fluent helpers to apply the ShippingType field to query operations.
|
static OutbDeliveryHeaderField<String> |
SHIPPINGLOCATIONTIMEZONE
Use with available fluent helpers to apply the Shippinglocationtimezone field to query operations.
|
static OutbDeliveryHeaderField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static OutbDeliveryHeaderField<String> |
SPECIAL_PROCESSING_CODE
Use with available fluent helpers to apply the SpecialProcessingCode field to query operations.
|
static OutbDeliveryHeaderField<String> |
STATISTICS_CURRENCY
Use with available fluent helpers to apply the StatisticsCurrency field to query operations.
|
static OutbDeliveryHeaderField<String> |
SUPPLIER
Use with available fluent helpers to apply the Supplier field to query operations.
|
static OutbDeliveryHeaderLink<OutbDeliveryItem> |
TO_DELIVERY_DOCUMENT_ITEM
Use with available fluent helpers to apply the to_DeliveryDocumentItem navigation property to query
operations.
|
static OutbDeliveryHeaderLink<OutbDeliveryPartner> |
TO_DELIVERY_DOCUMENT_PARTNER
Use with available fluent helpers to apply the to_DeliveryDocumentPartner navigation property to query
operations.
|
static OutbDeliveryHeaderField<String> |
TOTAL_BLOCK_STATUS
Use with available fluent helpers to apply the TotalBlockStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
TOTAL_CREDIT_CHECK_STATUS
Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
|
static OutbDeliveryHeaderField<String> |
TOTAL_NUMBER_OF_PACKAGE
Use with available fluent helpers to apply the TotalNumberOfPackage field to query operations.
|
static OutbDeliveryHeaderField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
static OutbDeliveryHeaderField<String> |
TRANSPORTATION_GROUP
Use with available fluent helpers to apply the TransportationGroup field to query operations.
|
static OutbDeliveryHeaderField<LocalDateTime> |
TRANSPORTATION_PLANNING_DATE
Use with available fluent helpers to apply the TransportationPlanningDate field to query operations.
|
static OutbDeliveryHeaderField<String> |
TRANSPORTATION_PLANNING_STATUS
Use with available fluent helpers to apply the TransportationPlanningStatus field to query operations.
|
static OutbDeliveryHeaderField<LocalTime> |
TRANSPORTATION_PLANNING_TIME
Use with available fluent helpers to apply the TransportationPlanningTime field to query operations.
|
static OutbDeliveryHeaderField<String> |
UNLOADING_POINT_NAME
Use with available fluent helpers to apply the UnloadingPointName field to query operations.
|
static OutbDeliveryHeaderField<String> |
WAREHOUSE
Use with available fluent helpers to apply the Warehouse field to query operations.
|
static OutbDeliveryHeaderField<String> |
WAREHOUSE_GATE
Use with available fluent helpers to apply the WarehouseGate field to query operations.
|
static OutbDeliveryHeaderField<String> |
WAREHOUSE_STAGING_AREA
Use with available fluent helpers to apply the WarehouseStagingArea field to query operations.
|
changedOriginalFields| Constructor and Description |
|---|
OutbDeliveryHeader() |
OutbDeliveryHeader(String actualDeliveryRoute,
String shippinglocationtimezone,
String receivinglocationtimezone,
LocalDateTime actualGoodsMovementDate,
LocalTime actualGoodsMovementTime,
LocalDateTime billingDocumentDate,
String billOfLading,
Boolean completeDeliveryIsDefined,
LocalTime confirmationTime,
String createdByUser,
LocalDateTime creationDate,
LocalTime creationTime,
String customerGroup,
String deliveryBlockReason,
LocalDateTime deliveryDate,
String deliveryDocument,
String deliveryDocumentBySupplier,
String deliveryDocumentType,
Boolean deliveryIsInPlant,
String deliveryPriority,
LocalTime deliveryTime,
String deliveryVersion,
BigDecimal depreciationPercentage,
String distrStatusByDecentralizedWrhs,
LocalDateTime documentDate,
String externalIdentificationType,
String externalTransportSystem,
String factoryCalendarByCustomer,
String goodsIssueOrReceiptSlipNumber,
LocalTime goodsIssueTime,
String handlingUnitInStock,
String hdrGeneralIncompletionStatus,
String hdrGoodsMvtIncompletionStatus,
String headerBillgIncompletionStatus,
String headerBillingBlockReason,
String headerDelivIncompletionStatus,
BigDecimal headerGrossWeight,
BigDecimal headerNetWeight,
String headerPackingIncompletionSts,
String headerPickgIncompletionStatus,
BigDecimal headerVolume,
String headerVolumeUnit,
String headerWeightUnit,
String incotermsClassification,
String incotermsTransferLocation,
LocalDateTime intercompanyBillingDate,
String internalFinancialDocument,
String isDeliveryForSingleWarehouse,
String isExportDelivery,
LocalDateTime lastChangeDate,
String lastChangedByUser,
LocalDateTime loadingDate,
String loadingPoint,
LocalTime loadingTime,
String meansOfTransport,
String meansOfTransportRefMaterial,
String meansOfTransportType,
Boolean orderCombinationIsAllowed,
String orderID,
String overallDelivConfStatus,
String overallDelivReltdBillgStatus,
String overallGoodsMovementStatus,
String overallIntcoBillingStatus,
String overallPackingStatus,
String overallPickingConfStatus,
String overallPickingStatus,
String overallProofOfDeliveryStatus,
String overallSDProcessStatus,
String overallWarehouseActivityStatus,
String ovrlItmDelivIncompletionSts,
String ovrlItmGdsMvtIncompletionSts,
String ovrlItmGeneralIncompletionSts,
String ovrlItmPackingIncompletionSts,
String ovrlItmPickingIncompletionSts,
String paymentGuaranteeProcedure,
String pickedItemsLocation,
LocalDateTime pickingDate,
LocalTime pickingTime,
LocalDateTime plannedGoodsIssueDate,
LocalDateTime proofOfDeliveryDate,
String proposedDeliveryRoute,
String receivingPlant,
String routeSchedule,
String salesDistrict,
String salesOffice,
String salesOrganization,
String sDDocumentCategory,
String shipmentBlockReason,
String shippingCondition,
String shippingPoint,
String shippingType,
String shipToParty,
String soldToParty,
String specialProcessingCode,
String statisticsCurrency,
String supplier,
String totalBlockStatus,
String totalCreditCheckStatus,
String totalNumberOfPackage,
String transactionCurrency,
String transportationGroup,
LocalDateTime transportationPlanningDate,
String transportationPlanningStatus,
LocalTime transportationPlanningTime,
String unloadingPointName,
String warehouse,
String warehouseGate,
String warehouseStagingArea,
List<OutbDeliveryPartner> toDeliveryDocumentPartner,
List<OutbDeliveryItem> toDeliveryDocumentItem) |
| Modifier and Type | Method and Description |
|---|---|
void |
addDeliveryDocumentItem(OutbDeliveryItem... entity)
Adds elements to the list of associated OutbDeliveryItem entities.
|
void |
addDeliveryDocumentPartner(OutbDeliveryPartner... entity)
Adds elements to the list of associated OutbDeliveryPartner entities.
|
void |
attachToService(String servicePath,
ErpConfigContext configContext)
Sets the service path and ERP configuration context for the fetch commands of this entity.
|
static OutbDeliveryHeader.OutbDeliveryHeaderBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<OutbDeliveryItem> |
fetchDeliveryDocumentItem()
Fetches the OutbDeliveryItem entities (one to many) associated with this entity.
|
List<OutbDeliveryPartner> |
fetchDeliveryDocumentPartner()
Fetches the OutbDeliveryPartner entities (one to many) associated with this entity.
|
static <T> OutbDeliveryHeaderField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getActualDeliveryRoute()
Constraints: Not nullable, Maximum length: 6
|
LocalDateTime |
getActualGoodsMovementDate()
Constraints: Not nullable, Precision: 7
|
LocalTime |
getActualGoodsMovementTime()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getBillingDocumentDate()
Constraints: Not nullable, Precision: 7
|
String |
getBillOfLading()
Constraints: Not nullable, Maximum length: 35
|
Boolean |
getCompleteDeliveryIsDefined()
Constraints: none
|
LocalTime |
getConfirmationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 7
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerGroup()
Constraints: Not nullable, Maximum length: 2
|
protected String |
getDefaultServicePath() |
String |
getDeliveryBlockReason()
Constraints: Not nullable, Maximum length: 2
|
LocalDateTime |
getDeliveryDate()
Constraints: Not nullable, Precision: 7
|
String |
getDeliveryDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getDeliveryDocumentBySupplier()
Constraints: Not nullable, Maximum length: 35
|
Optional<List<OutbDeliveryItem>> |
getDeliveryDocumentItemIfPresent()
Retrieval of associated OutbDeliveryItem entities (one to many).
|
List<OutbDeliveryItem> |
getDeliveryDocumentItemOrFetch()
Retrieval of associated OutbDeliveryItem entities (one to many).
|
Optional<List<OutbDeliveryPartner>> |
getDeliveryDocumentPartnerIfPresent()
Retrieval of associated OutbDeliveryPartner entities (one to many).
|
List<OutbDeliveryPartner> |
getDeliveryDocumentPartnerOrFetch()
Retrieval of associated OutbDeliveryPartner entities (one to many).
|
String |
getDeliveryDocumentType()
Constraints: Not nullable, Maximum length: 4
|
Boolean |
getDeliveryIsInPlant()
Constraints: none
|
String |
getDeliveryPriority()
Constraints: Not nullable, Maximum length: 2
|
LocalTime |
getDeliveryTime()
Constraints: Not nullable, Precision: 0
|
String |
getDeliveryVersion()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getDepreciationPercentage()
Constraints: Not nullable, Precision: 5, Scale: 2
|
String |
getDistrStatusByDecentralizedWrhs()
Constraints: Not nullable, Maximum length: 1
|
LocalDateTime |
getDocumentDate()
Constraints: Not nullable, Precision: 7
|
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getExternalIdentificationType()
Constraints: Not nullable, Maximum length: 1
|
String |
getExternalTransportSystem()
Constraints: Not nullable, Maximum length: 5
|
String |
getFactoryCalendarByCustomer()
Constraints: Not nullable, Maximum length: 2
|
String |
getGoodsIssueOrReceiptSlipNumber()
Constraints: Not nullable, Maximum length: 10
|
LocalTime |
getGoodsIssueTime()
Constraints: Not nullable, Precision: 0
|
String |
getHandlingUnitInStock()
Constraints: Not nullable, Maximum length: 1
|
String |
getHdrGeneralIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getHdrGoodsMvtIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getHeaderBillgIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getHeaderBillingBlockReason()
Constraints: Not nullable, Maximum length: 2
|
String |
getHeaderDelivIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getHeaderGrossWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
BigDecimal |
getHeaderNetWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getHeaderPackingIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getHeaderPickgIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getHeaderVolume()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getHeaderVolumeUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getHeaderWeightUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
LocalDateTime |
getIntercompanyBillingDate()
Constraints: Not nullable, Precision: 7
|
String |
getInternalFinancialDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getIsDeliveryForSingleWarehouse()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsExportDelivery()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getLastChangeDate()
Constraints: Not nullable, Precision: 7
|
String |
getLastChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getLoadingDate()
Constraints: Not nullable, Precision: 7
|
String |
getLoadingPoint()
Constraints: Not nullable, Maximum length: 2
|
LocalTime |
getLoadingTime()
Constraints: Not nullable, Precision: 0
|
String |
getMeansOfTransport()
Constraints: Not nullable, Maximum length: 20
|
String |
getMeansOfTransportRefMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMeansOfTransportType()
Constraints: Not nullable, Maximum length: 4
|
Boolean |
getOrderCombinationIsAllowed()
Constraints: none
|
String |
getOrderID()
Constraints: Not nullable, Maximum length: 12
|
String |
getOverallDelivConfStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallDelivReltdBillgStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallGoodsMovementStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallIntcoBillingStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallPackingStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallPickingConfStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallPickingStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallProofOfDeliveryStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallWarehouseActivityStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOvrlItmDelivIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getOvrlItmGdsMvtIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getOvrlItmGeneralIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getOvrlItmPackingIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getOvrlItmPickingIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getPaymentGuaranteeProcedure()
Constraints: Not nullable, Maximum length: 6
|
String |
getPickedItemsLocation()
Constraints: Not nullable, Maximum length: 20
|
LocalDateTime |
getPickingDate()
Constraints: Not nullable, Precision: 7
|
LocalTime |
getPickingTime()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getPlannedGoodsIssueDate()
Constraints: Not nullable, Precision: 7
|
LocalDateTime |
getProofOfDeliveryDate()
Constraints: Not nullable, Precision: 7
|
String |
getProposedDeliveryRoute()
Constraints: Not nullable, Maximum length: 6
|
String |
getReceivinglocationtimezone()
Constraints: Not nullable, Maximum length: 6
|
String |
getReceivingPlant()
Constraints: Not nullable, Maximum length: 4
|
String |
getRouteSchedule()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesDistrict()
Constraints: Not nullable, Maximum length: 6
|
String |
getSalesOffice()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
String |
getSDDocumentCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getShipmentBlockReason()
Constraints: Not nullable, Maximum length: 2
|
String |
getShippingCondition()
Constraints: Not nullable, Maximum length: 2
|
String |
getShippinglocationtimezone()
Constraints: Not nullable, Maximum length: 6
|
String |
getShippingPoint()
Constraints: Not nullable, Maximum length: 4
|
String |
getShippingType()
Constraints: Not nullable, Maximum length: 2
|
String |
getShipToParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getSpecialProcessingCode()
Constraints: Not nullable, Maximum length: 4
|
String |
getStatisticsCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getSupplier()
Constraints: Not nullable, Maximum length: 10
|
String |
getTotalBlockStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getTotalCreditCheckStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getTotalNumberOfPackage()
Constraints: Not nullable, Maximum length: 5
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getTransportationGroup()
Constraints: Not nullable, Maximum length: 4
|
LocalDateTime |
getTransportationPlanningDate()
Constraints: Not nullable, Precision: 7
|
String |
getTransportationPlanningStatus()
Constraints: Not nullable, Maximum length: 1
|
LocalTime |
getTransportationPlanningTime()
Constraints: Not nullable, Precision: 0
|
Class<OutbDeliveryHeader> |
getType() |
String |
getUnloadingPointName()
Constraints: Not nullable, Maximum length: 25
|
String |
getWarehouse()
Constraints: Not nullable, Maximum length: 3
|
String |
getWarehouseGate()
Constraints: Not nullable, Maximum length: 3
|
String |
getWarehouseStagingArea()
Constraints: Not nullable, Maximum length: 10
|
int |
hashCode() |
void |
setActualDeliveryRoute(String actualDeliveryRoute)
Constraints: Not nullable, Maximum length: 6
|
void |
setActualGoodsMovementDate(LocalDateTime actualGoodsMovementDate)
Constraints: Not nullable, Precision: 7
|
void |
setActualGoodsMovementTime(LocalTime actualGoodsMovementTime)
Constraints: Not nullable, Precision: 0
|
void |
setBillingDocumentDate(LocalDateTime billingDocumentDate)
Constraints: Not nullable, Precision: 7
|
void |
setBillOfLading(String billOfLading)
Constraints: Not nullable, Maximum length: 35
|
void |
setCompleteDeliveryIsDefined(Boolean completeDeliveryIsDefined)
Constraints: none
|
void |
setConfirmationTime(LocalTime confirmationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 7
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerGroup(String customerGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setDeliveryBlockReason(String deliveryBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setDeliveryDate(LocalDateTime deliveryDate)
Constraints: Not nullable, Precision: 7
|
void |
setDeliveryDocument(String deliveryDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setDeliveryDocumentBySupplier(String deliveryDocumentBySupplier)
Constraints: Not nullable, Maximum length: 35
|
void |
setDeliveryDocumentItem(List<OutbDeliveryItem> value)
Overwrites the list of associated OutbDeliveryItem entities for the loaded navigation property
to_DeliveryDocumentItem.
|
void |
setDeliveryDocumentPartner(List<OutbDeliveryPartner> value)
Overwrites the list of associated OutbDeliveryPartner entities for the loaded navigation property
to_DeliveryDocumentPartner.
|
void |
setDeliveryDocumentType(String deliveryDocumentType)
Constraints: Not nullable, Maximum length: 4
|
void |
setDeliveryIsInPlant(Boolean deliveryIsInPlant)
Constraints: none
|
void |
setDeliveryPriority(String deliveryPriority)
Constraints: Not nullable, Maximum length: 2
|
void |
setDeliveryTime(LocalTime deliveryTime)
Constraints: Not nullable, Precision: 0
|
void |
setDeliveryVersion(String deliveryVersion)
Constraints: Not nullable, Maximum length: 4
|
void |
setDepreciationPercentage(BigDecimal depreciationPercentage)
Constraints: Not nullable, Precision: 5, Scale: 2
|
void |
setDistrStatusByDecentralizedWrhs(String distrStatusByDecentralizedWrhs)
Constraints: Not nullable, Maximum length: 1
|
void |
setDocumentDate(LocalDateTime documentDate)
Constraints: Not nullable, Precision: 7
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Deprecated.
Use
attachToService(String, ErpConfigContext) instead. |
void |
setExternalIdentificationType(String externalIdentificationType)
Constraints: Not nullable, Maximum length: 1
|
void |
setExternalTransportSystem(String externalTransportSystem)
Constraints: Not nullable, Maximum length: 5
|
void |
setFactoryCalendarByCustomer(String factoryCalendarByCustomer)
Constraints: Not nullable, Maximum length: 2
|
void |
setGoodsIssueOrReceiptSlipNumber(String goodsIssueOrReceiptSlipNumber)
Constraints: Not nullable, Maximum length: 10
|
void |
setGoodsIssueTime(LocalTime goodsIssueTime)
Constraints: Not nullable, Precision: 0
|
void |
setHandlingUnitInStock(String handlingUnitInStock)
Constraints: Not nullable, Maximum length: 1
|
void |
setHdrGeneralIncompletionStatus(String hdrGeneralIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setHdrGoodsMvtIncompletionStatus(String hdrGoodsMvtIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setHeaderBillgIncompletionStatus(String headerBillgIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setHeaderBillingBlockReason(String headerBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setHeaderDelivIncompletionStatus(String headerDelivIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setHeaderGrossWeight(BigDecimal headerGrossWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setHeaderNetWeight(BigDecimal headerNetWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setHeaderPackingIncompletionSts(String headerPackingIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setHeaderPickgIncompletionStatus(String headerPickgIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setHeaderVolume(BigDecimal headerVolume)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setHeaderVolumeUnit(String headerVolumeUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setHeaderWeightUnit(String headerWeightUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
void |
setIntercompanyBillingDate(LocalDateTime intercompanyBillingDate)
Constraints: Not nullable, Precision: 7
|
void |
setInternalFinancialDocument(String internalFinancialDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setIsDeliveryForSingleWarehouse(String isDeliveryForSingleWarehouse)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsExportDelivery(String isExportDelivery)
Constraints: Not nullable, Maximum length: 1
|
void |
setLastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 7
|
void |
setLastChangedByUser(String lastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setLoadingDate(LocalDateTime loadingDate)
Constraints: Not nullable, Precision: 7
|
void |
setLoadingPoint(String loadingPoint)
Constraints: Not nullable, Maximum length: 2
|
void |
setLoadingTime(LocalTime loadingTime)
Constraints: Not nullable, Precision: 0
|
void |
setMeansOfTransport(String meansOfTransport)
Constraints: Not nullable, Maximum length: 20
|
void |
setMeansOfTransportRefMaterial(String meansOfTransportRefMaterial)
Constraints: Not nullable, Maximum length: 40
|
void |
setMeansOfTransportType(String meansOfTransportType)
Constraints: Not nullable, Maximum length: 4
|
void |
setOrderCombinationIsAllowed(Boolean orderCombinationIsAllowed)
Constraints: none
|
void |
setOrderID(String orderID)
Constraints: Not nullable, Maximum length: 12
|
void |
setOverallDelivConfStatus(String overallDelivConfStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallDelivReltdBillgStatus(String overallDelivReltdBillgStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallGoodsMovementStatus(String overallGoodsMovementStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallIntcoBillingStatus(String overallIntcoBillingStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallPackingStatus(String overallPackingStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallPickingConfStatus(String overallPickingConfStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallPickingStatus(String overallPickingStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallProofOfDeliveryStatus(String overallProofOfDeliveryStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallWarehouseActivityStatus(String overallWarehouseActivityStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOvrlItmDelivIncompletionSts(String ovrlItmDelivIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setOvrlItmGdsMvtIncompletionSts(String ovrlItmGdsMvtIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setOvrlItmGeneralIncompletionSts(String ovrlItmGeneralIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setOvrlItmPackingIncompletionSts(String ovrlItmPackingIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setOvrlItmPickingIncompletionSts(String ovrlItmPickingIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setPaymentGuaranteeProcedure(String paymentGuaranteeProcedure)
Constraints: Not nullable, Maximum length: 6
|
void |
setPickedItemsLocation(String pickedItemsLocation)
Constraints: Not nullable, Maximum length: 20
|
void |
setPickingDate(LocalDateTime pickingDate)
Constraints: Not nullable, Precision: 7
|
void |
setPickingTime(LocalTime pickingTime)
Constraints: Not nullable, Precision: 0
|
void |
setPlannedGoodsIssueDate(LocalDateTime plannedGoodsIssueDate)
Constraints: Not nullable, Precision: 7
|
void |
setProofOfDeliveryDate(LocalDateTime proofOfDeliveryDate)
Constraints: Not nullable, Precision: 7
|
void |
setProposedDeliveryRoute(String proposedDeliveryRoute)
Constraints: Not nullable, Maximum length: 6
|
void |
setReceivinglocationtimezone(String receivinglocationtimezone)
Constraints: Not nullable, Maximum length: 6
|
void |
setReceivingPlant(String receivingPlant)
Constraints: Not nullable, Maximum length: 4
|
void |
setRouteSchedule(String routeSchedule)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesDistrict(String salesDistrict)
Constraints: Not nullable, Maximum length: 6
|
void |
setSalesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
void |
setSDDocumentCategory(String sDDocumentCategory)
Constraints: Not nullable, Maximum length: 4
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setShipmentBlockReason(String shipmentBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setShippingCondition(String shippingCondition)
Constraints: Not nullable, Maximum length: 2
|
void |
setShippinglocationtimezone(String shippinglocationtimezone)
Constraints: Not nullable, Maximum length: 6
|
void |
setShippingPoint(String shippingPoint)
Constraints: Not nullable, Maximum length: 4
|
void |
setShippingType(String shippingType)
Constraints: Not nullable, Maximum length: 2
|
void |
setShipToParty(String shipToParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setSoldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setSpecialProcessingCode(String specialProcessingCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setStatisticsCurrency(String statisticsCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setSupplier(String supplier)
Constraints: Not nullable, Maximum length: 10
|
void |
setTotalBlockStatus(String totalBlockStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setTotalCreditCheckStatus(String totalCreditCheckStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setTotalNumberOfPackage(String totalNumberOfPackage)
Constraints: Not nullable, Maximum length: 5
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setTransportationGroup(String transportationGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setTransportationPlanningDate(LocalDateTime transportationPlanningDate)
Constraints: Not nullable, Precision: 7
|
void |
setTransportationPlanningStatus(String transportationPlanningStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setTransportationPlanningTime(LocalTime transportationPlanningTime)
Constraints: Not nullable, Precision: 0
|
void |
setUnloadingPointName(String unloadingPointName)
Constraints: Not nullable, Maximum length: 25
|
void |
setWarehouse(String warehouse)
Constraints: Not nullable, Maximum length: 3
|
void |
setWarehouseGate(String warehouseGate)
Constraints: Not nullable, Maximum length: 3
|
void |
setWarehouseStagingArea(String warehouseStagingArea)
Constraints: Not nullable, Maximum length: 10
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setVersionIdentifiergetChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFieldspublic static final OutbDeliveryHeaderSelectable ALL_FIELDS
public static final OutbDeliveryHeaderField<String> ACTUAL_DELIVERY_ROUTE
public static final OutbDeliveryHeaderField<String> SHIPPINGLOCATIONTIMEZONE
public static final OutbDeliveryHeaderField<String> RECEIVINGLOCATIONTIMEZONE
public static final OutbDeliveryHeaderField<LocalDateTime> ACTUAL_GOODS_MOVEMENT_DATE
public static final OutbDeliveryHeaderField<LocalTime> ACTUAL_GOODS_MOVEMENT_TIME
public static final OutbDeliveryHeaderField<LocalDateTime> BILLING_DOCUMENT_DATE
public static final OutbDeliveryHeaderField<String> BILL_OF_LADING
public static final OutbDeliveryHeaderField<Boolean> COMPLETE_DELIVERY_IS_DEFINED
public static final OutbDeliveryHeaderField<LocalTime> CONFIRMATION_TIME
public static final OutbDeliveryHeaderField<String> CREATED_BY_USER
public static final OutbDeliveryHeaderField<LocalDateTime> CREATION_DATE
public static final OutbDeliveryHeaderField<LocalTime> CREATION_TIME
public static final OutbDeliveryHeaderField<String> CUSTOMER_GROUP
public static final OutbDeliveryHeaderField<String> DELIVERY_BLOCK_REASON
public static final OutbDeliveryHeaderField<LocalDateTime> DELIVERY_DATE
public static final OutbDeliveryHeaderField<String> DELIVERY_DOCUMENT
public static final OutbDeliveryHeaderField<String> DELIVERY_DOCUMENT_BY_SUPPLIER
public static final OutbDeliveryHeaderField<String> DELIVERY_DOCUMENT_TYPE
public static final OutbDeliveryHeaderField<Boolean> DELIVERY_IS_IN_PLANT
public static final OutbDeliveryHeaderField<String> DELIVERY_PRIORITY
public static final OutbDeliveryHeaderField<LocalTime> DELIVERY_TIME
public static final OutbDeliveryHeaderField<String> DELIVERY_VERSION
public static final OutbDeliveryHeaderField<BigDecimal> DEPRECIATION_PERCENTAGE
public static final OutbDeliveryHeaderField<String> DISTR_STATUS_BY_DECENTRALIZED_WRHS
public static final OutbDeliveryHeaderField<LocalDateTime> DOCUMENT_DATE
public static final OutbDeliveryHeaderField<String> EXTERNAL_IDENTIFICATION_TYPE
public static final OutbDeliveryHeaderField<String> EXTERNAL_TRANSPORT_SYSTEM
public static final OutbDeliveryHeaderField<String> FACTORY_CALENDAR_BY_CUSTOMER
public static final OutbDeliveryHeaderField<String> GOODS_ISSUE_OR_RECEIPT_SLIP_NUMBER
public static final OutbDeliveryHeaderField<LocalTime> GOODS_ISSUE_TIME
public static final OutbDeliveryHeaderField<String> HANDLING_UNIT_IN_STOCK
public static final OutbDeliveryHeaderField<String> HDR_GENERAL_INCOMPLETION_STATUS
public static final OutbDeliveryHeaderField<String> HDR_GOODS_MVT_INCOMPLETION_STATUS
public static final OutbDeliveryHeaderField<String> HEADER_BILLG_INCOMPLETION_STATUS
public static final OutbDeliveryHeaderField<String> HEADER_BILLING_BLOCK_REASON
public static final OutbDeliveryHeaderField<String> HEADER_DELIV_INCOMPLETION_STATUS
public static final OutbDeliveryHeaderField<BigDecimal> HEADER_GROSS_WEIGHT
public static final OutbDeliveryHeaderField<BigDecimal> HEADER_NET_WEIGHT
public static final OutbDeliveryHeaderField<String> HEADER_PACKING_INCOMPLETION_STS
public static final OutbDeliveryHeaderField<String> HEADER_PICKG_INCOMPLETION_STATUS
public static final OutbDeliveryHeaderField<BigDecimal> HEADER_VOLUME
public static final OutbDeliveryHeaderField<String> HEADER_VOLUME_UNIT
public static final OutbDeliveryHeaderField<String> HEADER_WEIGHT_UNIT
public static final OutbDeliveryHeaderField<String> INCOTERMS_CLASSIFICATION
public static final OutbDeliveryHeaderField<String> INCOTERMS_TRANSFER_LOCATION
public static final OutbDeliveryHeaderField<LocalDateTime> INTERCOMPANY_BILLING_DATE
public static final OutbDeliveryHeaderField<String> INTERNAL_FINANCIAL_DOCUMENT
public static final OutbDeliveryHeaderField<String> IS_DELIVERY_FOR_SINGLE_WAREHOUSE
public static final OutbDeliveryHeaderField<String> IS_EXPORT_DELIVERY
public static final OutbDeliveryHeaderField<LocalDateTime> LAST_CHANGE_DATE
public static final OutbDeliveryHeaderField<String> LAST_CHANGED_BY_USER
public static final OutbDeliveryHeaderField<LocalDateTime> LOADING_DATE
public static final OutbDeliveryHeaderField<String> LOADING_POINT
public static final OutbDeliveryHeaderField<LocalTime> LOADING_TIME
public static final OutbDeliveryHeaderField<String> MEANS_OF_TRANSPORT
public static final OutbDeliveryHeaderField<String> MEANS_OF_TRANSPORT_REF_MATERIAL
public static final OutbDeliveryHeaderField<String> MEANS_OF_TRANSPORT_TYPE
public static final OutbDeliveryHeaderField<Boolean> ORDER_COMBINATION_IS_ALLOWED
public static final OutbDeliveryHeaderField<String> ORDER_ID
public static final OutbDeliveryHeaderField<String> OVERALL_DELIV_CONF_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_DELIV_RELTD_BILLG_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_GOODS_MOVEMENT_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_INTCO_BILLING_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_PACKING_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_PICKING_CONF_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_PICKING_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_PROOF_OF_DELIVERY_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_SD_PROCESS_STATUS
public static final OutbDeliveryHeaderField<String> OVERALL_WAREHOUSE_ACTIVITY_STATUS
public static final OutbDeliveryHeaderField<String> OVRL_ITM_DELIV_INCOMPLETION_STS
public static final OutbDeliveryHeaderField<String> OVRL_ITM_GDS_MVT_INCOMPLETION_STS
public static final OutbDeliveryHeaderField<String> OVRL_ITM_GENERAL_INCOMPLETION_STS
public static final OutbDeliveryHeaderField<String> OVRL_ITM_PACKING_INCOMPLETION_STS
public static final OutbDeliveryHeaderField<String> OVRL_ITM_PICKING_INCOMPLETION_STS
public static final OutbDeliveryHeaderField<String> PAYMENT_GUARANTEE_PROCEDURE
public static final OutbDeliveryHeaderField<String> PICKED_ITEMS_LOCATION
public static final OutbDeliveryHeaderField<LocalDateTime> PICKING_DATE
public static final OutbDeliveryHeaderField<LocalTime> PICKING_TIME
public static final OutbDeliveryHeaderField<LocalDateTime> PLANNED_GOODS_ISSUE_DATE
public static final OutbDeliveryHeaderField<LocalDateTime> PROOF_OF_DELIVERY_DATE
public static final OutbDeliveryHeaderField<String> PROPOSED_DELIVERY_ROUTE
public static final OutbDeliveryHeaderField<String> RECEIVING_PLANT
public static final OutbDeliveryHeaderField<String> ROUTE_SCHEDULE
public static final OutbDeliveryHeaderField<String> SALES_DISTRICT
public static final OutbDeliveryHeaderField<String> SALES_OFFICE
public static final OutbDeliveryHeaderField<String> SALES_ORGANIZATION
public static final OutbDeliveryHeaderField<String> SD_DOCUMENT_CATEGORY
public static final OutbDeliveryHeaderField<String> SHIPMENT_BLOCK_REASON
public static final OutbDeliveryHeaderField<String> SHIPPING_CONDITION
public static final OutbDeliveryHeaderField<String> SHIPPING_POINT
public static final OutbDeliveryHeaderField<String> SHIPPING_TYPE
public static final OutbDeliveryHeaderField<String> SHIP_TO_PARTY
public static final OutbDeliveryHeaderField<String> SOLD_TO_PARTY
public static final OutbDeliveryHeaderField<String> SPECIAL_PROCESSING_CODE
public static final OutbDeliveryHeaderField<String> STATISTICS_CURRENCY
public static final OutbDeliveryHeaderField<String> SUPPLIER
public static final OutbDeliveryHeaderField<String> TOTAL_BLOCK_STATUS
public static final OutbDeliveryHeaderField<String> TOTAL_CREDIT_CHECK_STATUS
public static final OutbDeliveryHeaderField<String> TOTAL_NUMBER_OF_PACKAGE
public static final OutbDeliveryHeaderField<String> TRANSACTION_CURRENCY
public static final OutbDeliveryHeaderField<String> TRANSPORTATION_GROUP
public static final OutbDeliveryHeaderField<LocalDateTime> TRANSPORTATION_PLANNING_DATE
public static final OutbDeliveryHeaderField<String> TRANSPORTATION_PLANNING_STATUS
public static final OutbDeliveryHeaderField<LocalTime> TRANSPORTATION_PLANNING_TIME
public static final OutbDeliveryHeaderField<String> UNLOADING_POINT_NAME
public static final OutbDeliveryHeaderField<String> WAREHOUSE
public static final OutbDeliveryHeaderField<String> WAREHOUSE_GATE
public static final OutbDeliveryHeaderField<String> WAREHOUSE_STAGING_AREA
public static final OutbDeliveryHeaderLink<OutbDeliveryPartner> TO_DELIVERY_DOCUMENT_PARTNER
public static final OutbDeliveryHeaderLink<OutbDeliveryItem> TO_DELIVERY_DOCUMENT_ITEM
public OutbDeliveryHeader()
public OutbDeliveryHeader(@Nullable String actualDeliveryRoute, @Nullable String shippinglocationtimezone, @Nullable String receivinglocationtimezone, @Nullable LocalDateTime actualGoodsMovementDate, @Nullable LocalTime actualGoodsMovementTime, @Nullable LocalDateTime billingDocumentDate, @Nullable String billOfLading, @Nullable Boolean completeDeliveryIsDefined, @Nullable LocalTime confirmationTime, @Nullable String createdByUser, @Nullable LocalDateTime creationDate, @Nullable LocalTime creationTime, @Nullable String customerGroup, @Nullable String deliveryBlockReason, @Nullable LocalDateTime deliveryDate, @Nullable String deliveryDocument, @Nullable String deliveryDocumentBySupplier, @Nullable String deliveryDocumentType, @Nullable Boolean deliveryIsInPlant, @Nullable String deliveryPriority, @Nullable LocalTime deliveryTime, @Nullable String deliveryVersion, @Nullable BigDecimal depreciationPercentage, @Nullable String distrStatusByDecentralizedWrhs, @Nullable LocalDateTime documentDate, @Nullable String externalIdentificationType, @Nullable String externalTransportSystem, @Nullable String factoryCalendarByCustomer, @Nullable String goodsIssueOrReceiptSlipNumber, @Nullable LocalTime goodsIssueTime, @Nullable String handlingUnitInStock, @Nullable String hdrGeneralIncompletionStatus, @Nullable String hdrGoodsMvtIncompletionStatus, @Nullable String headerBillgIncompletionStatus, @Nullable String headerBillingBlockReason, @Nullable String headerDelivIncompletionStatus, @Nullable BigDecimal headerGrossWeight, @Nullable BigDecimal headerNetWeight, @Nullable String headerPackingIncompletionSts, @Nullable String headerPickgIncompletionStatus, @Nullable BigDecimal headerVolume, @Nullable String headerVolumeUnit, @Nullable String headerWeightUnit, @Nullable String incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable LocalDateTime intercompanyBillingDate, @Nullable String internalFinancialDocument, @Nullable String isDeliveryForSingleWarehouse, @Nullable String isExportDelivery, @Nullable LocalDateTime lastChangeDate, @Nullable String lastChangedByUser, @Nullable LocalDateTime loadingDate, @Nullable String loadingPoint, @Nullable LocalTime loadingTime, @Nullable String meansOfTransport, @Nullable String meansOfTransportRefMaterial, @Nullable String meansOfTransportType, @Nullable Boolean orderCombinationIsAllowed, @Nullable String orderID, @Nullable String overallDelivConfStatus, @Nullable String overallDelivReltdBillgStatus, @Nullable String overallGoodsMovementStatus, @Nullable String overallIntcoBillingStatus, @Nullable String overallPackingStatus, @Nullable String overallPickingConfStatus, @Nullable String overallPickingStatus, @Nullable String overallProofOfDeliveryStatus, @Nullable String overallSDProcessStatus, @Nullable String overallWarehouseActivityStatus, @Nullable String ovrlItmDelivIncompletionSts, @Nullable String ovrlItmGdsMvtIncompletionSts, @Nullable String ovrlItmGeneralIncompletionSts, @Nullable String ovrlItmPackingIncompletionSts, @Nullable String ovrlItmPickingIncompletionSts, @Nullable String paymentGuaranteeProcedure, @Nullable String pickedItemsLocation, @Nullable LocalDateTime pickingDate, @Nullable LocalTime pickingTime, @Nullable LocalDateTime plannedGoodsIssueDate, @Nullable LocalDateTime proofOfDeliveryDate, @Nullable String proposedDeliveryRoute, @Nullable String receivingPlant, @Nullable String routeSchedule, @Nullable String salesDistrict, @Nullable String salesOffice, @Nullable String salesOrganization, @Nullable String sDDocumentCategory, @Nullable String shipmentBlockReason, @Nullable String shippingCondition, @Nullable String shippingPoint, @Nullable String shippingType, @Nullable String shipToParty, @Nullable String soldToParty, @Nullable String specialProcessingCode, @Nullable String statisticsCurrency, @Nullable String supplier, @Nullable String totalBlockStatus, @Nullable String totalCreditCheckStatus, @Nullable String totalNumberOfPackage, @Nullable String transactionCurrency, @Nullable String transportationGroup, @Nullable LocalDateTime transportationPlanningDate, @Nullable String transportationPlanningStatus, @Nullable LocalTime transportationPlanningTime, @Nullable String unloadingPointName, @Nullable String warehouse, @Nullable String warehouseGate, @Nullable String warehouseStagingArea, List<OutbDeliveryPartner> toDeliveryDocumentPartner, List<OutbDeliveryItem> toDeliveryDocumentItem)
@Nonnull public Class<OutbDeliveryHeader> getType()
getType in class VdmObject<OutbDeliveryHeader>public void setActualDeliveryRoute(@Nullable String actualDeliveryRoute)
Original property name from the Odata EDM: ActualDeliveryRoute
One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document.
actualDeliveryRoute - Route by which the delivery item is to be delivered to the customer. You can use the route in a
delivery to represent the following situations:public void setShippinglocationtimezone(@Nullable String shippinglocationtimezone)
Original property name from the Odata EDM: Shippinglocationtimezone
shippinglocationtimezone - Time zone of delivering locationpublic void setReceivinglocationtimezone(@Nullable String receivinglocationtimezone)
Original property name from the Odata EDM: Receivinglocationtimezone
receivinglocationtimezone - Time zone of recipient locationpublic void setActualGoodsMovementDate(@Nullable LocalDateTime actualGoodsMovementDate)
Original property name from the Odata EDM: ActualGoodsMovementDate
If the goods movement date is not filled in, the system automatically uses the current date.The posting date for the material document is filled using the actual goods movement date. The document date shown on the material document is the current date.
actualGoodsMovementDate - You can preset the posting date for goods movement with the actual goods movement date. For example,
if the posting should occur in a previous period or month, you can do so with this default.public void setActualGoodsMovementTime(@Nullable LocalTime actualGoodsMovementTime)
Original property name from the Odata EDM: ActualGoodsMovementTime
actualGoodsMovementTime - Time of Goods Issue (Local, Relating to a Plant)public void setBillingDocumentDate(@Nullable LocalDateTime billingDocumentDate)
Original property name from the Odata EDM: BillingDocumentDate
You can use the billing date as one of the selection criteria when you process billing documents collectively.If invoice dates are defined for the customer, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date.If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document.If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone.In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
billingDocumentDate - The date on which the billing is processed and booked for accounting purposes.public void setBillOfLading(@Nullable String billOfLading)
Original property name from the Odata EDM: BillOfLading
billOfLading - Identifies the number of the bill of lading with which the goods are to be transported.public void setCompleteDeliveryIsDefined(@Nullable Boolean completeDeliveryIsDefined)
Original property name from the Odata EDM: CompleteDeliveryIsDefined
completeDeliveryIsDefined - Indicates whether a sales order must be delivered completely in a single delivery or whether the order
can be partially delivered and completed over a number of deliveries.public void setConfirmationTime(@Nullable LocalTime confirmationTime)
Original property name from the Odata EDM: ConfirmationTime
The POD confirmation time is the same as the POD verification time if the ship-to party verifies the receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.
confirmationTime - Time at which the proof of delivery (POD) is confirmed for a delivery.public void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser - Name of Person Who Created Objectpublic void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate - Date on Which Record Was Createdpublic void setCreationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
creationTime - The time of day at which the document was posted and stored in the system.public void setCustomerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
customerGroup - Identifies a particular group of customers (for example, wholesale or retail) for the purpose of
pricing or generating statistics.public void setDeliveryBlockReason(@Nullable String deliveryBlockReason)
Original property name from the Odata EDM: DeliveryBlockReason
The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
deliveryBlockReason - Indicates if an entire sales document (a sales order, for example) is blocked for delivery.public void setDeliveryDate(@Nullable LocalDateTime deliveryDate)
Original property name from the Odata EDM: DeliveryDate
The system can use predefined time estimates to calculate the delivery date for goods issue. The estimates take into account the time needed for the following activities:Arranging transportationPicking and loading the goodsTransporting the delivery from your warehouse to the customerYou can change the date manually during delivery processing.
deliveryDate - The date by which the delivery should be received by the customer.public void setDeliveryDocument(@Nullable String deliveryDocument)
Original property name from the Odata EDM: DeliveryDocument
deliveryDocument - The number that uniquely identifies the delivery.public void setDeliveryDocumentBySupplier(@Nullable String deliveryDocumentBySupplier)
Original property name from the Odata EDM: DeliveryDocumentBySupplier
When you create an inbound delivery manually or when the supplier creates a notification (per EDI), the external identification number can have a maximum of 35 characters.Please note:Only 16 reference characters are used for invoice verification. Therefore, we recommend that you use no more than 16 characters in the external identification number.
deliveryDocumentBySupplier - The supplier's reference number appears in the delivery note's external identification.public void setDeliveryDocumentType(@Nullable String deliveryDocumentType)
Original property name from the Odata EDM: DeliveryDocumentType
The delivery type determines how the system processes a delivery. For example, depending on the delivery type, the system determines which screens to present and which data to request from the user.
deliveryDocumentType - A classification that distinguishes between different types of deliveries.public void setDeliveryIsInPlant(@Nullable Boolean deliveryIsInPlant)
Original property name from the Odata EDM: DeliveryIsInPlant
deliveryIsInPlant - Delivery has Status 'In Plant'public void setDeliveryPriority(@Nullable String deliveryPriority)
Original property name from the Odata EDM: DeliveryPriority
You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
deliveryPriority - The delivery priority assigned to an item.public void setDeliveryTime(@Nullable LocalTime deliveryTime)
Original property name from the Odata EDM: DeliveryTime
You can store information about the customer's goods receiving hours in the customer master record of the ship-to party. This information includes receiving hours for each working day and for each of the customer's unloading points.The system may propose an arrival time from the customer master record. If the customer allows deliveries during a certain time slot, the system proposes the earliest time in the slot. You can change the proposed time manually in the sales order.If you schedule a delivery for a Monday and the customer has receiving hours between 8am and 12am, the system proposes 8am as the earliest possible arrival time.
deliveryTime - The time at which the item should arrive at the customer site. The time is proposed for the scheduled
day of delivery.public void setDeliveryVersion(@Nullable String deliveryVersion)
Original property name from the Odata EDM: DeliveryVersion
deliveryVersion - Delivery Versionpublic void setDepreciationPercentage(@Nullable BigDecimal depreciationPercentage)
Original property name from the Odata EDM: DepreciationPercentage
In general, the financial document covers the full amount of a document, that is, 100%.In exceptional cases, business partners may agree that only part of the amount is to be covered by a corresponding financial document.This means that only part of the amount is written off against the total value of the financial document.For example, if a business transaction has been defined such that 30% of the document value is covered by credit management and the remaining amount by a corresponding letter of credit, you should enter the value 70.If you do not enter a value, or if you enter the value '0,00 %', the system uses the value '100.00 %', that is, the document value fully coverd by the assigned financial document.
depreciationPercentage - Enter the percentage of the document value that is covered by the assigned financial document and is
to be written off against the total value of the financial document.public void setDistrStatusByDecentralizedWrhs(@Nullable String distrStatusByDecentralizedWrhs)
Original property name from the Odata EDM: DistrStatusByDecentralizedWrhs
In the central system, this field may contain the following characteristics:' ': delivery is not relevant for distribution to a decentralized WM System.'A': delivery is relevant for distribution in the decentralized system. When the delivery is saved, an IDoc is created. The system then uses this IDoc to distribute the delivery in the decentralized system.'B': delivery was distributed in the decentralized system and is currently being processed there.'C': processing of the delivery in the decentralized system is complete. Any changes are confirmed in the central system.'D': The delivery is planned for distribution in the decentralized system. You can trigger distribution using the delivery monitor.'E': The delivery was subsequently split in the decentralized system. In this case, no further changes can be made to the document in the central system.'F': Change management was subsequently switched off. For example, because the central system was temporarily not available. The delivery can no longer be changed in the central system.This field may contain the following characteristics in the decentralized Warehouse Management System:'A': delivery is being processed.'C': processing of this delivery in the decentral system is complete. The delivery is confirmed in the central system via goods issue or goods receipt posting. The delivery can no longer be changed in the decentral system.'E': The delivery was split in the decentralized system. The delivery can then be changed, however, only changes to the delivery quantity are returned to the central system.'F': Change management was subsequently switched off. The delivery can only be changed in the decentralized system. Only changes to the delivery quantity are reported back to the central system.Statuses 'B' and 'D' do not occur in this system.
distrStatusByDecentralizedWrhs - This field displays the processing status of the delivery in terms of decentralized Warehouse
Management System processing. This field cannot be changed manually. Instead, the system determines
the status using delivery items' warehouse numbers and the delivery processing status.public void setDocumentDate(@Nullable LocalDateTime documentDate)
Original property name from the Odata EDM: DocumentDate
documentDate - The document date is the date on which the original document was issued.public void setExternalIdentificationType(@Nullable String externalIdentificationType)
Original property name from the Odata EDM: ExternalIdentificationType
externalIdentificationType - Type of External Identificationpublic void setExternalTransportSystem(@Nullable String externalTransportSystem)
Original property name from the Odata EDM: ExternalTransportSystem
externalTransportSystem - ID for External Transport Systempublic void setFactoryCalendarByCustomer(@Nullable String factoryCalendarByCustomer)
Original property name from the Odata EDM: FactoryCalendarByCustomer
The system proposes the factory calendar from the information about unloading points in the customer master record of the ship-to party.You cannot change the calendar during sales order and delivery processing. If you enter a date that does not comply with the specified calendar, the system gives you a warning message before you can continue.
factoryCalendarByCustomer - The factory calendar that determines the workdays for a particular unloading point at the customer
site.public void setGoodsIssueOrReceiptSlipNumber(@Nullable String goodsIssueOrReceiptSlipNumber)
Original property name from the Odata EDM: GoodsIssueOrReceiptSlipNumber
If number assignment for goods receipt/issue slips is active in the plant, you can proceed as follows:You enter a number manually.You do not enter a number. In this case, the system automatically assigns a number.NoteThis GR/GI slip number has only been designed for use in those countries (for example, Italy) whose legislation requires specification of this number for goods that leave the plant and are transported on public roads.In other countries, the material document number printed on the GR/GI slip (in the standard system) is usually sufficient. To enter external documents, you can use the field Material slip or Delivery note.
goodsIssueOrReceiptSlipNumber - Specifies a number which - in addition to the material document number - uniquely identifies a goods
receipt/issue slip. This number can be assigned both internally and externally.public void setGoodsIssueTime(@Nullable LocalTime goodsIssueTime)
Original property name from the Odata EDM: GoodsIssueTime
goodsIssueTime - Time of Goods Issue (Local, Relating to a Plant)public void setHandlingUnitInStock(@Nullable String handlingUnitInStock)
Original property name from the Odata EDM: HandlingUnitInStock
If an additional handling unit of the delivery has been placed in WM stock, goods issue cannot be posted for the delivery.
handlingUnitInStock - This field shows whether at least one handling unit in the delivery is in WM stock.public void setHdrGeneralIncompletionStatus(@Nullable String hdrGeneralIncompletionStatus)
Original property name from the Odata EDM: HdrGeneralIncompletionStatus
The status tells you if general header information is complete. You cannot copy sales documents with missing information into other sales documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
hdrGeneralIncompletionStatus - The incompletion status of general header information in the sales document. General information
includes business, shipping, and billing data.public void setHdrGoodsMvtIncompletionStatus(@Nullable String hdrGoodsMvtIncompletionStatus)
Original property name from the Odata EDM: HdrGoodsMvtIncompletionStatus
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
hdrGoodsMvtIncompletionStatus - Incomplete status of the billing-related header data in the sales document.public void setHeaderBillgIncompletionStatus(@Nullable String headerBillgIncompletionStatus)
Original property name from the Odata EDM: HeaderBillgIncompletionStatus
The status tells you if billing-related header information is complete. Incomplete sales documents cannot be billed. For example, if a sales order contains no information about terms of payment, you cannot create an invoice for it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
headerBillgIncompletionStatus - The completion status of billing-related header information in the sales document.public void setHeaderBillingBlockReason(@Nullable String headerBillingBlockReason)
Original property name from the Odata EDM: HeaderBillingBlockReason
The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
headerBillingBlockReason - Indicates if the entire sales document is blocked for billing.public void setHeaderDelivIncompletionStatus(@Nullable String headerDelivIncompletionStatus)
Original property name from the Odata EDM: HeaderDelivIncompletionStatus
The status tells you if delivery-related header information is complete. Missing information affects further processing. For example, a sales order that contains no information about Incoterms cannot be delivered.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
headerDelivIncompletionStatus - The incompletion status of delivery-related header information in the sales document.public void setHeaderGrossWeight(@Nullable BigDecimal headerGrossWeight)
Original property name from the Odata EDM: HeaderGrossWeight
The system calculates the gross weight for each item by multiplying the delivery quantity by the gross weight per sales unit from the sales order. If there is no related sales order, the system uses the gross weight from the material master record.
headerGrossWeight - The total gross weight of all items in the delivery.public void setHeaderNetWeight(@Nullable BigDecimal headerNetWeight)
Original property name from the Odata EDM: HeaderNetWeight
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.
headerNetWeight - The total net weight of all items in the delivery.public void setHeaderPackingIncompletionSts(@Nullable String headerPackingIncompletionSts)
Original property name from the Odata EDM: HeaderPackingIncompletionSts
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
headerPackingIncompletionSts - Incomplete status of the billing-related header data in the sales document.public void setHeaderPickgIncompletionStatus(@Nullable String headerPickgIncompletionStatus)
Original property name from the Odata EDM: HeaderPickgIncompletionStatus
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
headerPickgIncompletionStatus - Incomplete status of the billing-related header data in the sales document.public void setHeaderVolume(@Nullable BigDecimal headerVolume)
Original property name from the Odata EDM: HeaderVolume
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.
headerVolume - The total volume of all items in the delivery.public void setHeaderVolumeUnit(@Nullable String headerVolumeUnit)
Original property name from the Odata EDM: HeaderVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
headerVolumeUnit - Unit referring to the volume of the material.public void setHeaderWeightUnit(@Nullable String headerWeightUnit)
Original property name from the Odata EDM: HeaderWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
headerWeightUnit - Unit referring to the gross weight or net weight of the material.public void setIncotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
incotermsClassification - Commonly used trading terms that comply with the standards established by the International Chamber of
Commerce (ICC).public void setIncotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
incotermsTransferLocation - Additional information for the primary Incoterm.public void setIntercompanyBillingDate(@Nullable LocalDateTime intercompanyBillingDate)
Original property name from the Odata EDM: IntercompanyBillingDate
intercompanyBillingDate - Billing Date for Intercompany Billingpublic void setInternalFinancialDocument(@Nullable String internalFinancialDocument)
Original property name from the Odata EDM: InternalFinancialDocument
You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance.
internalFinancialDocument - Internal number of a financial document that is mapped to a trade finance transaction. The number is
assigned by the system.public void setIsDeliveryForSingleWarehouse(@Nullable String isDeliveryForSingleWarehouse)
Original property name from the Odata EDM: IsDeliveryForSingleWarehouse
on deliveries for one warehouse number.
isDeliveryForSingleWarehouse - Together with the warehouse number, this indicator provides informationpublic void setIsExportDelivery(@Nullable String isExportDelivery)
Original property name from the Odata EDM: IsExportDelivery
isExportDelivery - Indicates whether the delivery will be exported.public void setLastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
lastChangeDate - Date of Last Changepublic void setLastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
lastChangedByUser - Name of Person who Changed Objectpublic void setLoadingDate(@Nullable LocalDateTime loadingDate)
Original property name from the Odata EDM: LoadingDate
If items in the same delivery have different loading dates, the earliest date appears in the document header.The system uses predefined time estimates to calculate the loading date. The estimates take into account the following information:Shipping pointRouteLoading groupYou can change the loading date manually.
loadingDate - The date by which picking and packing must be completed so that the goods are ready for loading and
for the delivery to reach the customer on time. Any special packaging materials required for loading
must also be available by this date.public void setLoadingPoint(@Nullable String loadingPoint)
Original property name from the Odata EDM: LoadingPoint
loadingPoint - The exact physical location where the loading of a delivery item takes place (for example, the number
of a specific loading bay).public void setLoadingTime(@Nullable LocalTime loadingTime)
Original property name from the Odata EDM: LoadingTime
loadingTime - Loading Time (Local Time Relating to a Shipping Point)public void setMeansOfTransport(@Nullable String meansOfTransport)
Original property name from the Odata EDM: MeansOfTransport
You can specify the truck with which the goods are to be transported.
meansOfTransport - Classifies a shipment of goods.public void setMeansOfTransportRefMaterial(@Nullable String meansOfTransportRefMaterial)
Original property name from the Odata EDM: MeansOfTransportRefMaterial
meansOfTransportRefMaterial - The means of transport is a packaging material in the category 'means of transport' or 'transport
equipment'.public void setMeansOfTransportType(@Nullable String meansOfTransportType)
Original property name from the Odata EDM: MeansOfTransportType
This key identifies the means of transport type. The means of transport type is a packaging material type in the category 'means of transport' or 'transport equipment'.All available trucks are assigned to the means of transport type LKW.Available ships of means of transport type ship.If the goods are to be transported by road, enter the means of transport type LKW.
meansOfTransportType - Key which specifies how the goods are transported.public void setOrderCombinationIsAllowed(@Nullable Boolean orderCombinationIsAllowed)
Original property name from the Odata EDM: OrderCombinationIsAllowed
The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.
orderCombinationIsAllowed - Indicates whether you are allowed to combine orders during delivery processing.public void setOrderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
orderID - Key that uniquely identifies an order within a client.public void setOverallDelivConfStatus(@Nullable String overallDelivConfStatus)
Original property name from the Odata EDM: OverallDelivConfStatus
The system confirms delivery for each schedule line after checking availability. The confirmation means that the system is able to confirm that a quantity is available for delivery on a certain day. The confirmation does not reflect when the goods are shipped to or received by the customer.
overallDelivConfStatus - Represents the combined delivery confirmation status of all items in the sales document.public void setOverallDelivReltdBillgStatus(@Nullable String overallDelivReltdBillgStatus)
Original property name from the Odata EDM: OverallDelivReltdBillgStatus
The status message tells you if the document is completely billed, partly billed, or is not relevant for billing.
overallDelivReltdBillgStatus - The billing status of the sales or delivery document.public void setOverallGoodsMovementStatus(@Nullable String overallGoodsMovementStatus)
Original property name from the Odata EDM: OverallGoodsMovementStatus
The status tells you whether the delivery has already left your warehouse, is still being processed, or whether processing has not yet begun.
overallGoodsMovementStatus - Indicates if, and to what extent, the delivery has left your premises.public void setOverallIntcoBillingStatus(@Nullable String overallIntcoBillingStatus)
Original property name from the Odata EDM: OverallIntcoBillingStatus
overallIntcoBillingStatus - Billing Totals Status for Intercompany Billingpublic void setOverallPackingStatus(@Nullable String overallPackingStatus)
Original property name from the Odata EDM: OverallPackingStatus
overallPackingStatus - The packing status indicates whether there are items that are relevant for packing and, if so, where
these items are completely or only partially packed.public void setOverallPickingConfStatus(@Nullable String overallPickingConfStatus)
Original property name from the Odata EDM: OverallPickingConfStatus
The confirmation status is only relevant if you are not using WM transfer orders for picking.
overallPickingConfStatus - The confirmation status of the outbound delivery indicates whether picking must be explicitly
confirmed for the delivery or whether picking has already been confirmed.public void setOverallPickingStatus(@Nullable String overallPickingStatus)
Original property name from the Odata EDM: OverallPickingStatus
Displays whether the delivery has been completely picked or put away, whether it is in the process of being picked/put away, or whether it has just started.
overallPickingStatus - Overall status for picking or putting away the deliverypublic void setOverallProofOfDeliveryStatus(@Nullable String overallProofOfDeliveryStatus)
Original property name from the Odata EDM: OverallProofOfDeliveryStatus
The status informs you whether the ship-to party reported a POD for this delivery:This status can have the following values:' ' Not relevant for the POD process'A' Relevant for the POD process'B' Differences were reported'C' Quantities were verified and confirmedIf all item quantities of a delivery are reported with no differences, the process is confirmed automatically. If differences are reported, the proof of delivery must be confirmed manually.
overallProofOfDeliveryStatus - Proof of delivery status (POD status) for the entire delivery.public void setOverallSDProcessStatus(@Nullable String overallSDProcessStatus)
Original property name from the Odata EDM: OverallSDProcessStatus
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
overallSDProcessStatus - The processing status of the entire sales document.public void setOverallWarehouseActivityStatus(@Nullable String overallWarehouseActivityStatus)
Original property name from the Odata EDM: OverallWarehouseActivityStatus
The status line tells you whether a transfer order for WM is required or not, and, if required, whether it is confirmed or still open for processing.
overallWarehouseActivityStatus - Displays the status of processing in the warehouse management system (WM).public void setOvrlItmDelivIncompletionSts(@Nullable String ovrlItmDelivIncompletionSts)
Original property name from the Odata EDM: OvrlItmDelivIncompletionSts
If shipping-related item information is missing from the sales order, the system marks the status as incomplete. You cannot ship an item that has incomplete shipping information. For example, if an item contains no information about a shipping point, you cannot ship it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
ovrlItmDelivIncompletionSts - The incompletion status of shipping-related item information in the sales document.public void setOvrlItmGdsMvtIncompletionSts(@Nullable String ovrlItmGdsMvtIncompletionSts)
Original property name from the Odata EDM: OvrlItmGdsMvtIncompletionSts
If shipping-related item data from the sales order is missing, the system sets the status to incomplete. An item with incomplete shipping data cannot be transmitted. If an item does not, for example, contain any specifications on the shipping point, you cannot transmit it.If you attempt to save a document where data is missing, the system will point out that the document is incomplete. You can then call up a list of the fields with missing specifications and complete them. However, you can also save the incomplete document and supply the missing data at a later time.
ovrlItmGdsMvtIncompletionSts - Incompletion status of item data in the sales document that affects shipping.public void setOvrlItmGeneralIncompletionSts(@Nullable String ovrlItmGeneralIncompletionSts)
Original property name from the Odata EDM: OvrlItmGeneralIncompletionSts
The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
ovrlItmGeneralIncompletionSts - The incompletion status of general item information in the sales document. General item information
includes business, shipping, and billing data.public void setOvrlItmPackingIncompletionSts(@Nullable String ovrlItmPackingIncompletionSts)
Original property name from the Odata EDM: OvrlItmPackingIncompletionSts
If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
ovrlItmPackingIncompletionSts - Incomplete status of the item data in the sales document that is relevant for shipping.public void setOvrlItmPickingIncompletionSts(@Nullable String ovrlItmPickingIncompletionSts)
Original property name from the Odata EDM: OvrlItmPickingIncompletionSts
If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
ovrlItmPickingIncompletionSts - Incomplete status of the item data in the sales document that is relevant for shipping.public void setPaymentGuaranteeProcedure(@Nullable String paymentGuaranteeProcedure)
Original property name from the Odata EDM: PaymentGuaranteeProcedure
In risk management for receivables, depending on payment guarantee category, the system accesses the form of payment guarantee using the following rules:Payment cards are activated once you have specified a payment card in the documentDocumentary payment guarantees are immediately activedExternal export credit insurance is activated once a valid contract is available.
paymentGuaranteeProcedure - Contains the permitted forms of payment guarantee for the payer and document type. Controls the
sequence in which the system assigns forms of payment guarantee to sales document items.public void setPickedItemsLocation(@Nullable String pickedItemsLocation)
Original property name from the Odata EDM: PickedItemsLocation
If your warehouse procedures require it, you can arrange for picked items to be assembled in boxes, trays, or bins in the loading area, prior to packing and loading. The location you specify in this field appears on the picking list.
pickedItemsLocation - Identifies the specific location in the loading area where, after picking, an item is assembled for
packing and loading.public void setPickingDate(@Nullable LocalDateTime pickingDate)
Original property name from the Odata EDM: PickingDate
If the items in a delivery have different picking dates, the system displays the earliest picking date in the delivery document header. You can use the picking date as a selection criterion for processing picking lists.Picking can only begin when the goods are available. The picking date therefore depends on the material availability date.
pickingDate - The date by which picking must begin for the delivery item to reach the customer on time.public void setPickingTime(@Nullable LocalTime pickingTime)
Original property name from the Odata EDM: PickingTime
If the items in a delivery do not all have the same picking date, the system displays the earliest picking date in the delivery document header. You can use the picking data as a selection criterion for processing picking lists.Picking cannot begin until the goods are available. This means that the picking date depends on the material availability date.
pickingTime - Date on which picking must begin in order for the delivery item to reach the customer in time.public void setPlannedGoodsIssueDate(@Nullable LocalDateTime plannedGoodsIssueDate)
Original property name from the Odata EDM: PlannedGoodsIssueDate
When the goods physically leave the shipping point, the system automatically creates a goods issue document to account for the outgoing inventory. The bill that you subsequently send to the customer must correspond to the movement of inventory. The goods issue date enables the accounting department to relate the movement of goods to the bill.The system automatically calculates the goods issue date by taking into account the following factors:The requested delivery dateThe pick/pack timeThe loading timeThe transit timeYou can change the date manually during delivery processing.
plannedGoodsIssueDate - The date on which the goods must physically leave the shipping point to reach the customer on time.public void setProofOfDeliveryDate(@Nullable LocalDateTime proofOfDeliveryDate)
Original property name from the Odata EDM: ProofOfDeliveryDate
The POD date is the same as the verification date if the ship-to party verifies receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.However, if differences are reported, the POD date is set when manual confirmation occurs.
proofOfDeliveryDate - Date when the proof of delivery (POD) was confirmed for a delivery.public void setProposedDeliveryRoute(@Nullable String proposedDeliveryRoute)
Original property name from the Odata EDM: ProposedDeliveryRoute
One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document.
proposedDeliveryRoute - Route by which the delivery item is to be delivered to the customer. You can use the route in a
delivery to represent the following situations:public void setReceivingPlant(@Nullable String receivingPlant)
Original property name from the Odata EDM: ReceivingPlant
How this field is filled and interpreted depends on the document category/delivery type. You can distinguish between the following cases:Delivery from stock transport orderRecipient of the delivery/ordering plant from the stock transportorderShipping notificationThe shipping notification may refer to several recipients. In thiscase, the field is empty.Rough goods receiptPlant for which you create the rough goods issue.For the remaining deliveries, the field contains the customer's plant number, provided that this customer has been maintained.
receivingPlant - Receiving plant (for customer number) for a delivery.public void setRouteSchedule(@Nullable String routeSchedule)
Original property name from the Odata EDM: RouteSchedule
You can use a route schedule to determine the day (Monday through Sunday) and the time when a customer delivery leaves the shipping point.You can define different route schedules in the system. The system can automatically propose a route schedule depending on the following criteria:the shipping point from which the delivery is sentthe ship-to party and the unloading point to which the delivery is sentthe transportation group of the deliverythe shipping condition of the deliverythe calender week in which the delivery leaves the shipping pointIn addition, you can use route schedules to create work packages from deliveries that are collectively processed in shipping, for example by using Process delivery in the picking transaction.
routeSchedule - Planning of weekly customer deliveries from one shipping point to different ship-to parties and their
unloading points in one route.public void setSalesDistrict(@Nullable String salesDistrict)
Original property name from the Odata EDM: SalesDistrict
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
salesDistrict - A geographical sales district or region.public void setSalesOffice(@Nullable String salesOffice)
Original property name from the Odata EDM: 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 - A physical location (for example, a branch office) that has responsibility for the sale of certain
products or services within a given geographical area.public void setSalesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
salesOrganization - An organizational unit responsible for the sale of certain products or services. The responsibility of
a sales organization may include legal liability for products and customer claims.public void setSDDocumentCategory(@Nullable String sDDocumentCategory)
Original property name from the Odata EDM: 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 - A classification for the different types of documents that you can process in the sales and
distribution system (for example: quotations, sales orders, deliveries, and invoices).public void setShipmentBlockReason(@Nullable String shipmentBlockReason)
Original property name from the Odata EDM: ShipmentBlockReason
Deliveries for which as shipment blocking reason has been entered are not selected during a transportation planning run.You can enter a shipment blocking reason in the delivery. When you create a delivery, a shipment blocking reason is proposed on the basis of the delivery type.A delivery can be blocked for transportation planning until a quality control check has been performed.Returns should always be blocked for transportation planning.
shipmentBlockReason - Indicates the reason why the delivery is blocked for transportation planning.public void setShippingCondition(@Nullable String shippingCondition)
Original property name from the Odata EDM: ShippingCondition
You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
shippingCondition - General shipping strategy for the delivery of goods from the vendor to the customer.public void setShippingPoint(@Nullable String shippingPoint)
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.
shippingPoint - The physical location (for example, a warehouse or collection of loading ramps) from which you ship
the item.public void setShippingType(@Nullable String shippingType)
Original property name from the Odata EDM: ShippingType
During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
shippingType - Shipping type (for example, by road or rail) that has been selected for the transportation of the
goods for the shipment legs.public void setShipToParty(@Nullable String shipToParty)
Original property name from the Odata EDM: ShipToParty
shipToParty - The party who receives delivery of the goods.public void setSoldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
soldToParty - The customer who orders the goods or services. The sold-to party is contractually responsible for
sales orders.public void setSpecialProcessingCode(@Nullable String specialProcessingCode)
Original property name from the Odata EDM: SpecialProcessingCode
You can search for the indicator using a matchcode and enter the selection data for the field.By setting the status "planned", the special processing indicator is copied from the respective deliveries into the shipment header, provided:the special processing indicator is the same in all deliveriesthe special processing indicator is not already filled in the shipment header
specialProcessingCode - Indicator that results in a special processing form for a shipment or a special calculation form for
shipment costs. Examples for special processing are express shipments or special tariffs.public void setStatisticsCurrency(@Nullable String statisticsCurrency)
Original property name from the Odata EDM: StatisticsCurrency
statisticsCurrency - Statistics Currencypublic void setSupplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
supplier - Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.public void setTotalBlockStatus(@Nullable String totalBlockStatus)
Original property name from the Odata EDM: TotalBlockStatus
The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
totalBlockStatus - Overall blocked status.public void setTotalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
totalCreditCheckStatus - Overall Status of Credit Checkspublic void setTotalNumberOfPackage(@Nullable String totalNumberOfPackage)
Original property name from the Odata EDM: TotalNumberOfPackage
The system determines the number of packages. It considers only packages at the highest level, i.e. packages that are not packed into another package.
totalNumberOfPackage - The total number of packages for all items in the delivery.public void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency - The currency that applies to the document (for example, to a sales order or an invoice).public void setTransportationGroup(@Nullable String transportationGroup)
Original property name from the Odata EDM: 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 - A grouping of materials that share the same route and transportation requirements.public void setTransportationPlanningDate(@Nullable LocalDateTime transportationPlanningDate)
Original property name from the Odata EDM: TransportationPlanningDate
The system can propose the transportation scheduling date from predefined time estimates. Estimates may be based on the route. If items in a delivery have different transportation scheduling dates, the system displays the earliest date in the document header. You can change the date manually.If, for example, you plan to use an external carrier for trucking, you must arrange for a truck to be available when the goods are ready for loading.
transportationPlanningDate - The date by which you must arrange transportation so that the delivery can reach the customer on time.public void setTransportationPlanningStatus(@Nullable String transportationPlanningStatus)
Original property name from the Odata EDM: TransportationPlanningStatus
This characteristic controls the selection of deliveries to make up shipments in transportation planning. It is used a selection criterion for finding deliveries.The indicator is set by the system on the basis of the leg indicator (preliminary, subsequent, direct, return) in the headers of the shipment documents to which the delivery has been assigned.Blank - Not relevantDelivery is not to be processed in transportationplanning. This is the case when:- the delivery type is not relevant for transportation, or- the route is not relevant for transportation (only foroutbound deliveries; not required forinbound deliveries), or- a shipment block has been set in the delivery (only foroutbound deliveries: not required for inbound deliveries)A - Not yet plannedDelivery is to be processed in transportation planning.It has not yet been assigned to a shipment document.B - Partially plannedDelivery is to be processed in transportationplanning. The delivery has already beenassigned to at least one shipment document but thetransportation chain is not complete (see status C).C - Completely plannedDelivery has been assigned to one or moreshipment documents in transportation planning. Dependingon the leg indicator in each shipment header, the delivery isconsidered to be completely planned if- it exists in a direct leg or a return leg or- it exists in a preliminary, main, subsequent leg or- each stage assigned to the delivery connects to asubsequent stage, thus connecting the pointof departure with the destination of the delivery withno gaps in transportation (as of Release 4.6A).
transportationPlanningStatus - Indicates the extent to which transportation planning has been performed.public void setTransportationPlanningTime(@Nullable LocalTime transportationPlanningTime)
Original property name from the Odata EDM: TransportationPlanningTime
transportationPlanningTime - Transp. Planning Time (Local, Relating to a Shipping Point)public void setUnloadingPointName(@Nullable String unloadingPointName)
Original property name from the Odata EDM: UnloadingPointName
unloadingPointName - Specifies the point at which the material is to be unloaded (for example, ramp 1).public void setWarehouse(@Nullable String warehouse)
Original property name from the Odata EDM: Warehouse
All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
warehouse - Number that identifies a complex, physical warehouse structure within the Warehouse Management system.public void setWarehouseGate(@Nullable String warehouseGate)
Original property name from the Odata EDM: WarehouseGate
Doors can be defined for different purposes (both at the same and different times):for goods issuefor goods receiptfor cross docking processesfor flow-throughs
warehouseGate - Organizational unit that belongs underneath a warehouse.public void setWarehouseStagingArea(@Nullable String warehouseStagingArea)
Original property name from the Odata EDM: WarehouseStagingArea
Staging areas can be used for different purposes (at the same time, if necessary):o Goods issueo Goods receipto Cross-docking processeso Direct distribution
warehouseStagingArea - Organizational unit that is on a hierarchical level below a warehouse.protected String getEntityCollection()
getEntityCollection in class VdmEntity<OutbDeliveryHeader>@Nonnull protected Map<String,Object> getKey()
getKey in class VdmObject<OutbDeliveryHeader>@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields in class VdmObject<OutbDeliveryHeader>protected void fromMap(Map<String,Object> inputValues)
fromMap in class VdmObject<OutbDeliveryHeader>@Nonnull public static <T> OutbDeliveryHeaderField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T - The type of the extension field when performing value comparisons.fieldName - The name of the extension field as returned by the OData service.fieldType - The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> OutbDeliveryHeaderField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T - The type of the extension field when performing value comparisons.DomainT - The type of the extension field as returned by the OData service.typeConverter - A TypeConverterfieldName - The name of the extension field as returned by the OData service.@Nullable public ErpConfigContext getErpConfigContext()
VdmEntitygetErpConfigContext in class VdmEntity<OutbDeliveryHeader>@Deprecated public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
attachToService(String, ErpConfigContext) instead.VdmEntitysetErpConfigContext in class VdmEntity<OutbDeliveryHeader>erpConfigContext - New ERP configuration context to apply to this entityprotected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntityNote: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch in class VdmEntity<OutbDeliveryHeader>public void attachToService(@Nullable String servicePath, @Nullable ErpConfigContext configContext)
VdmEntityNote: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService in class VdmEntity<OutbDeliveryHeader>servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.configContext - Optional parameter. New ERP configuration context to apply to this entity and any associated entities
that were previously fetched. If a null value is provided and the ERP configuration context has never
been set, then the ERP configuration context will be set to a new instance of
ErpConfigContext.protected String getDefaultServicePath()
getDefaultServicePath in class VdmEntity<OutbDeliveryHeader>@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties in class VdmObject<OutbDeliveryHeader>@Nonnull public List<OutbDeliveryPartner> fetchDeliveryDocumentPartner() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<OutbDeliveryPartner> getDeliveryDocumentPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_DeliveryDocumentPartner of a queried OutbDeliveryHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public Optional<List<OutbDeliveryPartner>> getDeliveryDocumentPartnerIfPresent()
If the navigation property for an entity OutbDeliveryHeader has not been resolved yet, this method will
not query further information. Instead its Optional result state will be empty.
Optional with result
state empty is returned.public void setDeliveryDocumentPartner(@Nonnull List<OutbDeliveryPartner> value)
If the navigation property to_DeliveryDocumentPartner of a queried OutbDeliveryHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of OutbDeliveryPartner entities.public void addDeliveryDocumentPartner(OutbDeliveryPartner... entity)
If the navigation property to_DeliveryDocumentPartner of a queried OutbDeliveryHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of OutbDeliveryPartner entities.@Nonnull public List<OutbDeliveryItem> fetchDeliveryDocumentItem() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<OutbDeliveryItem> getDeliveryDocumentItemOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_DeliveryDocumentItem of a queried OutbDeliveryHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public Optional<List<OutbDeliveryItem>> getDeliveryDocumentItemIfPresent()
If the navigation property for an entity OutbDeliveryHeader has not been resolved yet, this method will
not query further information. Instead its Optional result state will be empty.
Optional with result state
empty is returned.public void setDeliveryDocumentItem(@Nonnull List<OutbDeliveryItem> value)
If the navigation property to_DeliveryDocumentItem of a queried OutbDeliveryHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of OutbDeliveryItem entities.public void addDeliveryDocumentItem(OutbDeliveryItem... entity)
If the navigation property to_DeliveryDocumentItem of a queried OutbDeliveryHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of OutbDeliveryItem entities.public static OutbDeliveryHeader.OutbDeliveryHeaderBuilder builder()
@Nullable public String getActualDeliveryRoute()
Original property name from the Odata EDM: ActualDeliveryRoute
One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document.
@Nullable public String getShippinglocationtimezone()
Original property name from the Odata EDM: Shippinglocationtimezone
@Nullable public String getReceivinglocationtimezone()
Original property name from the Odata EDM: Receivinglocationtimezone
@Nullable public LocalDateTime getActualGoodsMovementDate()
Original property name from the Odata EDM: ActualGoodsMovementDate
If the goods movement date is not filled in, the system automatically uses the current date.The posting date for the material document is filled using the actual goods movement date. The document date shown on the material document is the current date.
@Nullable public LocalTime getActualGoodsMovementTime()
Original property name from the Odata EDM: ActualGoodsMovementTime
@Nullable public LocalDateTime getBillingDocumentDate()
Original property name from the Odata EDM: BillingDocumentDate
You can use the billing date as one of the selection criteria when you process billing documents collectively.If invoice dates are defined for the customer, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date.If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document.If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone.In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
@Nullable public String getBillOfLading()
Original property name from the Odata EDM: BillOfLading
@Nullable public Boolean getCompleteDeliveryIsDefined()
Original property name from the Odata EDM: CompleteDeliveryIsDefined
@Nullable public LocalTime getConfirmationTime()
Original property name from the Odata EDM: ConfirmationTime
The POD confirmation time is the same as the POD verification time if the ship-to party verifies the receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public LocalTime getCreationTime()
Original property name from the Odata EDM: CreationTime
@Nullable public String getCustomerGroup()
Original property name from the Odata EDM: CustomerGroup
@Nullable public String getDeliveryBlockReason()
Original property name from the Odata EDM: DeliveryBlockReason
The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
@Nullable public LocalDateTime getDeliveryDate()
Original property name from the Odata EDM: DeliveryDate
The system can use predefined time estimates to calculate the delivery date for goods issue. The estimates take into account the time needed for the following activities:Arranging transportationPicking and loading the goodsTransporting the delivery from your warehouse to the customerYou can change the date manually during delivery processing.
@Nullable public String getDeliveryDocument()
Original property name from the Odata EDM: DeliveryDocument
@Nullable public String getDeliveryDocumentBySupplier()
Original property name from the Odata EDM: DeliveryDocumentBySupplier
When you create an inbound delivery manually or when the supplier creates a notification (per EDI), the external identification number can have a maximum of 35 characters.Please note:Only 16 reference characters are used for invoice verification. Therefore, we recommend that you use no more than 16 characters in the external identification number.
@Nullable public String getDeliveryDocumentType()
Original property name from the Odata EDM: DeliveryDocumentType
The delivery type determines how the system processes a delivery. For example, depending on the delivery type, the system determines which screens to present and which data to request from the user.
@Nullable public Boolean getDeliveryIsInPlant()
Original property name from the Odata EDM: DeliveryIsInPlant
@Nullable public String getDeliveryPriority()
Original property name from the Odata EDM: DeliveryPriority
You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
@Nullable public LocalTime getDeliveryTime()
Original property name from the Odata EDM: DeliveryTime
You can store information about the customer's goods receiving hours in the customer master record of the ship-to party. This information includes receiving hours for each working day and for each of the customer's unloading points.The system may propose an arrival time from the customer master record. If the customer allows deliveries during a certain time slot, the system proposes the earliest time in the slot. You can change the proposed time manually in the sales order.If you schedule a delivery for a Monday and the customer has receiving hours between 8am and 12am, the system proposes 8am as the earliest possible arrival time.
@Nullable public String getDeliveryVersion()
Original property name from the Odata EDM: DeliveryVersion
@Nullable public BigDecimal getDepreciationPercentage()
Original property name from the Odata EDM: DepreciationPercentage
In general, the financial document covers the full amount of a document, that is, 100%.In exceptional cases, business partners may agree that only part of the amount is to be covered by a corresponding financial document.This means that only part of the amount is written off against the total value of the financial document.For example, if a business transaction has been defined such that 30% of the document value is covered by credit management and the remaining amount by a corresponding letter of credit, you should enter the value 70.If you do not enter a value, or if you enter the value '0,00 %', the system uses the value '100.00 %', that is, the document value fully coverd by the assigned financial document.
@Nullable public String getDistrStatusByDecentralizedWrhs()
Original property name from the Odata EDM: DistrStatusByDecentralizedWrhs
In the central system, this field may contain the following characteristics:' ': delivery is not relevant for distribution to a decentralized WM System.'A': delivery is relevant for distribution in the decentralized system. When the delivery is saved, an IDoc is created. The system then uses this IDoc to distribute the delivery in the decentralized system.'B': delivery was distributed in the decentralized system and is currently being processed there.'C': processing of the delivery in the decentralized system is complete. Any changes are confirmed in the central system.'D': The delivery is planned for distribution in the decentralized system. You can trigger distribution using the delivery monitor.'E': The delivery was subsequently split in the decentralized system. In this case, no further changes can be made to the document in the central system.'F': Change management was subsequently switched off. For example, because the central system was temporarily not available. The delivery can no longer be changed in the central system.This field may contain the following characteristics in the decentralized Warehouse Management System:'A': delivery is being processed.'C': processing of this delivery in the decentral system is complete. The delivery is confirmed in the central system via goods issue or goods receipt posting. The delivery can no longer be changed in the decentral system.'E': The delivery was split in the decentralized system. The delivery can then be changed, however, only changes to the delivery quantity are returned to the central system.'F': Change management was subsequently switched off. The delivery can only be changed in the decentralized system. Only changes to the delivery quantity are reported back to the central system.Statuses 'B' and 'D' do not occur in this system.
@Nullable public LocalDateTime getDocumentDate()
Original property name from the Odata EDM: DocumentDate
@Nullable public String getExternalIdentificationType()
Original property name from the Odata EDM: ExternalIdentificationType
@Nullable public String getExternalTransportSystem()
Original property name from the Odata EDM: ExternalTransportSystem
@Nullable public String getFactoryCalendarByCustomer()
Original property name from the Odata EDM: FactoryCalendarByCustomer
The system proposes the factory calendar from the information about unloading points in the customer master record of the ship-to party.You cannot change the calendar during sales order and delivery processing. If you enter a date that does not comply with the specified calendar, the system gives you a warning message before you can continue.
@Nullable public String getGoodsIssueOrReceiptSlipNumber()
Original property name from the Odata EDM: GoodsIssueOrReceiptSlipNumber
If number assignment for goods receipt/issue slips is active in the plant, you can proceed as follows:You enter a number manually.You do not enter a number. In this case, the system automatically assigns a number.NoteThis GR/GI slip number has only been designed for use in those countries (for example, Italy) whose legislation requires specification of this number for goods that leave the plant and are transported on public roads.In other countries, the material document number printed on the GR/GI slip (in the standard system) is usually sufficient. To enter external documents, you can use the field Material slip or Delivery note.
@Nullable public LocalTime getGoodsIssueTime()
Original property name from the Odata EDM: GoodsIssueTime
@Nullable public String getHandlingUnitInStock()
Original property name from the Odata EDM: HandlingUnitInStock
If an additional handling unit of the delivery has been placed in WM stock, goods issue cannot be posted for the delivery.
@Nullable public String getHdrGeneralIncompletionStatus()
Original property name from the Odata EDM: HdrGeneralIncompletionStatus
The status tells you if general header information is complete. You cannot copy sales documents with missing information into other sales documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
@Nullable public String getHdrGoodsMvtIncompletionStatus()
Original property name from the Odata EDM: HdrGoodsMvtIncompletionStatus
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
@Nullable public String getHeaderBillgIncompletionStatus()
Original property name from the Odata EDM: HeaderBillgIncompletionStatus
The status tells you if billing-related header information is complete. Incomplete sales documents cannot be billed. For example, if a sales order contains no information about terms of payment, you cannot create an invoice for it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
@Nullable public String getHeaderBillingBlockReason()
Original property name from the Odata EDM: HeaderBillingBlockReason
The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
@Nullable public String getHeaderDelivIncompletionStatus()
Original property name from the Odata EDM: HeaderDelivIncompletionStatus
The status tells you if delivery-related header information is complete. Missing information affects further processing. For example, a sales order that contains no information about Incoterms cannot be delivered.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
@Nullable public BigDecimal getHeaderGrossWeight()
Original property name from the Odata EDM: HeaderGrossWeight
The system calculates the gross weight for each item by multiplying the delivery quantity by the gross weight per sales unit from the sales order. If there is no related sales order, the system uses the gross weight from the material master record.
@Nullable public BigDecimal getHeaderNetWeight()
Original property name from the Odata EDM: HeaderNetWeight
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.
@Nullable public String getHeaderPackingIncompletionSts()
Original property name from the Odata EDM: HeaderPackingIncompletionSts
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
@Nullable public String getHeaderPickgIncompletionStatus()
Original property name from the Odata EDM: HeaderPickgIncompletionStatus
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
@Nullable public BigDecimal getHeaderVolume()
Original property name from the Odata EDM: HeaderVolume
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.
@Nullable public String getHeaderVolumeUnit()
Original property name from the Odata EDM: HeaderVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
@Nullable public String getHeaderWeightUnit()
Original property name from the Odata EDM: HeaderWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
@Nullable public String getIncotermsClassification()
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
@Nullable public String getIncotermsTransferLocation()
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
@Nullable public LocalDateTime getIntercompanyBillingDate()
Original property name from the Odata EDM: IntercompanyBillingDate
@Nullable public String getInternalFinancialDocument()
Original property name from the Odata EDM: InternalFinancialDocument
You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance.
@Nullable public String getIsDeliveryForSingleWarehouse()
Original property name from the Odata EDM: IsDeliveryForSingleWarehouse
on deliveries for one warehouse number.
@Nullable public String getIsExportDelivery()
Original property name from the Odata EDM: IsExportDelivery
@Nullable public LocalDateTime getLastChangeDate()
Original property name from the Odata EDM: LastChangeDate
@Nullable public String getLastChangedByUser()
Original property name from the Odata EDM: LastChangedByUser
@Nullable public LocalDateTime getLoadingDate()
Original property name from the Odata EDM: LoadingDate
If items in the same delivery have different loading dates, the earliest date appears in the document header.The system uses predefined time estimates to calculate the loading date. The estimates take into account the following information:Shipping pointRouteLoading groupYou can change the loading date manually.
@Nullable public String getLoadingPoint()
Original property name from the Odata EDM: LoadingPoint
@Nullable public LocalTime getLoadingTime()
Original property name from the Odata EDM: LoadingTime
@Nullable public String getMeansOfTransport()
Original property name from the Odata EDM: MeansOfTransport
You can specify the truck with which the goods are to be transported.
@Nullable public String getMeansOfTransportRefMaterial()
Original property name from the Odata EDM: MeansOfTransportRefMaterial
@Nullable public String getMeansOfTransportType()
Original property name from the Odata EDM: MeansOfTransportType
This key identifies the means of transport type. The means of transport type is a packaging material type in the category 'means of transport' or 'transport equipment'.All available trucks are assigned to the means of transport type LKW.Available ships of means of transport type ship.If the goods are to be transported by road, enter the means of transport type LKW.
@Nullable public Boolean getOrderCombinationIsAllowed()
Original property name from the Odata EDM: OrderCombinationIsAllowed
The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.
@Nullable public String getOrderID()
Original property name from the Odata EDM: OrderID
@Nullable public String getOverallDelivConfStatus()
Original property name from the Odata EDM: OverallDelivConfStatus
The system confirms delivery for each schedule line after checking availability. The confirmation means that the system is able to confirm that a quantity is available for delivery on a certain day. The confirmation does not reflect when the goods are shipped to or received by the customer.
@Nullable public String getOverallDelivReltdBillgStatus()
Original property name from the Odata EDM: OverallDelivReltdBillgStatus
The status message tells you if the document is completely billed, partly billed, or is not relevant for billing.
@Nullable public String getOverallGoodsMovementStatus()
Original property name from the Odata EDM: OverallGoodsMovementStatus
The status tells you whether the delivery has already left your warehouse, is still being processed, or whether processing has not yet begun.
@Nullable public String getOverallIntcoBillingStatus()
Original property name from the Odata EDM: OverallIntcoBillingStatus
@Nullable public String getOverallPackingStatus()
Original property name from the Odata EDM: OverallPackingStatus
@Nullable public String getOverallPickingConfStatus()
Original property name from the Odata EDM: OverallPickingConfStatus
The confirmation status is only relevant if you are not using WM transfer orders for picking.
@Nullable public String getOverallPickingStatus()
Original property name from the Odata EDM: OverallPickingStatus
Displays whether the delivery has been completely picked or put away, whether it is in the process of being picked/put away, or whether it has just started.
@Nullable public String getOverallProofOfDeliveryStatus()
Original property name from the Odata EDM: OverallProofOfDeliveryStatus
The status informs you whether the ship-to party reported a POD for this delivery:This status can have the following values:' ' Not relevant for the POD process'A' Relevant for the POD process'B' Differences were reported'C' Quantities were verified and confirmedIf all item quantities of a delivery are reported with no differences, the process is confirmed automatically. If differences are reported, the proof of delivery must be confirmed manually.
@Nullable public String getOverallSDProcessStatus()
Original property name from the Odata EDM: OverallSDProcessStatus
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
@Nullable public String getOverallWarehouseActivityStatus()
Original property name from the Odata EDM: OverallWarehouseActivityStatus
The status line tells you whether a transfer order for WM is required or not, and, if required, whether it is confirmed or still open for processing.
@Nullable public String getOvrlItmDelivIncompletionSts()
Original property name from the Odata EDM: OvrlItmDelivIncompletionSts
If shipping-related item information is missing from the sales order, the system marks the status as incomplete. You cannot ship an item that has incomplete shipping information. For example, if an item contains no information about a shipping point, you cannot ship it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
@Nullable public String getOvrlItmGdsMvtIncompletionSts()
Original property name from the Odata EDM: OvrlItmGdsMvtIncompletionSts
If shipping-related item data from the sales order is missing, the system sets the status to incomplete. An item with incomplete shipping data cannot be transmitted. If an item does not, for example, contain any specifications on the shipping point, you cannot transmit it.If you attempt to save a document where data is missing, the system will point out that the document is incomplete. You can then call up a list of the fields with missing specifications and complete them. However, you can also save the incomplete document and supply the missing data at a later time.
@Nullable public String getOvrlItmGeneralIncompletionSts()
Original property name from the Odata EDM: OvrlItmGeneralIncompletionSts
The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
@Nullable public String getOvrlItmPackingIncompletionSts()
Original property name from the Odata EDM: OvrlItmPackingIncompletionSts
If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
@Nullable public String getOvrlItmPickingIncompletionSts()
Original property name from the Odata EDM: OvrlItmPickingIncompletionSts
If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
@Nullable public String getPaymentGuaranteeProcedure()
Original property name from the Odata EDM: PaymentGuaranteeProcedure
In risk management for receivables, depending on payment guarantee category, the system accesses the form of payment guarantee using the following rules:Payment cards are activated once you have specified a payment card in the documentDocumentary payment guarantees are immediately activedExternal export credit insurance is activated once a valid contract is available.
@Nullable public String getPickedItemsLocation()
Original property name from the Odata EDM: PickedItemsLocation
If your warehouse procedures require it, you can arrange for picked items to be assembled in boxes, trays, or bins in the loading area, prior to packing and loading. The location you specify in this field appears on the picking list.
@Nullable public LocalDateTime getPickingDate()
Original property name from the Odata EDM: PickingDate
If the items in a delivery have different picking dates, the system displays the earliest picking date in the delivery document header. You can use the picking date as a selection criterion for processing picking lists.Picking can only begin when the goods are available. The picking date therefore depends on the material availability date.
@Nullable public LocalTime getPickingTime()
Original property name from the Odata EDM: PickingTime
If the items in a delivery do not all have the same picking date, the system displays the earliest picking date in the delivery document header. You can use the picking data as a selection criterion for processing picking lists.Picking cannot begin until the goods are available. This means that the picking date depends on the material availability date.
@Nullable public LocalDateTime getPlannedGoodsIssueDate()
Original property name from the Odata EDM: PlannedGoodsIssueDate
When the goods physically leave the shipping point, the system automatically creates a goods issue document to account for the outgoing inventory. The bill that you subsequently send to the customer must correspond to the movement of inventory. The goods issue date enables the accounting department to relate the movement of goods to the bill.The system automatically calculates the goods issue date by taking into account the following factors:The requested delivery dateThe pick/pack timeThe loading timeThe transit timeYou can change the date manually during delivery processing.
@Nullable public LocalDateTime getProofOfDeliveryDate()
Original property name from the Odata EDM: ProofOfDeliveryDate
The POD date is the same as the verification date if the ship-to party verifies receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.However, if differences are reported, the POD date is set when manual confirmation occurs.
@Nullable public String getProposedDeliveryRoute()
Original property name from the Odata EDM: ProposedDeliveryRoute
One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document.
@Nullable public String getReceivingPlant()
Original property name from the Odata EDM: ReceivingPlant
How this field is filled and interpreted depends on the document category/delivery type. You can distinguish between the following cases:Delivery from stock transport orderRecipient of the delivery/ordering plant from the stock transportorderShipping notificationThe shipping notification may refer to several recipients. In thiscase, the field is empty.Rough goods receiptPlant for which you create the rough goods issue.For the remaining deliveries, the field contains the customer's plant number, provided that this customer has been maintained.
@Nullable public String getRouteSchedule()
Original property name from the Odata EDM: RouteSchedule
You can use a route schedule to determine the day (Monday through Sunday) and the time when a customer delivery leaves the shipping point.You can define different route schedules in the system. The system can automatically propose a route schedule depending on the following criteria:the shipping point from which the delivery is sentthe ship-to party and the unloading point to which the delivery is sentthe transportation group of the deliverythe shipping condition of the deliverythe calender week in which the delivery leaves the shipping pointIn addition, you can use route schedules to create work packages from deliveries that are collectively processed in shipping, for example by using Process delivery in the picking transaction.
@Nullable public String getSalesDistrict()
Original property name from the Odata EDM: SalesDistrict
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
@Nullable public String getSalesOffice()
Original property name from the Odata EDM: 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.
@Nullable public String getSalesOrganization()
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
@Nullable public String getSDDocumentCategory()
Original property name from the Odata EDM: 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).
@Nullable public String getShipmentBlockReason()
Original property name from the Odata EDM: ShipmentBlockReason
Deliveries for which as shipment blocking reason has been entered are not selected during a transportation planning run.You can enter a shipment blocking reason in the delivery. When you create a delivery, a shipment blocking reason is proposed on the basis of the delivery type.A delivery can be blocked for transportation planning until a quality control check has been performed.Returns should always be blocked for transportation planning.
@Nullable public String getShippingCondition()
Original property name from the Odata EDM: ShippingCondition
You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
@Nullable public String getShippingPoint()
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.
@Nullable public String getShippingType()
Original property name from the Odata EDM: ShippingType
During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
@Nullable public String getShipToParty()
Original property name from the Odata EDM: ShipToParty
@Nullable public String getSoldToParty()
Original property name from the Odata EDM: SoldToParty
@Nullable public String getSpecialProcessingCode()
Original property name from the Odata EDM: SpecialProcessingCode
You can search for the indicator using a matchcode and enter the selection data for the field.By setting the status "planned", the special processing indicator is copied from the respective deliveries into the shipment header, provided:the special processing indicator is the same in all deliveriesthe special processing indicator is not already filled in the shipment header
@Nullable public String getStatisticsCurrency()
Original property name from the Odata EDM: StatisticsCurrency
@Nullable public String getSupplier()
Original property name from the Odata EDM: Supplier
@Nullable public String getTotalBlockStatus()
Original property name from the Odata EDM: TotalBlockStatus
The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
@Nullable public String getTotalCreditCheckStatus()
Original property name from the Odata EDM: TotalCreditCheckStatus
@Nullable public String getTotalNumberOfPackage()
Original property name from the Odata EDM: TotalNumberOfPackage
The system determines the number of packages. It considers only packages at the highest level, i.e. packages that are not packed into another package.
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable public String getTransportationGroup()
Original property name from the Odata EDM: 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.
@Nullable public LocalDateTime getTransportationPlanningDate()
Original property name from the Odata EDM: TransportationPlanningDate
The system can propose the transportation scheduling date from predefined time estimates. Estimates may be based on the route. If items in a delivery have different transportation scheduling dates, the system displays the earliest date in the document header. You can change the date manually.If, for example, you plan to use an external carrier for trucking, you must arrange for a truck to be available when the goods are ready for loading.
@Nullable public String getTransportationPlanningStatus()
Original property name from the Odata EDM: TransportationPlanningStatus
This characteristic controls the selection of deliveries to make up shipments in transportation planning. It is used a selection criterion for finding deliveries.The indicator is set by the system on the basis of the leg indicator (preliminary, subsequent, direct, return) in the headers of the shipment documents to which the delivery has been assigned.Blank - Not relevantDelivery is not to be processed in transportationplanning. This is the case when:- the delivery type is not relevant for transportation, or- the route is not relevant for transportation (only foroutbound deliveries; not required forinbound deliveries), or- a shipment block has been set in the delivery (only foroutbound deliveries: not required for inbound deliveries)A - Not yet plannedDelivery is to be processed in transportation planning.It has not yet been assigned to a shipment document.B - Partially plannedDelivery is to be processed in transportationplanning. The delivery has already beenassigned to at least one shipment document but thetransportation chain is not complete (see status C).C - Completely plannedDelivery has been assigned to one or moreshipment documents in transportation planning. Dependingon the leg indicator in each shipment header, the delivery isconsidered to be completely planned if- it exists in a direct leg or a return leg or- it exists in a preliminary, main, subsequent leg or- each stage assigned to the delivery connects to asubsequent stage, thus connecting the pointof departure with the destination of the delivery withno gaps in transportation (as of Release 4.6A).
@Nullable public LocalTime getTransportationPlanningTime()
Original property name from the Odata EDM: TransportationPlanningTime
@Nullable public String getUnloadingPointName()
Original property name from the Odata EDM: UnloadingPointName
@Nullable public String getWarehouse()
Original property name from the Odata EDM: Warehouse
All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
@Nullable public String getWarehouseGate()
Original property name from the Odata EDM: WarehouseGate
Doors can be defined for different purposes (both at the same and different times):for goods issuefor goods receiptfor cross docking processesfor flow-throughs
@Nullable public String getWarehouseStagingArea()
Original property name from the Odata EDM: WarehouseStagingArea
Staging areas can be used for different purposes (at the same time, if necessary):o Goods issueo Goods receipto Cross-docking processeso Direct distribution
public String toString()
toString in class VdmObject<OutbDeliveryHeader>public boolean equals(Object o)
equals in class VdmObject<OutbDeliveryHeader>protected boolean canEqual(Object other)
canEqual in class VdmObject<OutbDeliveryHeader>public int hashCode()
hashCode in class VdmObject<OutbDeliveryHeader>Copyright © 2019 SAP SE. All rights reserved.