public static final class OutbDeliveryHeader.OutbDeliveryHeaderBuilder extends Object
@Nonnull public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryDocumentPartner(OutbDeliveryPartner... value)
value - The OutbDeliveryPartners to build this OutbDeliveryHeader with.@Nonnull public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryDocumentItem(OutbDeliveryItem... value)
value - The OutbDeliveryItems to build this OutbDeliveryHeader with.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder shippinglocationtimezone(@Nullable String shippinglocationtimezone)
Original property name from the Odata EDM: Shippinglocationtimezone
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder actualDeliveryRoute(@Nullable String actualDeliveryRoute)
Original property name from the Odata EDM: ActualDeliveryRoute
One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document.
to represent the following situations:this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder receivinglocationtimezone(@Nullable String receivinglocationtimezone)
Original property name from the Odata EDM: Receivinglocationtimezone
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder actualGoodsMovementDate(@Nullable LocalDateTime actualGoodsMovementDate)
Original property name from the Odata EDM: ActualGoodsMovementDate
If the goods movement date is not filled in, the system automatically uses the current date.The posting date for the material document is filled using the actual goods movement date. The document date shown on the material document is the current date.
the posting should occur in a previous period or month, you can do so with this default.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder actualGoodsMovementTime(@Nullable LocalTime actualGoodsMovementTime)
Original property name from the Odata EDM: ActualGoodsMovementTime
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder billingDocumentDate(@Nullable LocalDateTime billingDocumentDate)
Original property name from the Odata EDM: BillingDocumentDate
When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, 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. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. 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.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder billOfLading(@Nullable String billOfLading)
Original property name from the Odata EDM: BillOfLading
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder completeDeliveryIsDefined(@Nullable Boolean completeDeliveryIsDefined)
Original property name from the Odata EDM: CompleteDeliveryIsDefined
can be partially delivered and completed over a number of deliveries.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder confirmationTime(@Nullable LocalTime confirmationTime)
Original property name from the Odata EDM: ConfirmationTime
The POD confirmation time is the same as the POD verification time if the ship-to party verifies the receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder creationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryBlockReason(@Nullable String deliveryBlockReason)
Original property name from the Odata EDM: DeliveryBlockReason
The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryDate(@Nullable LocalDateTime deliveryDate)
Original property name from the Odata EDM: DeliveryDate
The system can use predefined time estimates to calculate the delivery date for goods issue. The estimates take into account the time needed for the following activities:Arranging transportationPicking and loading the goodsTransporting the delivery from your warehouse to the customerYou can change the date manually during delivery processing.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryDocument(@Nullable String deliveryDocument)
Original property name from the Odata EDM: DeliveryDocument
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryDocumentBySupplier(@Nullable String deliveryDocumentBySupplier)
Original property name from the Odata EDM: DeliveryDocumentBySupplier
When you create an inbound delivery manually or when the supplier creates a notification (per EDI), the external identification number can have a maximum of 35 characters.Please note:Only 16 reference characters are used for invoice verification. Therefore, we recommend that you use no more than 16 characters in the external identification number.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryDocumentType(@Nullable String deliveryDocumentType)
Original property name from the Odata EDM: DeliveryDocumentType
The delivery type determines how the system processes a delivery. For example, depending on the delivery type, the system determines which screens to present and which data to request from the user.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryIsInPlant(@Nullable Boolean deliveryIsInPlant)
Original property name from the Odata EDM: DeliveryIsInPlant
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryPriority(@Nullable String deliveryPriority)
Original property name from the Odata EDM: DeliveryPriority
You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryTime(@Nullable LocalTime deliveryTime)
Original property name from the Odata EDM: DeliveryTime
You can store information about the customer's goods receiving hours in the customer master record of the ship-to party. This information includes receiving hours for each working day and for each of the customer's unloading points.The system may propose an arrival time from the customer master record. If the customer allows deliveries during a certain time slot, the system proposes the earliest time in the slot. You can change the proposed time manually in the sales order.If you schedule a delivery for a Monday and the customer has receiving hours between 8am and 12am, the system proposes 8am as the earliest possible arrival time.
of delivery.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder deliveryVersion(@Nullable String deliveryVersion)
Original property name from the Odata EDM: DeliveryVersion
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder depreciationPercentage(@Nullable BigDecimal depreciationPercentage)
Original property name from the Odata EDM: DepreciationPercentage
In general, the financial document covers the full amount of a document, that is, 100%.In exceptional cases, business partners may agree that only part of the amount is to be covered by a corresponding financial document.This means that only part of the amount is written off against the total value of the financial document.For example, if a business transaction has been defined such that 30% of the document value is covered by credit management and the remaining amount by a corresponding letter of credit, you should enter the value 70.If you do not enter a value, or if you enter the value '0,00 %', the system uses the value '100.00 %', that is, the document value fully coverd by the assigned financial document.
be written off against the total value of the financial document.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder distrStatusByDecentralizedWrhs(@Nullable String distrStatusByDecentralizedWrhs)
Original property name from the Odata EDM: DistrStatusByDecentralizedWrhs
In the central system, this field may contain the following characteristics:' ': delivery is not relevant for distribution to a decentralized WM System.'A': delivery is relevant for distribution in the decentralized system. When the delivery is saved, an IDoc is created. The system then uses this IDoc to distribute the delivery in the decentralized system.'B': delivery was distributed in the decentralized system and is currently being processed there.'C': processing of the delivery in the decentralized system is complete. Any changes are confirmed in the central system.'D': The delivery is planned for distribution in the decentralized system. You can trigger distribution using the delivery monitor.'E': The delivery was subsequently split in the decentralized system. In this case, no further changes can be made to the document in the central system.'F': Change management was subsequently switched off. For example, because the central system was temporarily not available. The delivery can no longer be changed in the central system.This field may contain the following characteristics in the decentralized Warehouse Management System:'A': delivery is being processed.'C': processing of this delivery in the decentral system is complete. The delivery is confirmed in the central system via goods issue or goods receipt posting. The delivery can no longer be changed in the decentral system.'E': The delivery was split in the decentralized system. The delivery can then be changed, however, only changes to the delivery quantity are returned to the central system.'F': Change management was subsequently switched off. The delivery can only be changed in the decentralized system. Only changes to the delivery quantity are reported back to the central system.Statuses 'B' and 'D' do not occur in this system.
System processing. This field cannot be changed manually. Instead, the system determines the status using delivery items' warehouse numbers and the delivery processing status.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder documentDate(@Nullable LocalDateTime documentDate)
Original property name from the Odata EDM: DocumentDate
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder externalIdentificationType(@Nullable String externalIdentificationType)
Original property name from the Odata EDM: ExternalIdentificationType
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder externalTransportSystem(@Nullable String externalTransportSystem)
Original property name from the Odata EDM: ExternalTransportSystem
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder factoryCalendarByCustomer(@Nullable String factoryCalendarByCustomer)
Original property name from the Odata EDM: FactoryCalendarByCustomer
The system proposes the factory calendar from the information about unloading points in the customer master record of the ship-to party.You cannot change the calendar during sales order and delivery processing. If you enter a date that does not comply with the specified calendar, the system gives you a warning message before you can continue.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder goodsIssueOrReceiptSlipNumber(@Nullable String goodsIssueOrReceiptSlipNumber)
Original property name from the Odata EDM: GoodsIssueOrReceiptSlipNumber
If number assignment for goods receipt/issue slips is active in the plant, you can proceed as follows:You enter a number manually.You do not enter a number. In this case, the system automatically assigns a number.NoteThis GR/GI slip number has only been designed for use in those countries (for example, Italy) whose legislation requires specification of this number for goods that leave the plant and are transported on public roads.In other countries, the material document number printed on the GR/GI slip (in the standard system) is usually sufficient. To enter external documents, you can use the field Material slip or Delivery note.
receipt/issue slip. This number can be assigned both internally and externally.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder goodsIssueTime(@Nullable LocalTime goodsIssueTime)
Original property name from the Odata EDM: GoodsIssueTime
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder handlingUnitInStock(@Nullable String handlingUnitInStock)
Original property name from the Odata EDM: HandlingUnitInStock
If an additional handling unit of the delivery has been placed in WM stock, goods issue cannot be posted for the delivery.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder hdrGeneralIncompletionStatus(@Nullable String hdrGeneralIncompletionStatus)
Original property name from the Odata EDM: HdrGeneralIncompletionStatus
The status tells you if general header information is complete. You cannot copy sales documents with missing information into other sales documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
business, shipping, and billing data.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder hdrGoodsMvtIncompletionStatus(@Nullable String hdrGoodsMvtIncompletionStatus)
Original property name from the Odata EDM: HdrGoodsMvtIncompletionStatus
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerBillgIncompletionStatus(@Nullable String headerBillgIncompletionStatus)
Original property name from the Odata EDM: HeaderBillgIncompletionStatus
The status tells you if billing-related header information is complete. Incomplete sales documents cannot be billed. For example, if a sales order contains no information about terms of payment, you cannot create an invoice for it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerBillingBlockReason(@Nullable String headerBillingBlockReason)
Original property name from the Odata EDM: HeaderBillingBlockReason
The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerDelivIncompletionStatus(@Nullable String headerDelivIncompletionStatus)
Original property name from the Odata EDM: HeaderDelivIncompletionStatus
The status tells you if delivery-related header information is complete. Missing information affects further processing. For example, a sales order that contains no information about Incoterms cannot be delivered.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerGrossWeight(@Nullable BigDecimal headerGrossWeight)
Original property name from the Odata EDM: HeaderGrossWeight
The system calculates the gross weight for each item by multiplying the delivery quantity by the gross weight per sales unit from the sales order. If there is no related sales order, the system uses the gross weight from the material master record.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerNetWeight(@Nullable BigDecimal headerNetWeight)
Original property name from the Odata EDM: HeaderNetWeight
The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record.You can change the net weight manually in the delivery document.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerPackingIncompletionSts(@Nullable String headerPackingIncompletionSts)
Original property name from the Odata EDM: HeaderPackingIncompletionSts
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerPickgIncompletionStatus(@Nullable String headerPickgIncompletionStatus)
Original property name from the Odata EDM: HeaderPickgIncompletionStatus
This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerVolume(@Nullable BigDecimal headerVolume)
Original property name from the Odata EDM: HeaderVolume
The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order. If there is no related sales order, the system uses the volume from the material master record.You can change the volume manually in the delivery document.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerVolumeUnit(@Nullable String headerVolumeUnit)
Original property name from the Odata EDM: HeaderVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder headerWeightUnit(@Nullable String headerWeightUnit)
Original property name from the Odata EDM: HeaderWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder incotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
Commerce (ICC).this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder incotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder intercompanyBillingDate(@Nullable LocalDateTime intercompanyBillingDate)
Original property name from the Odata EDM: IntercompanyBillingDate
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder internalFinancialDocument(@Nullable String internalFinancialDocument)
Original property name from the Odata EDM: InternalFinancialDocument
You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance.
assigned by the system.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder isDeliveryForSingleWarehouse(@Nullable String isDeliveryForSingleWarehouse)
Original property name from the Odata EDM: IsDeliveryForSingleWarehouse
on deliveries for one warehouse number.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder isExportDelivery(@Nullable String isExportDelivery)
Original property name from the Odata EDM: IsExportDelivery
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder lastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder loadingDate(@Nullable LocalDateTime loadingDate)
Original property name from the Odata EDM: LoadingDate
If items in the same delivery have different loading dates, the earliest date appears in the document header.The system uses predefined time estimates to calculate the loading date. The estimates take into account the following information:Shipping pointRouteLoading groupYou can change the loading date manually.
the delivery to reach the customer on time. Any special packaging materials required for loading must also be available by this date.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder loadingPoint(@Nullable String loadingPoint)
Original property name from the Odata EDM: LoadingPoint
a specific loading bay).this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder loadingTime(@Nullable LocalTime loadingTime)
Original property name from the Odata EDM: LoadingTime
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder meansOfTransport(@Nullable String meansOfTransport)
Original property name from the Odata EDM: MeansOfTransport
You can specify the truck with which the goods are to be transported.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder meansOfTransportRefMaterial(@Nullable String meansOfTransportRefMaterial)
Original property name from the Odata EDM: MeansOfTransportRefMaterial
equipment'.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder meansOfTransportType(@Nullable String meansOfTransportType)
Original property name from the Odata EDM: MeansOfTransportType
This key identifies the means of transport type. The means of transport type is a packaging material type in the category 'means of transport' or 'transport equipment'.All available trucks are assigned to the means of transport type LKW.Available ships of means of transport type ship.If the goods are to be transported by road, enter the means of transport type LKW.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder orderCombinationIsAllowed(@Nullable Boolean orderCombinationIsAllowed)
Original property name from the Odata EDM: OrderCombinationIsAllowed
The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallDelivConfStatus(@Nullable String overallDelivConfStatus)
Original property name from the Odata EDM: OverallDelivConfStatus
The system confirms delivery for each schedule line after checking availability. The confirmation means that the system is able to confirm that a quantity is available for delivery on a certain day. The confirmation does not reflect when the goods are shipped to or received by the customer.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallDelivReltdBillgStatus(@Nullable String overallDelivReltdBillgStatus)
Original property name from the Odata EDM: OverallDelivReltdBillgStatus
The status message tells you if the document is completely billed, partly billed, or is not relevant for billing.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallGoodsMovementStatus(@Nullable String overallGoodsMovementStatus)
Original property name from the Odata EDM: OverallGoodsMovementStatus
The status tells you whether the delivery has already left your warehouse, is still being processed, or whether processing has not yet begun.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallIntcoBillingStatus(@Nullable String overallIntcoBillingStatus)
Original property name from the Odata EDM: OverallIntcoBillingStatus
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallPackingStatus(@Nullable String overallPackingStatus)
Original property name from the Odata EDM: OverallPackingStatus
these items are completely or only partially packed.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallPickingConfStatus(@Nullable String overallPickingConfStatus)
Original property name from the Odata EDM: OverallPickingConfStatus
The confirmation status is only relevant if you are not using WM transfer orders for picking.
for the delivery or whether picking has already been confirmed.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallPickingStatus(@Nullable String overallPickingStatus)
Original property name from the Odata EDM: OverallPickingStatus
Displays whether the delivery has been completely picked or put away, whether it is in the process of being picked/put away, or whether it has just started.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallProofOfDeliveryStatus(@Nullable String overallProofOfDeliveryStatus)
Original property name from the Odata EDM: OverallProofOfDeliveryStatus
The status informs you whether the ship-to party reported a POD for this delivery:This status can have the following values:' ' Not relevant for the POD process'A' Relevant for the POD process'B' Differences were reported'C' Quantities were verified and confirmedIf all item quantities of a delivery are reported with no differences, the process is confirmed automatically. If differences are reported, the proof of delivery must be confirmed manually.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallSDProcessStatus(@Nullable String overallSDProcessStatus)
Original property name from the Odata EDM: OverallSDProcessStatus
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder overallWarehouseActivityStatus(@Nullable String overallWarehouseActivityStatus)
Original property name from the Odata EDM: OverallWarehouseActivityStatus
The status line tells you whether a transfer order for WM is required or not, and, if required, whether it is confirmed or still open for processing.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder ovrlItmDelivIncompletionSts(@Nullable String ovrlItmDelivIncompletionSts)
Original property name from the Odata EDM: OvrlItmDelivIncompletionSts
If shipping-related item information is missing from the sales order, the system marks the status as incomplete. You cannot ship an item that has incomplete shipping information. For example, if an item contains no information about a shipping point, you cannot ship it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder ovrlItmGdsMvtIncompletionSts(@Nullable String ovrlItmGdsMvtIncompletionSts)
Original property name from the Odata EDM: OvrlItmGdsMvtIncompletionSts
If shipping-related item data from the sales order is missing, the system sets the status to incomplete. An item with incomplete shipping data cannot be transmitted. If an item does not, for example, contain any specifications on the shipping point, you cannot transmit it.If you attempt to save a document where data is missing, the system will point out that the document is incomplete. You can then call up a list of the fields with missing specifications and complete them. However, you can also save the incomplete document and supply the missing data at a later time.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder ovrlItmGeneralIncompletionSts(@Nullable String ovrlItmGeneralIncompletionSts)
Original property name from the Odata EDM: OvrlItmGeneralIncompletionSts
The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
includes business, shipping, and billing data.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder ovrlItmPackingIncompletionSts(@Nullable String ovrlItmPackingIncompletionSts)
Original property name from the Odata EDM: OvrlItmPackingIncompletionSts
If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder ovrlItmPickingIncompletionSts(@Nullable String ovrlItmPickingIncompletionSts)
Original property name from the Odata EDM: OvrlItmPickingIncompletionSts
If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder paymentGuaranteeProcedure(@Nullable String paymentGuaranteeProcedure)
Original property name from the Odata EDM: PaymentGuaranteeProcedure
In risk management for receivables, depending on payment guarantee category, the system accesses the form of payment guarantee using the following rules:Payment cards are activated once you have specified a payment card in the documentDocumentary payment guarantees are immediately activedExternal export credit insurance is activated once a valid contract is available.
in which the system assigns forms of payment guarantee to sales document items.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder pickedItemsLocation(@Nullable String pickedItemsLocation)
Original property name from the Odata EDM: PickedItemsLocation
If your warehouse procedures require it, you can arrange for picked items to be assembled in boxes, trays, or bins in the loading area, prior to packing and loading. The location you specify in this field appears on the picking list.
packing and loading.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder pickingDate(@Nullable LocalDateTime pickingDate)
Original property name from the Odata EDM: PickingDate
If the items in a delivery have different picking dates, the system displays the earliest picking date in the delivery document header. You can use the picking date as a selection criterion for processing picking lists.Picking can only begin when the goods are available. The picking date therefore depends on the material availability date.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder pickingTime(@Nullable LocalTime pickingTime)
Original property name from the Odata EDM: PickingTime
If the items in a delivery do not all have the same picking date, the system displays the earliest picking date in the delivery document header. You can use the picking data as a selection criterion for processing picking lists.Picking cannot begin until the goods are available. This means that the picking date depends on the material availability date.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder plannedGoodsIssueDate(@Nullable LocalDateTime plannedGoodsIssueDate)
Original property name from the Odata EDM: PlannedGoodsIssueDate
When the goods physically leave the shipping point, the system automatically creates a goods issue document to account for the outgoing inventory. The bill that you subsequently send to the customer must correspond to the movement of inventory. The goods issue date enables the accounting department to relate the movement of goods to the bill.The system automatically calculates the goods issue date by taking into account the following factors:The requested delivery dateThe pick/pack timeThe loading timeThe transit timeYou can change the date manually during delivery processing.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder proofOfDeliveryDate(@Nullable LocalDateTime proofOfDeliveryDate)
Original property name from the Odata EDM: ProofOfDeliveryDate
The POD date is the same as the verification date if the ship-to party verifies receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.However, if differences are reported, the POD date is set when manual confirmation occurs.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder proposedDeliveryRoute(@Nullable String proposedDeliveryRoute)
Original property name from the Odata EDM: ProposedDeliveryRoute
One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document.
to represent the following situations:this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder receivingPlant(@Nullable String receivingPlant)
Original property name from the Odata EDM: ReceivingPlant
How this field is filled and interpreted depends on the document category/delivery type. You can distinguish between the following cases:Delivery from stock transport orderRecipient of the delivery/ordering plant from the stock transportorderShipping notificationThe shipping notification may refer to several recipients. In thiscase, the field is empty.Rough goods receiptPlant for which you create the rough goods issue.For the remaining deliveries, the field contains the customer's plant number, provided that this customer has been maintained.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder routeSchedule(@Nullable String routeSchedule)
Original property name from the Odata EDM: RouteSchedule
You can use a route schedule to determine the day (Monday through Sunday) and the time when a customer delivery leaves the shipping point.You can define different route schedules in the system. The system can automatically propose a route schedule depending on the following criteria:the shipping point from which the delivery is sentthe ship-to party and the unloading point to which the delivery is sentthe transportation group of the deliverythe shipping condition of the deliverythe calender week in which the delivery leaves the shipping pointIn addition, you can use route schedules to create work packages from deliveries that are collectively processed in shipping, for example by using Process delivery in the picking transaction.
unloading points in one route.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder salesDistrict(@Nullable String salesDistrict)
Original property name from the Odata EDM: SalesDistrict
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder salesOffice(@Nullable String salesOffice)
Original property name from the Odata EDM: SalesOffice
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
products or services within a given geographical area.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder salesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
sales organization may include legal liability for products and customer claims.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder sDDocumentCategory(@Nullable String sDDocumentCategory)
Original property name from the Odata EDM: SDDocumentCategory
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
sales orders, deliveries, and invoices.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder shipmentBlockReason(@Nullable String shipmentBlockReason)
Original property name from the Odata EDM: ShipmentBlockReason
Deliveries for which as shipment blocking reason has been entered are not selected during a transportation planning run.You can enter a shipment blocking reason in the delivery. When you create a delivery, a shipment blocking reason is proposed on the basis of the delivery type.A delivery can be blocked for transportation planning until a quality control check has been performed.Returns should always be blocked for transportation planning.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder shippingCondition(@Nullable String shippingCondition)
Original property name from the Odata EDM: ShippingCondition
You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder shippingPoint(@Nullable String shippingPoint)
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.
item.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder shippingType(@Nullable String shippingType)
Original property name from the Odata EDM: ShippingType
During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
for the shipment legs.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder shipToParty(@Nullable String shipToParty)
Original property name from the Odata EDM: ShipToParty
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
orders.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder specialProcessingCode(@Nullable String specialProcessingCode)
Original property name from the Odata EDM: SpecialProcessingCode
You can search for the indicator using a matchcode and enter the selection data for the field.By setting the status "planned", the special processing indicator is copied from the respective deliveries into the shipment header, provided:the special processing indicator is the same in all deliveriesthe special processing indicator is not already filled in the shipment header
shipment costs. Examples for special processing are express shipments or special tariffs.this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder statisticsCurrency(@Nullable String statisticsCurrency)
Original property name from the Odata EDM: StatisticsCurrency
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder supplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder totalBlockStatus(@Nullable String totalBlockStatus)
Original property name from the Odata EDM: TotalBlockStatus
The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder totalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder totalNumberOfPackage(@Nullable String totalNumberOfPackage)
Original property name from the Odata EDM: TotalNumberOfPackage
The system determines the number of packages. It considers only packages at the highest level, i.e. packages that are not packed into another package.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder transportationGroup(@Nullable String transportationGroup)
Original property name from the Odata EDM: TransportationGroup
Transportation groups are used for automatic route scheduling during sales order and delivery note processing.Suppose that you sell food products, some of which are perishable and require refrigeration. You create a transportation group that includes all the products that need refrigerated trucks for delivery.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder transportationPlanningDate(@Nullable LocalDateTime transportationPlanningDate)
Original property name from the Odata EDM: TransportationPlanningDate
The system can propose the transportation scheduling date from predefined time estimates. Estimates may be based on the route. If items in a delivery have different transportation scheduling dates, the system displays the earliest date in the document header. You can change the date manually.If, for example, you plan to use an external carrier for trucking, you must arrange for a truck to be available when the goods are ready for loading.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder transportationPlanningStatus(@Nullable String transportationPlanningStatus)
Original property name from the Odata EDM: TransportationPlanningStatus
This characteristic controls the selection of deliveries to make up shipments in transportation planning. It is used a selection criterion for finding deliveries.The indicator is set by the system on the basis of the leg indicator (preliminary, subsequent, direct, return) in the headers of the shipment documents to which the delivery has been assigned.Blank - Not relevantDelivery is not to be processed in transportationplanning. This is the case when:- the delivery type is not relevant for transportation, or- the route is not relevant for transportation (only foroutbound deliveries; not required forinbound deliveries), or- a shipment block has been set in the delivery (only foroutbound deliveries: not required for inbound deliveries)A - Not yet plannedDelivery is to be processed in transportation planning.It has not yet been assigned to a shipment document.B - Partially plannedDelivery is to be processed in transportationplanning. The delivery has already beenassigned to at least one shipment document but thetransportation chain is not complete (see status C).C - Completely plannedDelivery has been assigned to one or moreshipment documents in transportation planning. Dependingon the leg indicator in each shipment header, the delivery isconsidered to be completely planned if- it exists in a direct leg or a return leg or- it exists in a preliminary, main, subsequent leg or- each stage assigned to the delivery connects to asubsequent stage, thus connecting the pointof departure with the destination of the delivery withno gaps in transportation (as of Release 4.6A).
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder transportationPlanningTime(@Nullable LocalTime transportationPlanningTime)
Original property name from the Odata EDM: TransportationPlanningTime
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder unloadingPointName(@Nullable String unloadingPointName)
Original property name from the Odata EDM: UnloadingPointName
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder warehouse(@Nullable String warehouse)
Original property name from the Odata EDM: Warehouse
All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder warehouseGate(@Nullable String warehouseGate)
Original property name from the Odata EDM: WarehouseGate
Doors can be defined for different purposes (both at the same and different times):for goods issuefor goods receiptfor cross docking processesfor flow-throughs
this.public OutbDeliveryHeader.OutbDeliveryHeaderBuilder warehouseStagingArea(@Nullable String warehouseStagingArea)
Original property name from the Odata EDM: WarehouseStagingArea
Staging areas can be used for different purposes (at the same time, if necessary):o Goods issueo Goods receipto Cross-docking processeso Direct distribution
this.public OutbDeliveryHeader build()
Copyright © 2020 SAP SE. All rights reserved.