public static class SalesDocumentProposalItem.SalesDocumentProposalItemBuilder extends Object
@Nonnull public SalesDocumentProposalItem.SalesDocumentProposalItemBuilder 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 SalesDocumentProposalItem.SalesDocumentProposalItemBuilder 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 SalesDocumentProposalItem.SalesDocumentProposalItemBuilder 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 SalesDocumentProposalItem.SalesDocumentProposalItemBuilder 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 SalesDocumentProposalItem.SalesDocumentProposalItemBuilder 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 SalesDocumentProposalItem.SalesDocumentProposalItemBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
this
.@Nonnull public SalesDocumentProposalItem.SalesDocumentProposalItemBuilder salesDocumentType(@Nullable String salesDocumentType)
Original property name from the Odata EDM: SalesDocumentType
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.
this
.@Nonnull public SalesDocumentProposalItem.SalesDocumentProposalItemBuilder product(@Nullable String product)
Original property name from the Odata EDM: Product
this
.@Nonnull public SalesDocumentProposalItem.SalesDocumentProposalItemBuilder batch(@Nullable String batch)
Original property name from the Odata EDM: Batch
this
.@Nonnull public SalesDocumentProposalItem.SalesDocumentProposalItemBuilder orderQuantity(@Nullable BigDecimal orderQuantity)
Original property name from the Odata EDM: OrderQuantity
this
.@Nonnull public SalesDocumentProposalItem.SalesDocumentProposalItemBuilder orderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
this
.@Nonnull public SalesDocumentProposalItem build()
Copyright © 2021 SAP SE. All rights reserved.