public static final class SalesContract.SalesContractBuilder extends Object
| Modifier and Type | Method and Description |
|---|---|
SalesContract |
build() |
SalesContract.SalesContractBuilder |
contractManualCompletion(String contractManualCompletion)
Constraints: Not nullable, Maximum length: 1
|
SalesContract.SalesContractBuilder |
createdByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
SalesContract.SalesContractBuilder |
creationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
customerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
customerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
customerPurchaseOrderType(String customerPurchaseOrderType)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
distributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
SalesContract.SalesContractBuilder |
incotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
SalesContract.SalesContractBuilder |
incotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
SalesContract.SalesContractBuilder |
incotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
SalesContract.SalesContractBuilder |
incotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
SalesContract.SalesContractBuilder |
incotermsVersion(String incotermsVersion)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
item(SalesContractItem... value)
Navigation property to_Item for SalesContract to multiple SalesContractItem.
|
SalesContract.SalesContractBuilder |
lastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
lastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
SalesContract.SalesContractBuilder |
nmbrOfSalesContractValdtyPerd(String nmbrOfSalesContractValdtyPerd)
Constraints: Not nullable, Maximum length: 3
|
SalesContract.SalesContractBuilder |
organizationDivision(String organizationDivision)
Constraints: Not nullable, Maximum length: 2
|
SalesContract.SalesContractBuilder |
overallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)
Constraints: Not nullable, Maximum length: 1
|
SalesContract.SalesContractBuilder |
overallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
SalesContract.SalesContractBuilder |
partner(SalesContractPartner... value)
Navigation property to_Partner for SalesContract to multiple SalesContractPartner.
|
SalesContract.SalesContractBuilder |
paymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
SalesContract.SalesContractBuilder |
pricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
pricingElement(SalesContractPrcgElmnt... value)
Navigation property to_PricingElement for SalesContract to multiple
SalesContractPrcgElmnt.
|
SalesContract.SalesContractBuilder |
purchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
SalesContract.SalesContractBuilder |
referenceSDDocument(String referenceSDDocument)
Constraints: Not nullable, Maximum length: 10
|
SalesContract.SalesContractBuilder |
referenceSDDocumentCategory(String referenceSDDocumentCategory)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
salesContract(String salesContract)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
SalesContract.SalesContractBuilder |
salesContractDate(LocalDateTime salesContractDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
salesContractFollowUpAction(String salesContractFollowUpAction)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
salesContractSignedDate(LocalDateTime salesContractSignedDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
salesContractType(String salesContractType)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
salesContractValidityEndDate(LocalDateTime salesContractValidityEndDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
salesContractValidityPerdCat(String salesContractValidityPerdCat)
Constraints: Not nullable, Maximum length: 2
|
SalesContract.SalesContractBuilder |
salesContractValidityPerdUnit(String salesContractValidityPerdUnit)
Constraints: Not nullable, Maximum length: 1
|
SalesContract.SalesContractBuilder |
salesContractValidityStartDate(LocalDateTime salesContractValidityStartDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
salesDistrict(String salesDistrict)
Constraints: Not nullable, Maximum length: 6
|
SalesContract.SalesContractBuilder |
salesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
SalesContract.SalesContractBuilder |
salesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
salesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
SalesContract.SalesContractBuilder |
sDDocumentReason(String sDDocumentReason)
Constraints: Not nullable, Maximum length: 3
|
SalesContract.SalesContractBuilder |
slsContractFollowUpActionDate(LocalDateTime slsContractFollowUpActionDate)
Constraints: Not nullable, Precision: 0
|
SalesContract.SalesContractBuilder |
soldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
String |
toString() |
SalesContract.SalesContractBuilder |
totalCreditCheckStatus(String totalCreditCheckStatus)
Constraints: Not nullable, Maximum length: 1
|
SalesContract.SalesContractBuilder |
totalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
SalesContract.SalesContractBuilder |
transactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
@Nonnull public SalesContract.SalesContractBuilder item(SalesContractItem... value)
value - The SalesContractItems to build this SalesContract with.@Nonnull public SalesContract.SalesContractBuilder partner(SalesContractPartner... value)
value - The SalesContractPartners to build this SalesContract with.@Nonnull public SalesContract.SalesContractBuilder pricingElement(SalesContractPrcgElmnt... value)
value - The SalesContractPrcgElmnts to build this SalesContract with.public SalesContract.SalesContractBuilder salesContract(@Nullable String salesContract)
Original property name from the Odata EDM: SalesContract
public SalesContract.SalesContractBuilder salesContractType(@Nullable String salesContractType)
Original property name from the Odata EDM: SalesContractType
The sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for.
public SalesContract.SalesContractBuilder 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.public SalesContract.SalesContractBuilder 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.public SalesContract.SalesContractBuilder 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.public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder 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.public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
orders.public SalesContract.SalesContractBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
public SalesContract.SalesContractBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
public SalesContract.SalesContractBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder 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).public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder customerPurchaseOrderDate(@Nullable LocalDateTime customerPurchaseOrderDate)
Original property name from the Odata EDM: CustomerPurchaseOrderDate
the customer created the purchase order.public SalesContract.SalesContractBuilder salesContractDate(@Nullable LocalDateTime salesContractDate)
Original property name from the Odata EDM: SalesContractDate
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.public SalesContract.SalesContractBuilder totalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
account. The value is expressed in the document currency.public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder 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).public SalesContract.SalesContractBuilder 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").
public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder 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:public SalesContract.SalesContractBuilder incotermsVersion(@Nullable String incotermsVersion)
Original property name from the Odata EDM: IncotermsVersion
defined by the International Chamber of Commerce (ICC).public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder salesContractValidityStartDate(@Nullable LocalDateTime salesContractValidityStartDate)
Original property name from the Odata EDM: SalesContractValidityStartDate
an outline agreement ora product proposalThe outline agreement or product proposal is valid after this date. The beginning date and the end date together define the validity period.For more information about the impact of validity periods on scheduling agreements, please refer to SAP Note 914607.
public SalesContract.SalesContractBuilder salesContractValidityEndDate(@Nullable LocalDateTime salesContractValidityEndDate)
Original property name from the Odata EDM: SalesContractValidityEndDate
An outline agreement orA product proposalAfter this date the outline agreement or the product proposal is no longer valid.The beginning date and the end date together define the validity period. The validity period affects processing. If, for example, you are processing a scheduling agreement, you can only deliver a schedule line if its requested delivery date falls within the validity period of the outline agreement.
public SalesContract.SalesContractBuilder salesContractValidityPerdUnit(@Nullable String salesContractValidityPerdUnit)
Original property name from the Odata EDM: SalesContractValidityPerdUnit
public SalesContract.SalesContractBuilder salesContractValidityPerdCat(@Nullable String salesContractValidityPerdCat)
Original property name from the Odata EDM: SalesContractValidityPerdCat
on).public SalesContract.SalesContractBuilder salesContractSignedDate(@Nullable LocalDateTime salesContractSignedDate)
Original property name from the Odata EDM: SalesContractSignedDate
The date you enter can be used as a baseline date for determining other dates in the contract.You want the contract to become valid on the day it is signed by the customer. You enter a date rule for the contract start date which has the date on which the contract is signed as its baseline date. When you enter the date on which the contract was signed in the contract, the system automatically makes the appropriate entry in the contract start date field.
public SalesContract.SalesContractBuilder nmbrOfSalesContractValdtyPerd(@Nullable String nmbrOfSalesContractValdtyPerd)
Original property name from the Odata EDM: NmbrOfSalesContractValdtyPerd
public SalesContract.SalesContractBuilder salesContractFollowUpAction(@Nullable String salesContractFollowUpAction)
Original property name from the Odata EDM: SalesContractFollowUpAction
Creating a contractCreating a quotationCreating a sales activity such as a telephone callSending an internal electronic mail
public SalesContract.SalesContractBuilder slsContractFollowUpActionDate(@Nullable LocalDateTime slsContractFollowUpActionDate)
Original property name from the Odata EDM: SlsContractFollowUpActionDate
The contract will be included in the worklist for contracts with follow-up actions whenThe date you enter in this field lies within the selection period you define for the worklistThe contract fulfills the other selection criteria you define for the worklist.You reach the selection screen for the worklist for contracts with follow-up actions by choosing Outline agreements -> Contracts -> Subsequent functions -> Follow-up actions.
public SalesContract.SalesContractBuilder contractManualCompletion(@Nullable String contractManualCompletion)
Original property name from the Odata EDM: ContractManualCompletion
public SalesContract.SalesContractBuilder referenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
public SalesContract.SalesContractBuilder referenceSDDocumentCategory(@Nullable String referenceSDDocumentCategory)
Original property name from the Odata EDM: ReferenceSDDocumentCategory
public SalesContract.SalesContractBuilder 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.
public SalesContract.SalesContractBuilder totalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
public SalesContract.SalesContractBuilder 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.
public SalesContract build()
Copyright © 2019 SAP SE. All rights reserved.