public static final class SalesOrder.SalesOrderBuilder extends Object
Modifier and Type | Method and Description |
---|---|
SalesOrder.SalesOrderBuilder |
accountingDocExternalReference(String accountingDocExternalReference)
Constraints: Not nullable, Maximum length: 16
|
SalesOrder.SalesOrderBuilder |
accountingExchangeRate(BigDecimal accountingExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5
|
SalesOrder.SalesOrderBuilder |
additionalCustomerGroup1(String additionalCustomerGroup1)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
additionalCustomerGroup2(String additionalCustomerGroup2)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
additionalCustomerGroup3(String additionalCustomerGroup3)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
additionalCustomerGroup4(String additionalCustomerGroup4)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
additionalCustomerGroup5(String additionalCustomerGroup5)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
assignmentReference(String assignmentReference)
Constraints: Not nullable, Maximum length: 18
|
SalesOrder |
build() |
SalesOrder.SalesOrderBuilder |
completeDeliveryIsDefined(Boolean completeDeliveryIsDefined)
Constraints: none
|
SalesOrder.SalesOrderBuilder |
createdByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
SalesOrder.SalesOrderBuilder |
creationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
SalesOrder.SalesOrderBuilder |
customerAccountAssignmentGroup(String customerAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
customerGroup(String customerGroup)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
customerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
customerPriceGroup(String customerPriceGroup)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
customerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)
Constraints: Not nullable, Precision: 0
|
SalesOrder.SalesOrderBuilder |
customerPurchaseOrderType(String customerPurchaseOrderType)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification1(String customerTaxClassification1)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification2(String customerTaxClassification2)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification3(String customerTaxClassification3)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification4(String customerTaxClassification4)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification5(String customerTaxClassification5)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification6(String customerTaxClassification6)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification7(String customerTaxClassification7)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification8(String customerTaxClassification8)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
customerTaxClassification9(String customerTaxClassification9)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
deliveryBlockReason(String deliveryBlockReason)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
deliveryDateTypeRule(String deliveryDateTypeRule)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
distributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
externalDocumentID(String externalDocumentID)
Constraints: Not nullable, Maximum length: 40
|
SalesOrder.SalesOrderBuilder |
headerBillingBlockReason(String headerBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
incotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
incotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
SalesOrder.SalesOrderBuilder |
incotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
SalesOrder.SalesOrderBuilder |
incotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
SalesOrder.SalesOrderBuilder |
incotermsVersion(String incotermsVersion)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
item(SalesOrderItem... value)
Navigation property to_Item for SalesOrder to multiple SalesOrderItem.
|
SalesOrder.SalesOrderBuilder |
lastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
SalesOrder.SalesOrderBuilder |
lastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
SalesOrder.SalesOrderBuilder |
organizationDivision(String organizationDivision)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
overallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
overallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
overallTotalDeliveryStatus(String overallTotalDeliveryStatus)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
partner(SalesOrderHeaderPartner... value)
Navigation property to_Partner for SalesOrder to multiple SalesOrderHeaderPartner.
|
SalesOrder.SalesOrderBuilder |
paymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
paymentPlanItemDetails(SlsOrdPaymentPlanItemDetails... value)
Navigation property to_PaymentPlanItemDetails for SalesOrder to multiple
SlsOrdPaymentPlanItemDetails.
|
SalesOrder.SalesOrderBuilder |
priceListType(String priceListType)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
pricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
SalesOrder.SalesOrderBuilder |
pricingElement(SalesOrderHeaderPrElement... value)
Navigation property to_PricingElement for SalesOrder to multiple
SalesOrderHeaderPrElement.
|
SalesOrder.SalesOrderBuilder |
purchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
SalesOrder.SalesOrderBuilder |
purchaseOrderByShipToParty(String purchaseOrderByShipToParty)
Constraints: Not nullable, Maximum length: 35
|
SalesOrder.SalesOrderBuilder |
referenceSDDocument(String referenceSDDocument)
Constraints: Not nullable, Maximum length: 10
|
SalesOrder.SalesOrderBuilder |
referenceSDDocumentCategory(String referenceSDDocumentCategory)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
requestedDeliveryDate(LocalDateTime requestedDeliveryDate)
Constraints: Not nullable, Precision: 0
|
SalesOrder.SalesOrderBuilder |
salesDistrict(String salesDistrict)
Constraints: Not nullable, Maximum length: 6
|
SalesOrder.SalesOrderBuilder |
salesDocApprovalStatus(String salesDocApprovalStatus)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
salesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
salesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
salesOrder(String salesOrder)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
SalesOrder.SalesOrderBuilder |
salesOrderApprovalReason(String salesOrderApprovalReason)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
salesOrderDate(LocalDateTime salesOrderDate)
Constraints: Not nullable, Precision: 0
|
SalesOrder.SalesOrderBuilder |
salesOrderType(String salesOrderType)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
salesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
SalesOrder.SalesOrderBuilder |
sDDocumentReason(String sDDocumentReason)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
senderBusinessSystemName(String senderBusinessSystemName)
Constraints: Not nullable, Maximum length: 60
|
SalesOrder.SalesOrderBuilder |
shippingCondition(String shippingCondition)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
shippingType(String shippingType)
Constraints: Not nullable, Maximum length: 2
|
SalesOrder.SalesOrderBuilder |
slsDocIsRlvtForProofOfDeliv(Boolean slsDocIsRlvtForProofOfDeliv)
Constraints: none
|
SalesOrder.SalesOrderBuilder |
soldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
SalesOrder.SalesOrderBuilder |
taxDepartureCountry(String taxDepartureCountry)
Constraints: Not nullable, Maximum length: 3
|
SalesOrder.SalesOrderBuilder |
text(SalesOrderText... value)
Navigation property to_Text for SalesOrder to multiple SalesOrderText.
|
String |
toString() |
SalesOrder.SalesOrderBuilder |
totalCreditCheckStatus(String totalCreditCheckStatus)
Constraints: Not nullable, Maximum length: 1
|
SalesOrder.SalesOrderBuilder |
totalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
SalesOrder.SalesOrderBuilder |
transactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
SalesOrder.SalesOrderBuilder |
vATRegistrationCountry(String vATRegistrationCountry)
Constraints: Not nullable, Maximum length: 3
|
@Nonnull public SalesOrder.SalesOrderBuilder item(SalesOrderItem... value)
value
- The SalesOrderItems to build this SalesOrder with.@Nonnull public SalesOrder.SalesOrderBuilder partner(SalesOrderHeaderPartner... value)
value
- The SalesOrderHeaderPartners to build this SalesOrder with.@Nonnull public SalesOrder.SalesOrderBuilder paymentPlanItemDetails(SlsOrdPaymentPlanItemDetails... value)
value
- The SlsOrdPaymentPlanItemDetailss to build this SalesOrder with.@Nonnull public SalesOrder.SalesOrderBuilder pricingElement(SalesOrderHeaderPrElement... value)
value
- The SalesOrderHeaderPrElements to build this SalesOrder with.@Nonnull public SalesOrder.SalesOrderBuilder text(SalesOrderText... value)
value
- The SalesOrderTexts to build this SalesOrder with.@Nonnull public SalesOrder.SalesOrderBuilder salesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
this
.@Nonnull public SalesOrder.SalesOrderBuilder salesOrderType(@Nullable String salesOrderType)
Original property name from the Odata EDM: SalesOrderType
this
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder distributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
wholesale, retail, or direct sales.this
.@Nonnull public SalesOrder.SalesOrderBuilder organizationDivision(@Nullable String organizationDivision)
Original property name from the Odata EDM: OrganizationDivision
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
areas and the business areas for a material, product, or service.this
.@Nonnull public SalesOrder.SalesOrderBuilder salesGroup(@Nullable String salesGroup)
Original property name from the Odata EDM: SalesGroup
By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
this
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
orders.this
.@Nonnull public SalesOrder.SalesOrderBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this
.@Nonnull public SalesOrder.SalesOrderBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this
.@Nonnull public SalesOrder.SalesOrderBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
this
.@Nonnull public SalesOrder.SalesOrderBuilder senderBusinessSystemName(@Nullable String senderBusinessSystemName)
Original property name from the Odata EDM: SenderBusinessSystemName
this
.@Nonnull public SalesOrder.SalesOrderBuilder externalDocumentID(@Nullable String externalDocumentID)
Original property name from the Odata EDM: ExternalDocumentID
this
.@Nonnull public SalesOrder.SalesOrderBuilder lastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
this
.@Nonnull public SalesOrder.SalesOrderBuilder purchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
order).this
.@Nonnull public SalesOrder.SalesOrderBuilder purchaseOrderByShipToParty(@Nullable String purchaseOrderByShipToParty)
Original property name from the Odata EDM: PurchaseOrderByShipToParty
The number is the link between the end customer's purchase order and the sales documents that you have created. You can use the end customer's number for correspondence with the customer, in particular for finding certain document information. If the number refers to a purchase order, you can also print documents that you wish to send to the end customer, such as the delivery note.
purchase).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerPurchaseOrderType(@Nullable String customerPurchaseOrderType)
Original property name from the Odata EDM: CustomerPurchaseOrderType
You can record here whether the sales document arrived, for example, by telephone, mail, or fax.Enter one of the values predefined for your system.
this
.@Nonnull public SalesOrder.SalesOrderBuilder customerPurchaseOrderDate(@Nullable LocalDateTime customerPurchaseOrderDate)
Original property name from the Odata EDM: CustomerPurchaseOrderDate
the customer created the purchase order.this
.@Nonnull public SalesOrder.SalesOrderBuilder salesOrderDate(@Nullable LocalDateTime salesOrderDate)
Original property name from the Odata EDM: SalesOrderDate
When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected. You can define the document date to meet the needs of your organization.For sales orders, for example, you can define the document date as the date when the order actually arrives at your offices. Alternatively, you could define it as the date when the order was written up by a field sales representative.The system proposes the current date. You can change it manually in the sales document.
sales management purposes.this
.@Nonnull public SalesOrder.SalesOrderBuilder totalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
account. The value is expressed in the document currency.this
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder sDDocumentReason(@Nullable String sDDocumentReason)
Original property name from the Odata EDM: SDDocumentReason
You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria.Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason.If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
this
.@Nonnull public SalesOrder.SalesOrderBuilder pricingDate(@Nullable LocalDateTime pricingDate)
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
this
.@Nonnull public SalesOrder.SalesOrderBuilder requestedDeliveryDate(@Nullable LocalDateTime requestedDeliveryDate)
Original property name from the Odata EDM: RequestedDeliveryDate
this
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder completeDeliveryIsDefined(@Nullable Boolean completeDeliveryIsDefined)
Original property name from the Odata EDM: CompleteDeliveryIsDefined
can be partially delivered and completed over a number of deliveries.this
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder deliveryDateTypeRule(@Nullable String deliveryDateTypeRule)
Original property name from the Odata EDM: DeliveryDateTypeRule
You can choose one of the following options:The goods should be delivered on the requested delivery date or later. Note that there is no guarantee that the goods will not be delivered earlier.The goods must be delivered exactly on the confirmed delivery date.The goods must be delivered by the confirmed delivery date (that is, on the date or earlier).You can set the delivery date rule on header level to set a default for any items that you create afterwards.In Transportation Management (TM), this field has the following implications:If you want the goods to be delivered on the requested delivery date or later, the delivery date/time is used as the earliest requested delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered on the confirmed delivery date, the start of the delivery date is used as the earliest acceptable delivery date/time and the end of the delivery date as the latest acceptable delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered by the confirmed delivery date, the end of the delivery date is used as the latest acceptable delivery date/time of the freight unit which contains the sales order item.Note: If you want to the goods to be delivered on or by the confirmed delivery date, the system ignores the rule for pick-up and delivery window and the condition for pick-up and delivery window determination which you have defined in the freight unit type for the delivery stop.
this
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder incotermsLocation1(@Nullable String incotermsLocation1)
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
this
.@Nonnull public SalesOrder.SalesOrderBuilder incotermsLocation2(@Nullable String incotermsLocation2)
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
customized appropriately). Note the following for the incoterms versions below:this
.@Nonnull public SalesOrder.SalesOrderBuilder incotermsVersion(@Nullable String incotermsVersion)
Original property name from the Odata EDM: IncotermsVersion
defined by the International Chamber of Commerce (ICC).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerPriceGroup(@Nullable String customerPriceGroup)
Original property name from the Odata EDM: CustomerPriceGroup
You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.
this
.@Nonnull public SalesOrder.SalesOrderBuilder priceListType(@Nullable String priceListType)
Original property name from the Odata EDM: PriceListType
You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.
this
.@Nonnull public SalesOrder.SalesOrderBuilder customerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
this
.@Nonnull public SalesOrder.SalesOrderBuilder paymentMethod(@Nullable String paymentMethod)
Original property name from the Odata EDM: PaymentMethod
If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
this
.@Nonnull public SalesOrder.SalesOrderBuilder assignmentReference(@Nullable String assignmentReference)
Original property name from the Odata EDM: AssignmentReference
The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document.
this
.@Nonnull public SalesOrder.SalesOrderBuilder referenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
this
.@Nonnull public SalesOrder.SalesOrderBuilder referenceSDDocumentCategory(@Nullable String referenceSDDocumentCategory)
Original property name from the Odata EDM: ReferenceSDDocumentCategory
this
.@Nonnull public SalesOrder.SalesOrderBuilder accountingDocExternalReference(@Nullable String accountingDocExternalReference)
Original property name from the Odata EDM: AccountingDocExternalReference
The reference document number serves as a search criterion when displaying or changing documents. In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document.
this
.@Nonnull public SalesOrder.SalesOrderBuilder customerAccountAssignmentGroup(@Nullable String customerAccountAssignmentGroup)
Original property name from the Odata EDM: CustomerAccountAssignmentGroup
The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
this
.@Nonnull public SalesOrder.SalesOrderBuilder accountingExchangeRate(@Nullable BigDecimal accountingExchangeRate)
Original property name from the Odata EDM: AccountingExchangeRate
Your system is configured in such a way that it expects:No prefix (leading sign) for direct ratesA "" as prefix (leading sign) for direct ratesNo prefix for indirect ratesA "" as prefix for indirect rates
this
.@Nonnull public SalesOrder.SalesOrderBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.this
.@Nonnull public SalesOrder.SalesOrderBuilder additionalCustomerGroup1(@Nullable String additionalCustomerGroup1)
Original property name from the Odata EDM: AdditionalCustomerGroup1
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public SalesOrder.SalesOrderBuilder additionalCustomerGroup2(@Nullable String additionalCustomerGroup2)
Original property name from the Odata EDM: AdditionalCustomerGroup2
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public SalesOrder.SalesOrderBuilder additionalCustomerGroup3(@Nullable String additionalCustomerGroup3)
Original property name from the Odata EDM: AdditionalCustomerGroup3
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public SalesOrder.SalesOrderBuilder additionalCustomerGroup4(@Nullable String additionalCustomerGroup4)
Original property name from the Odata EDM: AdditionalCustomerGroup4
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public SalesOrder.SalesOrderBuilder additionalCustomerGroup5(@Nullable String additionalCustomerGroup5)
Original property name from the Odata EDM: AdditionalCustomerGroup5
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public SalesOrder.SalesOrderBuilder slsDocIsRlvtForProofOfDeliv(@Nullable Boolean slsDocIsRlvtForProofOfDeliv)
Original property name from the Odata EDM: SlsDocIsRlvtForProofOfDeliv
this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification1(@Nullable String customerTaxClassification1)
Original property name from the Odata EDM: CustomerTaxClassification1
The system copies the tax classification from the tax information stored in the customer master record of the goods recipient. During pricing, the system uses the tax classification and the country key (which identifies the customer location) to determine the relevant taxes. You can enter a different (alternative) tax classification in the order.
value-added tax).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification2(@Nullable String customerTaxClassification2)
Original property name from the Odata EDM: CustomerTaxClassification2
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification3(@Nullable String customerTaxClassification3)
Original property name from the Odata EDM: CustomerTaxClassification3
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification4(@Nullable String customerTaxClassification4)
Original property name from the Odata EDM: CustomerTaxClassification4
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification5(@Nullable String customerTaxClassification5)
Original property name from the Odata EDM: CustomerTaxClassification5
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification6(@Nullable String customerTaxClassification6)
Original property name from the Odata EDM: CustomerTaxClassification6
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification7(@Nullable String customerTaxClassification7)
Original property name from the Odata EDM: CustomerTaxClassification7
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification8(@Nullable String customerTaxClassification8)
Original property name from the Odata EDM: CustomerTaxClassification8
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder customerTaxClassification9(@Nullable String customerTaxClassification9)
Original property name from the Odata EDM: CustomerTaxClassification9
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.@Nonnull public SalesOrder.SalesOrderBuilder taxDepartureCountry(@Nullable String taxDepartureCountry)
Original property name from the Odata EDM: TaxDepartureCountry
A different country needs to be entered for certain internal European transactions (chain transactions).
this
.@Nonnull public SalesOrder.SalesOrderBuilder vATRegistrationCountry(@Nullable String vATRegistrationCountry)
Original property name from the Odata EDM: VATRegistrationCountry
A different country needs to be entered for certain internal European transactions (chain transactions).
this
.@Nonnull public SalesOrder.SalesOrderBuilder salesOrderApprovalReason(@Nullable String salesOrderApprovalReason)
Original property name from the Odata EDM: SalesOrderApprovalReason
Whenever an approval request reason is set and the corresponding workflow is defined, the sales document is considered relevant for approvals. The approval request reason consists of an ID and a description.You define that for customer ABC, sales quotations always have to be approved. The system automatically sets this reason when a sales quotation for this customer is created. It cannot be released without sending it to an approver first.
this
.@Nonnull public SalesOrder.SalesOrderBuilder salesDocApprovalStatus(@Nullable String salesDocApprovalStatus)
Original property name from the Odata EDM: SalesDocApprovalStatus
this
.@Nonnull public SalesOrder.SalesOrderBuilder 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
.@Nonnull public SalesOrder.SalesOrderBuilder totalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
this
.@Nonnull public SalesOrder.SalesOrderBuilder overallTotalDeliveryStatus(@Nullable String overallTotalDeliveryStatus)
Original property name from the Odata EDM: OverallTotalDeliveryStatus
this
.@Nonnull public SalesOrder.SalesOrderBuilder overallSDDocumentRejectionSts(@Nullable String overallSDDocumentRejectionSts)
Original property name from the Odata EDM: OverallSDDocumentRejectionSts
The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
this
.@Nonnull public SalesOrder build()
Copyright © 2020 SAP SE. All rights reserved.