public class OutbDeliveryHeader extends VdmEntity<OutbDeliveryHeader>
| Modifier and Type | Class and Description |
|---|---|
static class |
OutbDeliveryHeader.OutbDeliveryHeaderBuilder |
| 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<Calendar> |
ACTUAL_GOODS_MOVEMENT_DATE
Use with available fluent helpers to apply the ActualGoodsMovementDate field to query operations.
|
static OutbDeliveryHeaderField<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static OutbDeliveryHeaderField<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
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<Calendar> |
PICKING_DATE
Use with available fluent helpers to apply the PickingDate field to query operations.
|
static OutbDeliveryHeaderField<Calendar> |
PICKING_TIME
Use with available fluent helpers to apply the PickingTime field to query operations.
|
static OutbDeliveryHeaderField<Calendar> |
PLANNED_GOODS_ISSUE_DATE
Use with available fluent helpers to apply the PlannedGoodsIssueDate field to query operations.
|
static OutbDeliveryHeaderField<Calendar> |
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> |
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> |
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<Calendar> |
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<Calendar> |
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.
|
| Constructor and Description |
|---|
OutbDeliveryHeader() |
OutbDeliveryHeader(String actualDeliveryRoute,
Calendar actualGoodsMovementDate,
Calendar actualGoodsMovementTime,
Calendar billingDocumentDate,
String billOfLading,
Boolean completeDeliveryIsDefined,
Calendar confirmationTime,
String createdByUser,
Calendar creationDate,
Calendar creationTime,
String customerGroup,
String deliveryBlockReason,
Calendar deliveryDate,
String deliveryDocument,
String deliveryDocumentBySupplier,
String deliveryDocumentType,
Boolean deliveryIsInPlant,
String deliveryPriority,
Calendar deliveryTime,
String deliveryVersion,
BigDecimal depreciationPercentage,
String distrStatusByDecentralizedWrhs,
Calendar documentDate,
String externalIdentificationType,
String externalTransportSystem,
String factoryCalendarByCustomer,
String goodsIssueOrReceiptSlipNumber,
Calendar 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,
Calendar intercompanyBillingDate,
String internalFinancialDocument,
String isDeliveryForSingleWarehouse,
String isExportDelivery,
Calendar lastChangeDate,
String lastChangedByUser,
Calendar loadingDate,
String loadingPoint,
Calendar 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,
Calendar pickingDate,
Calendar pickingTime,
Calendar plannedGoodsIssueDate,
Calendar 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,
Calendar transportationPlanningDate,
String transportationPlanningStatus,
Calendar transportationPlanningTime,
String unloadingPointName,
String warehouse,
String warehouseGate,
String warehouseStagingArea,
ErpConfigContext erpConfigContext,
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.
|
static OutbDeliveryHeader.OutbDeliveryHeaderBuilder |
builder() |
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.
|
String |
getActualDeliveryRoute()
Constraints: Not nullable, Maximum length: 6
|
Calendar |
getActualGoodsMovementDate()
Constraints: Not nullable, Precision: 7
|
Calendar |
getActualGoodsMovementTime()
Constraints: Not nullable, Precision: 0
|
Calendar |
getBillingDocumentDate()
Constraints: Not nullable, Precision: 7
|
String |
getBillOfLading()
Constraints: Not nullable, Maximum length: 35
|
Boolean |
getCompleteDeliveryIsDefined()
Constraints: none
|
Calendar |
getConfirmationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
Calendar |
getCreationDate()
Constraints: Not nullable, Precision: 7
|
Calendar |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getDeliveryBlockReason()
Constraints: Not nullable, Maximum length: 2
|
Calendar |
getDeliveryDate()
Constraints: Not nullable, Precision: 7
|
String |
getDeliveryDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getDeliveryDocumentBySupplier()
Constraints: Not nullable, Maximum length: 35
|
List<OutbDeliveryItem> |
getDeliveryDocumentItemOrFetch()
Retrieval of associated OutbDeliveryItem entities (one to many).
|
com.google.common.base.Optional<List<OutbDeliveryItem>> |
getDeliveryDocumentItemOrNull()
Retrieval of associated OutbDeliveryItem entities (one to many).
|
List<OutbDeliveryPartner> |
getDeliveryDocumentPartnerOrFetch()
Retrieval of associated OutbDeliveryPartner entities (one to many).
|
com.google.common.base.Optional<List<OutbDeliveryPartner>> |
getDeliveryDocumentPartnerOrNull()
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
|
Calendar |
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
|
Calendar |
getDocumentDate()
Constraints: Not nullable, Precision: 7
|
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
|
Calendar |
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
|
Calendar |
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
|
Calendar |
getLastChangeDate()
Constraints: Not nullable, Precision: 7
|
String |
getLastChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
Calendar |
getLoadingDate()
Constraints: Not nullable, Precision: 7
|
String |
getLoadingPoint()
Constraints: Not nullable, Maximum length: 2
|
Calendar |
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
|
Calendar |
getPickingDate()
Constraints: Not nullable, Precision: 7
|
Calendar |
getPickingTime()
Constraints: Not nullable, Precision: 0
|
Calendar |
getPlannedGoodsIssueDate()
Constraints: Not nullable, Precision: 7
|
Calendar |
getProofOfDeliveryDate()
Constraints: Not nullable, Precision: 7
|
String |
getProposedDeliveryRoute()
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 |
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
|
Calendar |
getTransportationPlanningDate()
Constraints: Not nullable, Precision: 7
|
String |
getTransportationPlanningStatus()
Constraints: Not nullable, Maximum length: 1
|
Calendar |
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(Calendar actualGoodsMovementDate)
Constraints: Not nullable, Precision: 7
|
void |
setActualGoodsMovementTime(Calendar actualGoodsMovementTime)
Constraints: Not nullable, Precision: 0
|
void |
setBillingDocumentDate(Calendar billingDocumentDate)
Constraints: Not nullable, Precision: 7
|
void |
setBillOfLading(String billOfLading)
Constraints: Not nullable, Maximum length: 35
|
void |
setCompleteDeliveryIsDefined(Boolean completeDeliveryIsDefined)
Constraints: none
|
void |
setConfirmationTime(Calendar confirmationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(Calendar creationDate)
Constraints: Not nullable, Precision: 7
|
void |
setCreationTime(Calendar creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerGroup(String customerGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setDeliveryBlockReason(String deliveryBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setDeliveryDate(Calendar 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(Calendar 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(Calendar documentDate)
Constraints: Not nullable, Precision: 7
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
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(Calendar 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(Calendar 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(Calendar lastChangeDate)
Constraints: Not nullable, Precision: 7
|
void |
setLastChangedByUser(String lastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setLoadingDate(Calendar loadingDate)
Constraints: Not nullable, Precision: 7
|
void |
setLoadingPoint(String loadingPoint)
Constraints: Not nullable, Maximum length: 2
|
void |
setLoadingTime(Calendar 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(Calendar pickingDate)
Constraints: Not nullable, Precision: 7
|
void |
setPickingTime(Calendar pickingTime)
Constraints: Not nullable, Precision: 0
|
void |
setPlannedGoodsIssueDate(Calendar plannedGoodsIssueDate)
Constraints: Not nullable, Precision: 7
|
void |
setProofOfDeliveryDate(Calendar proofOfDeliveryDate)
Constraints: Not nullable, Precision: 7
|
void |
setProposedDeliveryRoute(String proposedDeliveryRoute)
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
|
void |
setShipmentBlockReason(String shipmentBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setShippingCondition(String shippingCondition)
Constraints: Not nullable, Maximum length: 2
|
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(Calendar transportationPlanningDate)
Constraints: Not nullable, Precision: 7
|
void |
setTransportationPlanningStatus(String transportationPlanningStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setTransportationPlanningTime(Calendar 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
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final OutbDeliveryHeaderSelectable ALL_FIELDS
public static final OutbDeliveryHeaderField<String> ACTUAL_DELIVERY_ROUTE
public static final OutbDeliveryHeaderField<Calendar> ACTUAL_GOODS_MOVEMENT_DATE
public static final OutbDeliveryHeaderField<Calendar> ACTUAL_GOODS_MOVEMENT_TIME
public static final OutbDeliveryHeaderField<Calendar> BILLING_DOCUMENT_DATE
public static final OutbDeliveryHeaderField<String> BILL_OF_LADING
public static final OutbDeliveryHeaderField<Boolean> COMPLETE_DELIVERY_IS_DEFINED
public static final OutbDeliveryHeaderField<Calendar> CONFIRMATION_TIME
public static final OutbDeliveryHeaderField<String> CREATED_BY_USER
public static final OutbDeliveryHeaderField<Calendar> CREATION_DATE
public static final OutbDeliveryHeaderField<Calendar> CREATION_TIME
public static final OutbDeliveryHeaderField<String> CUSTOMER_GROUP
public static final OutbDeliveryHeaderField<String> DELIVERY_BLOCK_REASON
public static final OutbDeliveryHeaderField<Calendar> 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<Calendar> 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<Calendar> 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<Calendar> 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<Calendar> 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<Calendar> LAST_CHANGE_DATE
public static final OutbDeliveryHeaderField<String> LAST_CHANGED_BY_USER
public static final OutbDeliveryHeaderField<Calendar> LOADING_DATE
public static final OutbDeliveryHeaderField<String> LOADING_POINT
public static final OutbDeliveryHeaderField<Calendar> 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<Calendar> PICKING_DATE
public static final OutbDeliveryHeaderField<Calendar> PICKING_TIME
public static final OutbDeliveryHeaderField<Calendar> PLANNED_GOODS_ISSUE_DATE
public static final OutbDeliveryHeaderField<Calendar> 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<Calendar> TRANSPORTATION_PLANNING_DATE
public static final OutbDeliveryHeaderField<String> TRANSPORTATION_PLANNING_STATUS
public static final OutbDeliveryHeaderField<Calendar> 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
@Generated(value="lombok") public OutbDeliveryHeader()
@ConstructorProperties(value={"actualDeliveryRoute","actualGoodsMovementDate","actualGoodsMovementTime","billingDocumentDate","billOfLading","completeDeliveryIsDefined","confirmationTime","createdByUser","creationDate","creationTime","customerGroup","deliveryBlockReason","deliveryDate","deliveryDocument","deliveryDocumentBySupplier","deliveryDocumentType","deliveryIsInPlant","deliveryPriority","deliveryTime","deliveryVersion","depreciationPercentage","distrStatusByDecentralizedWrhs","documentDate","externalIdentificationType","externalTransportSystem","factoryCalendarByCustomer","goodsIssueOrReceiptSlipNumber","goodsIssueTime","handlingUnitInStock","hdrGeneralIncompletionStatus","hdrGoodsMvtIncompletionStatus","headerBillgIncompletionStatus","headerBillingBlockReason","headerDelivIncompletionStatus","headerGrossWeight","headerNetWeight","headerPackingIncompletionSts","headerPickgIncompletionStatus","headerVolume","headerVolumeUnit","headerWeightUnit","incotermsClassification","incotermsTransferLocation","intercompanyBillingDate","internalFinancialDocument","isDeliveryForSingleWarehouse","isExportDelivery","lastChangeDate","lastChangedByUser","loadingDate","loadingPoint","loadingTime","meansOfTransport","meansOfTransportRefMaterial","meansOfTransportType","orderCombinationIsAllowed","orderID","overallDelivConfStatus","overallDelivReltdBillgStatus","overallGoodsMovementStatus","overallIntcoBillingStatus","overallPackingStatus","overallPickingConfStatus","overallPickingStatus","overallProofOfDeliveryStatus","overallSDProcessStatus","overallWarehouseActivityStatus","ovrlItmDelivIncompletionSts","ovrlItmGdsMvtIncompletionSts","ovrlItmGeneralIncompletionSts","ovrlItmPackingIncompletionSts","ovrlItmPickingIncompletionSts","paymentGuaranteeProcedure","pickedItemsLocation","pickingDate","pickingTime","plannedGoodsIssueDate","proofOfDeliveryDate","proposedDeliveryRoute","receivingPlant","routeSchedule","salesDistrict","salesOffice","salesOrganization","sDDocumentCategory","shipmentBlockReason","shippingCondition","shippingPoint","shippingType","shipToParty","soldToParty","specialProcessingCode","statisticsCurrency","supplier","totalBlockStatus","totalCreditCheckStatus","totalNumberOfPackage","transactionCurrency","transportationGroup","transportationPlanningDate","transportationPlanningStatus","transportationPlanningTime","unloadingPointName","warehouse","warehouseGate","warehouseStagingArea","erpConfigContext","toDeliveryDocumentPartner","toDeliveryDocumentItem"}) @Generated(value="lombok") public OutbDeliveryHeader(@Nullable String actualDeliveryRoute, @Nullable Calendar actualGoodsMovementDate, @Nullable Calendar actualGoodsMovementTime, @Nullable Calendar billingDocumentDate, @Nullable String billOfLading, @Nullable Boolean completeDeliveryIsDefined, @Nullable Calendar confirmationTime, @Nullable String createdByUser, @Nullable Calendar creationDate, @Nullable Calendar creationTime, @Nullable String customerGroup, @Nullable String deliveryBlockReason, @Nullable Calendar deliveryDate, @Nullable String deliveryDocument, @Nullable String deliveryDocumentBySupplier, @Nullable String deliveryDocumentType, @Nullable Boolean deliveryIsInPlant, @Nullable String deliveryPriority, @Nullable Calendar deliveryTime, @Nullable String deliveryVersion, @Nullable BigDecimal depreciationPercentage, @Nullable String distrStatusByDecentralizedWrhs, @Nullable Calendar documentDate, @Nullable String externalIdentificationType, @Nullable String externalTransportSystem, @Nullable String factoryCalendarByCustomer, @Nullable String goodsIssueOrReceiptSlipNumber, @Nullable Calendar 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 Calendar intercompanyBillingDate, @Nullable String internalFinancialDocument, @Nullable String isDeliveryForSingleWarehouse, @Nullable String isExportDelivery, @Nullable Calendar lastChangeDate, @Nullable String lastChangedByUser, @Nullable Calendar loadingDate, @Nullable String loadingPoint, @Nullable Calendar 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 Calendar pickingDate, @Nullable Calendar pickingTime, @Nullable Calendar plannedGoodsIssueDate, @Nullable Calendar 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 Calendar transportationPlanningDate, @Nullable String transportationPlanningStatus, @Nullable Calendar transportationPlanningTime, @Nullable String unloadingPointName, @Nullable String warehouse, @Nullable String warehouseGate, @Nullable String warehouseStagingArea, @Nullable ErpConfigContext erpConfigContext, List<OutbDeliveryPartner> toDeliveryDocumentPartner, List<OutbDeliveryItem> toDeliveryDocumentItem)
public Class<OutbDeliveryHeader> getType()
getType in class VdmObject<OutbDeliveryHeader>public static <T> OutbDeliveryHeaderField<T> field(String fieldName, Class<T> fieldType)
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.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.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.public com.google.common.base.Optional<List<OutbDeliveryPartner>> getDeliveryDocumentPartnerOrNull()
If the navigation property to_DeliveryDocumentPartner for an entity OutbDeliveryHeader has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
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.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.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.public com.google.common.base.Optional<List<OutbDeliveryItem>> getDeliveryDocumentItemOrNull()
If the navigation property to_DeliveryDocumentItem for an entity OutbDeliveryHeader has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
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.@Generated(value="lombok") public static OutbDeliveryHeader.OutbDeliveryHeaderBuilder builder()
@Nullable @Generated(value="lombok") public String getActualDeliveryRoute()
One or more legs Connection between point of departure and destination point Target area You can predefine different standard routes in the system. These are dependent on: Where the delivery comes from Where the delivery is going to Under what conditions the delivery is to take place You can use the route as a selection criteria for: Collective processing of deliveries Selecting deliveries for transportation planning Route as a Connection Between Departure Point and Destination Point In the delivery, you can specify that it takes one of these routes: NA: North Atlantic PA: Pacific Which ship is to carry the delivery is not determined until transportation planning. Route as a Target Area A country can be divided into different delivery areas: R1: North R2: North-West R3: North-East R4: East, and so on Enter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas. The system can propose a route automatically via Customizing. If alternative entry values are defined for your system, you can change the route manually in the document.
@Nullable @Generated(value="lombok") public Calendar getActualGoodsMovementDate()
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 @Generated(value="lombok") public Calendar getActualGoodsMovementTime()
@Nullable @Generated(value="lombok") public Calendar getBillingDocumentDate()
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 @Generated(value="lombok") public String getBillOfLading()
@Nullable @Generated(value="lombok") public Boolean getCompleteDeliveryIsDefined()
@Nullable @Generated(value="lombok") public Calendar getConfirmationTime()
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 @Generated(value="lombok") public String getCreatedByUser()
@Nullable @Generated(value="lombok") public Calendar getCreationDate()
@Nullable @Generated(value="lombok") public Calendar getCreationTime()
@Nullable @Generated(value="lombok") public String getCustomerGroup()
@Nullable @Generated(value="lombok") public String getDeliveryBlockReason()
The system can propose the delivery block indicator according to sales document type. You can also enter a block manually in the header. A block in the header applies to the entire document. If you want to block one or more specific items, you can enter the block at item level. You can block delivery automatically for certain sales document types (for example, free of charge deliveries) where it is important that someone checks the details before shipping takes place. If you use a credit limit check, the system can automatically block delivery. You can change this block. However, as soon as you change any of the values in the sales document, the system automatically reapplies the delivery block.
@Nullable @Generated(value="lombok") public Calendar getDeliveryDate()
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 transportation Picking and loading the goods Transporting the delivery from your warehouse to the customer You can change the date manually during delivery processing.
@Nullable @Generated(value="lombok") public String getDeliveryDocument()
@Nullable @Generated(value="lombok") public String getDeliveryDocumentBySupplier()
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 @Generated(value="lombok") public String getDeliveryDocumentType()
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 @Generated(value="lombok") public Boolean getDeliveryIsInPlant()
@Nullable @Generated(value="lombok") public String getDeliveryPriority()
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 @Generated(value="lombok") public Calendar getDeliveryTime()
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 @Generated(value="lombok") public String getDeliveryVersion()
@Nullable @Generated(value="lombok") public BigDecimal getDepreciationPercentage()
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 @Generated(value="lombok") public String getDistrStatusByDecentralizedWrhs()
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 @Generated(value="lombok") public Calendar getDocumentDate()
@Nullable @Generated(value="lombok") public String getExternalIdentificationType()
@Nullable @Generated(value="lombok") public String getExternalTransportSystem()
@Nullable @Generated(value="lombok") public String getFactoryCalendarByCustomer()
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 @Generated(value="lombok") public String getGoodsIssueOrReceiptSlipNumber()
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. Note This 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 @Generated(value="lombok") public Calendar getGoodsIssueTime()
@Nullable @Generated(value="lombok") public String getHandlingUnitInStock()
If an additional handling unit of the delivery has been placed in WM stock, goods issue cannot be posted for the delivery.
@Nullable @Generated(value="lombok") public String getHdrGeneralIncompletionStatus()
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 @Generated(value="lombok") public String getHdrGoodsMvtIncompletionStatus()
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 @Generated(value="lombok") public String getHeaderBillgIncompletionStatus()
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 @Generated(value="lombok") public String getHeaderBillingBlockReason()
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 @Generated(value="lombok") public String getHeaderDelivIncompletionStatus()
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 @Generated(value="lombok") public BigDecimal getHeaderGrossWeight()
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 @Generated(value="lombok") public BigDecimal getHeaderNetWeight()
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 @Generated(value="lombok") public String getHeaderPackingIncompletionSts()
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 @Generated(value="lombok") public String getHeaderPickgIncompletionStatus()
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 @Generated(value="lombok") public BigDecimal getHeaderVolume()
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 @Generated(value="lombok") public String getHeaderVolumeUnit()
If you specify a volume, you have to enter the corresponding volume unit here.
@Nullable @Generated(value="lombok") public String getHeaderWeightUnit()
If you specify a weight, you must enter the corresponding unit of weight here.
@Nullable @Generated(value="lombok") public String getIncotermsClassification()
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 @Generated(value="lombok") public String getIncotermsTransferLocation()
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 @Generated(value="lombok") public Calendar getIntercompanyBillingDate()
@Nullable @Generated(value="lombok") public String getInternalFinancialDocument()
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 @Generated(value="lombok") public String getIsDeliveryForSingleWarehouse()
on deliveries for one warehouse number.
@Nullable @Generated(value="lombok") public String getIsExportDelivery()
@Nullable @Generated(value="lombok") public Calendar getLastChangeDate()
@Nullable @Generated(value="lombok") public String getLastChangedByUser()
@Nullable @Generated(value="lombok") public Calendar getLoadingDate()
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 point Route Loading group You can change the loading date manually.
@Nullable @Generated(value="lombok") public String getLoadingPoint()
@Nullable @Generated(value="lombok") public Calendar getLoadingTime()
@Nullable @Generated(value="lombok") public String getMeansOfTransport()
You can specify the truck with which the goods are to be transported.
@Nullable @Generated(value="lombok") public String getMeansOfTransportRefMaterial()
@Nullable @Generated(value="lombok") public String getMeansOfTransportType()
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 @Generated(value="lombok") public Boolean getOrderCombinationIsAllowed()
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 @Generated(value="lombok") public String getOrderID()
@Nullable @Generated(value="lombok") public String getOverallDelivConfStatus()
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 @Generated(value="lombok") public String getOverallDelivReltdBillgStatus()
The status message tells you if the document is completely billed, partly billed, or is not relevant for billing.
@Nullable @Generated(value="lombok") public String getOverallGoodsMovementStatus()
The status tells you whether the delivery has already left your warehouse, is still being processed, or whether processing has not yet begun.
@Nullable @Generated(value="lombok") public String getOverallIntcoBillingStatus()
@Nullable @Generated(value="lombok") public String getOverallPackingStatus()
@Nullable @Generated(value="lombok") public String getOverallPickingConfStatus()
The confirmation status is only relevant if you are not using WM transfer orders for picking.
@Nullable @Generated(value="lombok") public String getOverallPickingStatus()
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 @Generated(value="lombok") public String getOverallProofOfDeliveryStatus()
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 confirmed If 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 @Generated(value="lombok") public String getOverallSDProcessStatus()
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 @Generated(value="lombok") public String getOverallWarehouseActivityStatus()
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 @Generated(value="lombok") public String getOvrlItmDelivIncompletionSts()
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 @Generated(value="lombok") public String getOvrlItmGdsMvtIncompletionSts()
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 @Generated(value="lombok") public String getOvrlItmGeneralIncompletionSts()
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 @Generated(value="lombok") public String getOvrlItmPackingIncompletionSts()
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 @Generated(value="lombok") public String getOvrlItmPickingIncompletionSts()
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 @Generated(value="lombok") public String getPaymentGuaranteeProcedure()
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 document Documentary payment guarantees are immediately actived External export credit insurance is activated once a valid contract is available.
@Nullable @Generated(value="lombok") public String getPickedItemsLocation()
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 @Generated(value="lombok") public Calendar getPickingDate()
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 @Generated(value="lombok") public Calendar getPickingTime()
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 @Generated(value="lombok") public Calendar getPlannedGoodsIssueDate()
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 date The pick/pack time The loading time The transit time You can change the date manually during delivery processing.
@Nullable @Generated(value="lombok") public Calendar getProofOfDeliveryDate()
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 @Generated(value="lombok") public String getProposedDeliveryRoute()
One or more legs Connection between point of departure and destination point Target area You can predefine different standard routes in the system. These are dependent on: Where the delivery comes from Where the delivery is going to Under what conditions the delivery is to take place You can use the route as a selection criteria for: Collective processing of deliveries Selecting deliveries for transportation planning Route as a Connection Between Departure Point and Destination Point In the delivery, you can specify that it takes one of these routes: NA: North Atlantic PA: Pacific Which ship is to carry the delivery is not determined until transportation planning. Route as a Target Area A country can be divided into different delivery areas: R1: North R2: North-West R3: North-East R4: East, and so on Enter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas. The system can propose a route automatically via Customizing. If alternative entry values are defined for your system, you can change the route manually in the document.
@Nullable @Generated(value="lombok") public String getReceivingPlant()
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 order Recipient of the delivery/ordering plant from the stock transport order Shipping notification The shipping notification may refer to several recipients. In this case, the field is empty. Rough goods receipt Plant 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 @Generated(value="lombok") public String getRouteSchedule()
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 sent the ship-to party and the unloading point to which the delivery is sent the transportation group of the delivery the shipping condition of the delivery the calender week in which the delivery leaves the shipping point In 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 @Generated(value="lombok") public String getSalesDistrict()
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 @Generated(value="lombok") public String getSalesOffice()
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
@Nullable @Generated(value="lombok") public String getSalesOrganization()
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 @Generated(value="lombok") public String getSDDocumentCategory()
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
@Nullable @Generated(value="lombok") public String getShipmentBlockReason()
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 @Generated(value="lombok") public String getShippingCondition()
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 @Generated(value="lombok") public String getShippingPoint()
You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries. A delivery can be shipped from one shipping point only or received at one receiving point only. 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. You can define a user-specific default value for the shipping point in the user parameter VST.
@Nullable @Generated(value="lombok") public String getShippingType()
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 @Generated(value="lombok") public String getShipToParty()
@Nullable @Generated(value="lombok") public String getSoldToParty()
@Nullable @Generated(value="lombok") public String getSpecialProcessingCode()
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 deliveries the special processing indicator is not already filled in the shipment header
@Nullable @Generated(value="lombok") public String getStatisticsCurrency()
@Nullable @Generated(value="lombok") public String getSupplier()
@Nullable @Generated(value="lombok") public String getTotalBlockStatus()
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 @Generated(value="lombok") public String getTotalCreditCheckStatus()
@Nullable @Generated(value="lombok") public String getTotalNumberOfPackage()
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 @Generated(value="lombok") public String getTransactionCurrency()
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 @Generated(value="lombok") public String getTransportationGroup()
Transportation groups are used for automatic route scheduling during sales order and delivery note processing. Suppose that you sell food products, some of which are perishable and require refrigeration. You create a transportation group that includes all the products that need refrigerated trucks for delivery.
@Nullable @Generated(value="lombok") public Calendar getTransportationPlanningDate()
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 @Generated(value="lombok") public String getTransportationPlanningStatus()
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 relevant Delivery is not to be processed in transportation planning. This is the case when: - the delivery type is not relevant for transportation, or - the route is not relevant for transportation (only for outbound deliveries; not required for inbound deliveries), or - a shipment block has been set in the delivery (only for outbound deliveries: not required for inbound deliveries) A - Not yet planned Delivery is to be processed in transportation planning. It has not yet been assigned to a shipment document. B - Partially planned Delivery is to be processed in transportation planning. The delivery has already been assigned to at least one shipment document but the transportation chain is not complete (see status C). C - Completely planned Delivery has been assigned to one or more shipment documents in transportation planning. Depending on the leg indicator in each shipment header, the delivery is considered 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 a subsequent stage, thus connecting the point of departure with the destination of the delivery with no gaps in transportation (as of Release 4.6A).
@Nullable @Generated(value="lombok") public Calendar getTransportationPlanningTime()
@Nullable @Generated(value="lombok") public String getUnloadingPointName()
@Nullable @Generated(value="lombok") public String getWarehouse()
All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
@Nullable @Generated(value="lombok") public String getWarehouseGate()
Doors can be defined for different purposes (both at the same and different times): for goods issue for goods receipt for cross docking processes for flow-throughs
@Nullable @Generated(value="lombok") public String getWarehouseStagingArea()
Staging areas can be used for different purposes (at the same time, if necessary): o Goods issue o Goods receipt o Cross-docking processes o Direct distribution
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setActualDeliveryRoute(@Nullable String actualDeliveryRoute)
One or more legs Connection between point of departure and destination point Target area You can predefine different standard routes in the system. These are dependent on: Where the delivery comes from Where the delivery is going to Under what conditions the delivery is to take place You can use the route as a selection criteria for: Collective processing of deliveries Selecting deliveries for transportation planning Route as a Connection Between Departure Point and Destination Point In the delivery, you can specify that it takes one of these routes: NA: North Atlantic PA: Pacific Which ship is to carry the delivery is not determined until transportation planning. Route as a Target Area A country can be divided into different delivery areas: R1: North R2: North-West R3: North-East R4: East, and so on Enter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas. The system can propose a route automatically via Customizing. If alternative entry values are defined for your system, you can change the route manually in the document.
actualDeliveryRoute - @Generated(value="lombok") public void setActualGoodsMovementDate(@Nullable Calendar 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 - @Generated(value="lombok") public void setActualGoodsMovementTime(@Nullable Calendar actualGoodsMovementTime)
actualGoodsMovementTime - @Generated(value="lombok") public void setBillingDocumentDate(@Nullable Calendar 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 - @Generated(value="lombok") public void setBillOfLading(@Nullable String billOfLading)
billOfLading - @Generated(value="lombok") public void setCompleteDeliveryIsDefined(@Nullable Boolean completeDeliveryIsDefined)
completeDeliveryIsDefined - @Generated(value="lombok") public void setConfirmationTime(@Nullable Calendar 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 - @Generated(value="lombok") public void setCreatedByUser(@Nullable String createdByUser)
createdByUser - @Generated(value="lombok") public void setCreationDate(@Nullable Calendar creationDate)
creationDate - @Generated(value="lombok") public void setCreationTime(@Nullable Calendar creationTime)
creationTime - @Generated(value="lombok") public void setCustomerGroup(@Nullable String customerGroup)
customerGroup - @Generated(value="lombok") public void setDeliveryBlockReason(@Nullable String deliveryBlockReason)
The system can propose the delivery block indicator according to sales document type. You can also enter a block manually in the header. A block in the header applies to the entire document. If you want to block one or more specific items, you can enter the block at item level. You can block delivery automatically for certain sales document types (for example, free of charge deliveries) where it is important that someone checks the details before shipping takes place. If you use a credit limit check, the system can automatically block delivery. You can change this block. However, as soon as you change any of the values in the sales document, the system automatically reapplies the delivery block.
deliveryBlockReason - @Generated(value="lombok") public void setDeliveryDate(@Nullable Calendar 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 transportation Picking and loading the goods Transporting the delivery from your warehouse to the customer You can change the date manually during delivery processing.
deliveryDate - @Generated(value="lombok") public void setDeliveryDocument(@Nullable String deliveryDocument)
deliveryDocument - @Generated(value="lombok") public void setDeliveryDocumentBySupplier(@Nullable String 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 - @Generated(value="lombok") public void setDeliveryDocumentType(@Nullable String 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 - @Generated(value="lombok") public void setDeliveryIsInPlant(@Nullable Boolean deliveryIsInPlant)
deliveryIsInPlant - @Generated(value="lombok") public void setDeliveryPriority(@Nullable String 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 - @Generated(value="lombok") public void setDeliveryTime(@Nullable Calendar 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 - @Generated(value="lombok") public void setDeliveryVersion(@Nullable String deliveryVersion)
deliveryVersion - @Generated(value="lombok") public void setDepreciationPercentage(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setDistrStatusByDecentralizedWrhs(@Nullable String 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 - @Generated(value="lombok") public void setDocumentDate(@Nullable Calendar documentDate)
documentDate - @Generated(value="lombok") public void setExternalIdentificationType(@Nullable String externalIdentificationType)
externalIdentificationType - @Generated(value="lombok") public void setExternalTransportSystem(@Nullable String externalTransportSystem)
externalTransportSystem - @Generated(value="lombok") public void setFactoryCalendarByCustomer(@Nullable String 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 - @Generated(value="lombok") public void setGoodsIssueOrReceiptSlipNumber(@Nullable String 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. Note This 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 - @Generated(value="lombok") public void setGoodsIssueTime(@Nullable Calendar goodsIssueTime)
goodsIssueTime - @Generated(value="lombok") public void setHandlingUnitInStock(@Nullable String handlingUnitInStock)
If an additional handling unit of the delivery has been placed in WM stock, goods issue cannot be posted for the delivery.
handlingUnitInStock - @Generated(value="lombok") public void setHdrGeneralIncompletionStatus(@Nullable String 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 - @Generated(value="lombok") public void setHdrGoodsMvtIncompletionStatus(@Nullable String 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 - @Generated(value="lombok") public void setHeaderBillgIncompletionStatus(@Nullable String 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 - @Generated(value="lombok") public void setHeaderBillingBlockReason(@Nullable String 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 - @Generated(value="lombok") public void setHeaderDelivIncompletionStatus(@Nullable String 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 - @Generated(value="lombok") public void setHeaderGrossWeight(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setHeaderNetWeight(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setHeaderPackingIncompletionSts(@Nullable String 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 - @Generated(value="lombok") public void setHeaderPickgIncompletionStatus(@Nullable String 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 - @Generated(value="lombok") public void setHeaderVolume(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setHeaderVolumeUnit(@Nullable String headerVolumeUnit)
If you specify a volume, you have to enter the corresponding volume unit here.
headerVolumeUnit - @Generated(value="lombok") public void setHeaderWeightUnit(@Nullable String headerWeightUnit)
If you specify a weight, you must enter the corresponding unit of weight here.
headerWeightUnit - @Generated(value="lombok") public void setIncotermsClassification(@Nullable String 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 - @Generated(value="lombok") public void setIncotermsTransferLocation(@Nullable String 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 - @Generated(value="lombok") public void setIntercompanyBillingDate(@Nullable Calendar intercompanyBillingDate)
intercompanyBillingDate - @Generated(value="lombok") public void setInternalFinancialDocument(@Nullable String 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 - @Generated(value="lombok") public void setIsDeliveryForSingleWarehouse(@Nullable String isDeliveryForSingleWarehouse)
on deliveries for one warehouse number.
isDeliveryForSingleWarehouse - @Generated(value="lombok") public void setIsExportDelivery(@Nullable String isExportDelivery)
isExportDelivery - @Generated(value="lombok") public void setLastChangeDate(@Nullable Calendar lastChangeDate)
lastChangeDate - @Generated(value="lombok") public void setLastChangedByUser(@Nullable String lastChangedByUser)
lastChangedByUser - @Generated(value="lombok") public void setLoadingDate(@Nullable Calendar 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 point Route Loading group You can change the loading date manually.
loadingDate - @Generated(value="lombok") public void setLoadingPoint(@Nullable String loadingPoint)
loadingPoint - @Generated(value="lombok") public void setLoadingTime(@Nullable Calendar loadingTime)
loadingTime - @Generated(value="lombok") public void setMeansOfTransport(@Nullable String meansOfTransport)
You can specify the truck with which the goods are to be transported.
meansOfTransport - @Generated(value="lombok") public void setMeansOfTransportRefMaterial(@Nullable String meansOfTransportRefMaterial)
meansOfTransportRefMaterial - @Generated(value="lombok") public void setMeansOfTransportType(@Nullable String 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 - @Generated(value="lombok") public void setOrderCombinationIsAllowed(@Nullable Boolean 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 - @Generated(value="lombok") public void setOrderID(@Nullable String orderID)
orderID - @Generated(value="lombok") public void setOverallDelivConfStatus(@Nullable String 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 - @Generated(value="lombok") public void setOverallDelivReltdBillgStatus(@Nullable String overallDelivReltdBillgStatus)
The status message tells you if the document is completely billed, partly billed, or is not relevant for billing.
overallDelivReltdBillgStatus - @Generated(value="lombok") public void setOverallGoodsMovementStatus(@Nullable String 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 - @Generated(value="lombok") public void setOverallIntcoBillingStatus(@Nullable String overallIntcoBillingStatus)
overallIntcoBillingStatus - @Generated(value="lombok") public void setOverallPackingStatus(@Nullable String overallPackingStatus)
overallPackingStatus - @Generated(value="lombok") public void setOverallPickingConfStatus(@Nullable String overallPickingConfStatus)
The confirmation status is only relevant if you are not using WM transfer orders for picking.
overallPickingConfStatus - @Generated(value="lombok") public void setOverallPickingStatus(@Nullable String 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 - @Generated(value="lombok") public void setOverallProofOfDeliveryStatus(@Nullable String 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 confirmed If 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 - @Generated(value="lombok") public void setOverallSDProcessStatus(@Nullable String 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 - @Generated(value="lombok") public void setOverallWarehouseActivityStatus(@Nullable String 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 - @Generated(value="lombok") public void setOvrlItmDelivIncompletionSts(@Nullable String 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 - @Generated(value="lombok") public void setOvrlItmGdsMvtIncompletionSts(@Nullable String 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 - @Generated(value="lombok") public void setOvrlItmGeneralIncompletionSts(@Nullable String 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 - @Generated(value="lombok") public void setOvrlItmPackingIncompletionSts(@Nullable String 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 - @Generated(value="lombok") public void setOvrlItmPickingIncompletionSts(@Nullable String 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 - @Generated(value="lombok") public void setPaymentGuaranteeProcedure(@Nullable String 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 document Documentary payment guarantees are immediately actived External export credit insurance is activated once a valid contract is available.
paymentGuaranteeProcedure - @Generated(value="lombok") public void setPickedItemsLocation(@Nullable String 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 - @Generated(value="lombok") public void setPickingDate(@Nullable Calendar 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 - @Generated(value="lombok") public void setPickingTime(@Nullable Calendar 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 - @Generated(value="lombok") public void setPlannedGoodsIssueDate(@Nullable Calendar 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 date The pick/pack time The loading time The transit time You can change the date manually during delivery processing.
plannedGoodsIssueDate - @Generated(value="lombok") public void setProofOfDeliveryDate(@Nullable Calendar 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 - @Generated(value="lombok") public void setProposedDeliveryRoute(@Nullable String proposedDeliveryRoute)
One or more legs Connection between point of departure and destination point Target area You can predefine different standard routes in the system. These are dependent on: Where the delivery comes from Where the delivery is going to Under what conditions the delivery is to take place You can use the route as a selection criteria for: Collective processing of deliveries Selecting deliveries for transportation planning Route as a Connection Between Departure Point and Destination Point In the delivery, you can specify that it takes one of these routes: NA: North Atlantic PA: Pacific Which ship is to carry the delivery is not determined until transportation planning. Route as a Target Area A country can be divided into different delivery areas: R1: North R2: North-West R3: North-East R4: East, and so on Enter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas. The system can propose a route automatically via Customizing. If alternative entry values are defined for your system, you can change the route manually in the document.
proposedDeliveryRoute - @Generated(value="lombok") public void setReceivingPlant(@Nullable String 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 order Recipient of the delivery/ordering plant from the stock transport order Shipping notification The shipping notification may refer to several recipients. In this case, the field is empty. Rough goods receipt Plant 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 - @Generated(value="lombok") public void setRouteSchedule(@Nullable String 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 sent the ship-to party and the unloading point to which the delivery is sent the transportation group of the delivery the shipping condition of the delivery the calender week in which the delivery leaves the shipping point In 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 - @Generated(value="lombok") public void setSalesDistrict(@Nullable String 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 - @Generated(value="lombok") public void setSalesOffice(@Nullable String salesOffice)
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
salesOffice - @Generated(value="lombok") public void setSalesOrganization(@Nullable String 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 - @Generated(value="lombok") public void setSDDocumentCategory(@Nullable String sDDocumentCategory)
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
sDDocumentCategory - @Generated(value="lombok") public void setShipmentBlockReason(@Nullable String 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 - @Generated(value="lombok") public void setShippingCondition(@Nullable String 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 - @Generated(value="lombok") public void setShippingPoint(@Nullable String shippingPoint)
You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries. A delivery can be shipped from one shipping point only or received at one receiving point only. 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. You can define a user-specific default value for the shipping point in the user parameter VST.
shippingPoint - @Generated(value="lombok") public void setShippingType(@Nullable String 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 - @Generated(value="lombok") public void setShipToParty(@Nullable String shipToParty)
shipToParty - @Generated(value="lombok") public void setSoldToParty(@Nullable String soldToParty)
soldToParty - @Generated(value="lombok") public void setSpecialProcessingCode(@Nullable String 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 deliveries the special processing indicator is not already filled in the shipment header
specialProcessingCode - @Generated(value="lombok") public void setStatisticsCurrency(@Nullable String statisticsCurrency)
statisticsCurrency - @Generated(value="lombok") public void setSupplier(@Nullable String supplier)
supplier - @Generated(value="lombok") public void setTotalBlockStatus(@Nullable String 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 - @Generated(value="lombok") public void setTotalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
totalCreditCheckStatus - @Generated(value="lombok") public void setTotalNumberOfPackage(@Nullable String 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 - @Generated(value="lombok") public void setTransactionCurrency(@Nullable String 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 - @Generated(value="lombok") public void setTransportationGroup(@Nullable String transportationGroup)
Transportation groups are used for automatic route scheduling during sales order and delivery note processing. Suppose that you sell food products, some of which are perishable and require refrigeration. You create a transportation group that includes all the products that need refrigerated trucks for delivery.
transportationGroup - @Generated(value="lombok") public void setTransportationPlanningDate(@Nullable Calendar 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 - @Generated(value="lombok") public void setTransportationPlanningStatus(@Nullable String 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 relevant Delivery is not to be processed in transportation planning. This is the case when: - the delivery type is not relevant for transportation, or - the route is not relevant for transportation (only for outbound deliveries; not required for inbound deliveries), or - a shipment block has been set in the delivery (only for outbound deliveries: not required for inbound deliveries) A - Not yet planned Delivery is to be processed in transportation planning. It has not yet been assigned to a shipment document. B - Partially planned Delivery is to be processed in transportation planning. The delivery has already been assigned to at least one shipment document but the transportation chain is not complete (see status C). C - Completely planned Delivery has been assigned to one or more shipment documents in transportation planning. Depending on the leg indicator in each shipment header, the delivery is considered 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 a subsequent stage, thus connecting the point of departure with the destination of the delivery with no gaps in transportation (as of Release 4.6A).
transportationPlanningStatus - @Generated(value="lombok") public void setTransportationPlanningTime(@Nullable Calendar transportationPlanningTime)
transportationPlanningTime - @Generated(value="lombok") public void setUnloadingPointName(@Nullable String unloadingPointName)
unloadingPointName - @Generated(value="lombok") public void setWarehouse(@Nullable String warehouse)
All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
warehouse - @Generated(value="lombok") public void setWarehouseGate(@Nullable String warehouseGate)
Doors can be defined for different purposes (both at the same and different times): for goods issue for goods receipt for cross docking processes for flow-throughs
warehouseGate - @Generated(value="lombok") public void setWarehouseStagingArea(@Nullable String warehouseStagingArea)
Staging areas can be used for different purposes (at the same time, if necessary): o Goods issue o Goods receipt o Cross-docking processes o Direct distribution
warehouseStagingArea - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<OutbDeliveryHeader>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<OutbDeliveryHeader>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<OutbDeliveryHeader>Copyright © 2017 SAP SE. All rights reserved.