public static final class CustProjSlsOrd.CustProjSlsOrdBuilder extends Object
| Modifier and Type | Method and Description |
|---|---|
CustProjSlsOrd |
build() |
CustProjSlsOrd.CustProjSlsOrdBuilder |
customerAccountAssignmentGroup(String customerAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
customerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
customerProject(String customerProject)
(Key Field) Constraints: Not nullable, Maximum length: 40
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
customerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)
Constraints: Not nullable, Precision: 0
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
custProjSlsOrdItem(CustProjSlsOrdItem... value)
Navigation property to_CustProjSlsOrdItem for CustProjSlsOrd to multiple
CustProjSlsOrdItem.
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
custProjSlsOrdText(CustProjSlsOrdText... value)
Navigation property to_CustProjSlsOrdText for CustProjSlsOrd to multiple
CustProjSlsOrdText.
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
distributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
headerBillingBlockReason(String headerBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
organizationDivision(String organizationDivision)
Constraints: Not nullable, Maximum length: 2
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
purchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
salesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
salesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
salesOrder(String salesOrder)
Constraints: Not nullable, Maximum length: 10
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
salesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
soldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
String |
toString() |
CustProjSlsOrd.CustProjSlsOrdBuilder |
totalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
CustProjSlsOrd.CustProjSlsOrdBuilder |
transactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
@Nonnull public CustProjSlsOrd.CustProjSlsOrdBuilder custProjSlsOrdItem(CustProjSlsOrdItem... value)
value - The CustProjSlsOrdItems to build this CustProjSlsOrd with.@Nonnull public CustProjSlsOrd.CustProjSlsOrdBuilder custProjSlsOrdText(CustProjSlsOrdText... value)
value - The CustProjSlsOrdTexts to build this CustProjSlsOrd with.public CustProjSlsOrd.CustProjSlsOrdBuilder customerProject(@Nullable String customerProject)
Original property name from the Odata EDM: CustomerProject
public CustProjSlsOrd.CustProjSlsOrdBuilder salesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
public CustProjSlsOrd.CustProjSlsOrdBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
orders.public CustProjSlsOrd.CustProjSlsOrdBuilder totalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
account. The value is expressed in the document currency.public CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd.CustProjSlsOrdBuilder customerPurchaseOrderDate(@Nullable LocalDateTime customerPurchaseOrderDate)
Original property name from the Odata EDM: CustomerPurchaseOrderDate
the customer created the purchase order.public CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd.CustProjSlsOrdBuilder 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.
public CustProjSlsOrd.CustProjSlsOrdBuilder 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.
public CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd.CustProjSlsOrdBuilder 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 CustProjSlsOrd build()
Copyright © 2019 SAP SE. All rights reserved.