public static class CustSalesPartnerFunc.CustSalesPartnerFuncBuilder extends Object
public CustSalesPartnerFunc.CustSalesPartnerFuncBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public CustSalesPartnerFunc.CustSalesPartnerFuncBuilder 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 CustSalesPartnerFunc.CustSalesPartnerFuncBuilder 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 CustSalesPartnerFunc.CustSalesPartnerFuncBuilder division(@Nullable String division)
Original property name from the Odata EDM: Division
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 CustSalesPartnerFunc.CustSalesPartnerFuncBuilder partnerCounter(@Nullable String partnerCounter)
Original property name from the Odata EDM: PartnerCounter
When you create a sales order for a particular customer, there may be more than one ship-to party defined. The different ship-to parties are numbered sequentially.
partner function.public CustSalesPartnerFunc.CustSalesPartnerFuncBuilder partnerFunction(@Nullable String partnerFunction)
Original property name from the Odata EDM: PartnerFunction
public CustSalesPartnerFunc.CustSalesPartnerFuncBuilder bPCustomerNumber(@Nullable String bPCustomerNumber)
Original property name from the Odata EDM: BPCustomerNumber
public CustSalesPartnerFunc.CustSalesPartnerFuncBuilder customerPartnerDescription(@Nullable String customerPartnerDescription)
Original property name from the Odata EDM: CustomerPartnerDescription
The system uses this number to automatically determine the ship-to party.
public CustSalesPartnerFunc.CustSalesPartnerFuncBuilder defaultPartner(@Nullable Boolean defaultPartner)
Original property name from the Odata EDM: DefaultPartner
When you enter more than one partner for a particular partner function (for example, you define three different ship-to parties), you can select one partner as the default. During sales or purchasing processing, if you have defined multiple partners for a partner function, the system prompts you to choose just one partner. The system presents the default partner as the first choice in the pop-up window.
public CustSalesPartnerFunc.CustSalesPartnerFuncBuilder authorizationGroup(@Nullable String authorizationGroup)
Original property name from the Odata EDM: AuthorizationGroup
authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.public CustSalesPartnerFunc build()
Copyright © 2019 SAP SE. All rights reserved.