SalesSchedgAgrmt.SalesSchedgAgrmtBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.salesschedulingagreement.SalesSchedgAgrmt.SalesSchedgAgrmtBuilder

Enclosing class:

SalesSchedgAgrmt
```
public static final class SalesSchedgAgrmt.SalesSchedgAgrmtBuilder
extends Object
```
Helper class to allow for fluent creation of SalesSchedgAgrmt instances.

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`agrmtValdtyEndDate(LocalDateTime agrmtValdtyEndDate)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`agrmtValdtyStartDate(LocalDateTime agrmtValdtyStartDate)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt`	`build()`
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`createdByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`creationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`creationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`customerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`customerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`customerPurchaseOrderType(String customerPurchaseOrderType)` Constraints: Not nullable, Maximum length: 4
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`deliveryBlockReason(String deliveryBlockReason)` Constraints: Not nullable, Maximum length: 2
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`delivSchedTypeMRPRlvnceCode(String delivSchedTypeMRPRlvnceCode)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`distributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`fiscalPeriod(String fiscalPeriod)` Constraints: Not nullable, Maximum length: 3
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`fiscalYear(String fiscalYear)` Constraints: Not nullable, Maximum length: 4
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`headerBillingBlockReason(String headerBillingBlockReason)` Constraints: Not nullable, Maximum length: 2
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`incotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`incotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`incotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`incotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`incotermsVersion(String incotermsVersion)` Constraints: Not nullable, Maximum length: 4
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`item(SalesSchedgAgrmtItem... value)` Navigation property to_Item for SalesSchedgAgrmt to multiple SalesSchedgAgrmtItem.
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`lastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`lastChangeDateTime(ZonedDateTime lastChangeDateTime)` Constraints: Not nullable, Precision: 7
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`lastChangedByUser(String lastChangedByUser)` Constraints: Not nullable, Maximum length: 12
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`matlUsageIndicator(String matlUsageIndicator)` Constraints: Not nullable, Maximum length: 3
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`organizationDivision(String organizationDivision)` Constraints: Not nullable, Maximum length: 2
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`overallBillingBlockStatus(String overallBillingBlockStatus)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`overallDeliveryBlockStatus(String overallDeliveryBlockStatus)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`overallDeliveryStatus(String overallDeliveryStatus)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`overallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`overallSDProcessStatus(String overallSDProcessStatus)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`partner(SalesSchedgAgrmtPartner... value)` Navigation property to_Partner for SalesSchedgAgrmt to multiple SalesSchedgAgrmtPartner.
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`paymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`pricingDate(LocalDateTime pricingDate)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`pricingElement(SalesSchedgAgrmtPrcgElement... value)` Navigation property to_PricingElement for SalesSchedgAgrmt to multiple SalesSchedgAgrmtPrcgElement.
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`purchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`salesDistrict(String salesDistrict)` Constraints: Not nullable, Maximum length: 6
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`salesGroup(String salesGroup)` Constraints: Not nullable, Maximum length: 3
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`salesOffice(String salesOffice)` Constraints: Not nullable, Maximum length: 4
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`salesOrganization(String salesOrganization)` Constraints: Not nullable, Maximum length: 4
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`salesSchedgAgrmtDate(LocalDateTime salesSchedgAgrmtDate)` Constraints: Not nullable, Precision: 0
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`salesSchedgAgrmtType(String salesSchedgAgrmtType)` Constraints: Not nullable, Maximum length: 4
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`salesSchedulingAgreement(String salesSchedulingAgreement)` (Key Field) Constraints: Not nullable, Maximum length: 10
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`sDDocumentReason(String sDDocumentReason)` Constraints: Not nullable, Maximum length: 3
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`shippingCondition(String shippingCondition)` Constraints: Not nullable, Maximum length: 2
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`shippingType(String shippingType)` Constraints: Not nullable, Maximum length: 2
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`soldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`text(SalesSchedgAgrmtText... value)` Navigation property to_Text for SalesSchedgAgrmt to multiple SalesSchedgAgrmtText.
`String`	`toString()`
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`totalBlockStatus(String totalBlockStatus)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`totalCreditCheckStatus(String totalCreditCheckStatus)` Constraints: Not nullable, Maximum length: 1
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`totalNetAmount(BigDecimal totalNetAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`transactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

- Method Detail
  - item
```
@Nonnull
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder item(SalesSchedgAgrmtItem... value)
```
    Navigation property to_Item for SalesSchedgAgrmt to multiple SalesSchedgAgrmtItem.
    
    Parameters:
    
    value - The SalesSchedgAgrmtItems to build this SalesSchedgAgrmt with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - partner
```
@Nonnull
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder partner(SalesSchedgAgrmtPartner... value)
```
    Navigation property to_Partner for SalesSchedgAgrmt to multiple SalesSchedgAgrmtPartner.
    
    Parameters:
    
    value - The SalesSchedgAgrmtPartners to build this SalesSchedgAgrmt with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - pricingElement
```
@Nonnull
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder pricingElement(SalesSchedgAgrmtPrcgElement... value)
```
    Navigation property to_PricingElement for SalesSchedgAgrmt to multiple SalesSchedgAgrmtPrcgElement.
    
    Parameters:
    
    value - The SalesSchedgAgrmtPrcgElements to build this SalesSchedgAgrmt with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - text
```
@Nonnull
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder text(SalesSchedgAgrmtText... value)
```
    Navigation property to_Text for SalesSchedgAgrmt to multiple SalesSchedgAgrmtText.
    
    Parameters:
    
    value - The SalesSchedgAgrmtTexts to build this SalesSchedgAgrmt with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - salesSchedulingAgreement
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder salesSchedulingAgreement(@Nullable
                                                                         String salesSchedulingAgreement)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesSchedulingAgreement
  - salesSchedgAgrmtType
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder salesSchedgAgrmtType(@Nullable
                                                                     String salesSchedgAgrmtType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesSchedgAgrmtType
  - createdByUser
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder createdByUser(@Nullable
                                                              String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
  - lastChangedByUser
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder lastChangedByUser(@Nullable
                                                                  String lastChangedByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: LastChangedByUser
  - creationDate
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder creationDate(@Nullable
                                                             LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
  - creationTime
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder creationTime(@Nullable
                                                             LocalTime creationTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
  - lastChangeDate
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder lastChangeDate(@Nullable
                                                               LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
  - lastChangeDateTime
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder lastChangeDateTime(@Nullable
                                                                   ZonedDateTime lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    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.
  - salesOrganization
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder salesOrganization(@Nullable
                                                                  String salesOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    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.
  - distributionChannel
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder distributionChannel(@Nullable
                                                                    String distributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - organizationDivision
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder organizationDivision(@Nullable
                                                                     String organizationDivision)
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - salesGroup
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder salesGroup(@Nullable
                                                           String salesGroup)
```
    Constraints: Not nullable, Maximum length: 3
    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.
  - salesOffice
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder salesOffice(@Nullable
                                                            String salesOffice)
```
    Constraints: Not nullable, Maximum length: 4
    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.
  - soldToParty
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder soldToParty(@Nullable
                                                            String soldToParty)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
  - salesSchedgAgrmtDate
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder salesSchedgAgrmtDate(@Nullable
                                                                     LocalDateTime salesSchedgAgrmtDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesSchedgAgrmtDate
    
    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.
  - sDDocumentReason
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder sDDocumentReason(@Nullable
                                                                 String sDDocumentReason)
```
    Constraints: Not nullable, Maximum length: 3
    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.
  - purchaseOrderByCustomer
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder purchaseOrderByCustomer(@Nullable
                                                                        String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    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).
  - customerPurchaseOrderType
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder customerPurchaseOrderType(@Nullable
                                                                          String customerPurchaseOrderType)
```
    Constraints: Not nullable, Maximum length: 4
    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.
  - customerPurchaseOrderDate
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder customerPurchaseOrderDate(@Nullable
                                                                          LocalDateTime customerPurchaseOrderDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CustomerPurchaseOrderDate
    the customer created the purchase order.
  - salesDistrict
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder salesDistrict(@Nullable
                                                              String salesDistrict)
```
    Constraints: Not nullable, Maximum length: 6
    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.
  - totalNetAmount
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder totalNetAmount(@Nullable
                                                               BigDecimal totalNetAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    account. The value is expressed in the document currency.
  - transactionCurrency
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder transactionCurrency(@Nullable
                                                                    String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    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.
  - pricingDate
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder pricingDate(@Nullable
                                                            LocalDateTime pricingDate)
```
    Constraints: Not nullable, Precision: 0
    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.
  - shippingType
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder shippingType(@Nullable
                                                             String shippingType)
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - shippingCondition
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder shippingCondition(@Nullable
                                                                  String shippingCondition)
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - incotermsVersion
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder incotermsVersion(@Nullable
                                                                 String incotermsVersion)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: IncotermsVersion
    defined by the International Chamber of Commerce (ICC).
  - incotermsClassification
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder incotermsClassification(@Nullable
                                                                        String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    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).
  - incotermsTransferLocation
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder incotermsTransferLocation(@Nullable
                                                                          String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    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").
  - incotermsLocation1
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder incotermsLocation1(@Nullable
                                                                   String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    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.
  - incotermsLocation2
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder incotermsLocation2(@Nullable
                                                                   String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    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:
  - deliveryBlockReason
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder deliveryBlockReason(@Nullable
                                                                    String deliveryBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - delivSchedTypeMRPRlvnceCode
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder delivSchedTypeMRPRlvnceCode(@Nullable
                                                                            String delivSchedTypeMRPRlvnceCode)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DelivSchedTypeMRPRlvnceCode
    
    The SAP System contains the following requirements planning settings:No delivery schedules are used.This indicator is default for all sales documents without delivery schedules.Only forecast delivery schedules are relevant for requirements planning. Forecast delivery schedules and JIT (just-in-time) delivery schedules are relevant for delivery, depending on their validity.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning and delivery, depending on their validity.Only forecast delivery schedules are relevant for requirements planning. Only JIT delivery schedules are relevant for delivery.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning, depending on their validity. Only JIT delivery schedules are relevant for delivery.JIT delivery schedules are not used.You have set material requirements planning indicator B (Forecast and JIT delivery schedules are relevant for requirements planning and delivery) in the scheduling agreement header. The forecast delivery schedule contains schedule lines from January 1 up to March 31. The JIT delivery schedule horizon covers the period up to January 31. The JIT delivery schedule is relevant for requirements planning and delivery within this horizon. As of February 1, the forecast delivery schedule is relevant for requirements planning and delivery.
    delivery.
  - agrmtValdtyStartDate
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder agrmtValdtyStartDate(@Nullable
                                                                     LocalDateTime agrmtValdtyStartDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: AgrmtValdtyStartDate
  - agrmtValdtyEndDate
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder agrmtValdtyEndDate(@Nullable
                                                                   LocalDateTime agrmtValdtyEndDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: AgrmtValdtyEndDate
  - matlUsageIndicator
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder matlUsageIndicator(@Nullable
                                                                   String matlUsageIndicator)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: MatlUsageIndicator
    
    The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.The same material, but with different uses, can be sold to the same customer in separate items or orders.Enter whether the material is:A spare, or replacement partA samplePart of a series, used in repetitive manufacturing
  - headerBillingBlockReason
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder headerBillingBlockReason(@Nullable
                                                                         String headerBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - customerPaymentTerms
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder customerPaymentTerms(@Nullable
                                                                     String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    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.
  - paymentMethod
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder paymentMethod(@Nullable
                                                              String paymentMethod)
```
    Constraints: Not nullable, Maximum length: 1
    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.
  - fiscalYear
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder fiscalYear(@Nullable
                                                           String fiscalYear)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: FiscalYear
    fiscal year can be the same as the calendar year, but does not have to be.
  - fiscalPeriod
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder fiscalPeriod(@Nullable
                                                             String fiscalPeriod)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: FiscalPeriod
    
    Every business transaction is allocated to a posting period. The monthly debits and credits of the different business transactions are accumulated per posting period.Examples of period classifications:Per calendar month -> 12 posting periodsEvery 4 weeks -> 13 posting periodsWeekly -> 52 or 53 posting periods
  - overallSDProcessStatus
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder overallSDProcessStatus(@Nullable
                                                                       String overallSDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    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.
  - overallSDDocumentRejectionSts
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder overallSDDocumentRejectionSts(@Nullable
                                                                              String overallSDDocumentRejectionSts)
```
    Constraints: Not nullable, Maximum length: 1
    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.
  - totalBlockStatus
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder totalBlockStatus(@Nullable
                                                                 String totalBlockStatus)
```
    Constraints: Not nullable, Maximum length: 1
    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
  - overallDeliveryStatus
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder overallDeliveryStatus(@Nullable
                                                                      String overallDeliveryStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryStatus
  - overallDeliveryBlockStatus
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder overallDeliveryBlockStatus(@Nullable
                                                                           String overallDeliveryBlockStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryBlockStatus
    
    Item delivery block status + Document header delivery block + user status for header
  - overallBillingBlockStatus
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder overallBillingBlockStatus(@Nullable
                                                                          String overallBillingBlockStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallBillingBlockStatus
    
    Billing block status of item + sales document billing block + user status header
  - totalCreditCheckStatus
```
public SalesSchedgAgrmt.SalesSchedgAgrmtBuilder totalCreditCheckStatus(@Nullable
                                                                       String totalCreditCheckStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalCreditCheckStatus
  - build
```
public SalesSchedgAgrmt build()
```
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class Object

Class SalesSchedgAgrmt.SalesSchedgAgrmtBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

item

partner

pricingElement

text

salesSchedulingAgreement

salesSchedgAgrmtType

createdByUser

lastChangedByUser

creationDate

creationTime

lastChangeDate

lastChangeDateTime

salesOrganization

distributionChannel

organizationDivision

salesGroup

salesOffice

soldToParty

salesSchedgAgrmtDate

sDDocumentReason

purchaseOrderByCustomer

customerPurchaseOrderType

customerPurchaseOrderDate

salesDistrict

totalNetAmount

transactionCurrency

pricingDate

shippingType

shippingCondition

incotermsVersion

incotermsClassification

incotermsTransferLocation

incotermsLocation1

incotermsLocation2

deliveryBlockReason

delivSchedTypeMRPRlvnceCode

agrmtValdtyStartDate

agrmtValdtyEndDate

matlUsageIndicator

headerBillingBlockReason

customerPaymentTerms

paymentMethod

fiscalYear

fiscalPeriod

overallSDProcessStatus

overallSDDocumentRejectionSts

totalBlockStatus

overallDeliveryStatus

overallDeliveryBlockStatus

overallBillingBlockStatus

totalCreditCheckStatus

build

toString