public class CustSalesPartnerFunc extends VdmEntity<CustSalesPartnerFunc>
Modifier and Type | Class and Description |
---|---|
static class |
CustSalesPartnerFunc.CustSalesPartnerFuncBuilder |
Modifier and Type | Field and Description |
---|---|
static CustSalesPartnerFuncSelectable |
ALL_FIELDS
Selector for all available fields of CustSalesPartnerFunc.
|
static CustSalesPartnerFuncField<String> |
AUTHORIZATION_GROUP
Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
|
static CustSalesPartnerFuncField<String> |
BP_CUSTOMER_NUMBER
Use with available fluent helpers to apply the BPCustomerNumber field to query operations.
|
static CustSalesPartnerFuncField<String> |
CUSTOMER
Use with available fluent helpers to apply the Customer field to query operations.
|
static CustSalesPartnerFuncField<String> |
CUSTOMER_PARTNER_DESCRIPTION
Use with available fluent helpers to apply the CustomerPartnerDescription field to query operations.
|
static CustSalesPartnerFuncField<Boolean> |
DEFAULT_PARTNER
Use with available fluent helpers to apply the DefaultPartner field to query operations.
|
static CustSalesPartnerFuncField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static CustSalesPartnerFuncField<String> |
DIVISION
Use with available fluent helpers to apply the Division field to query operations.
|
static CustSalesPartnerFuncField<String> |
PARTNER_COUNTER
Use with available fluent helpers to apply the PartnerCounter field to query operations.
|
static CustSalesPartnerFuncField<String> |
PARTNER_FUNCTION
Use with available fluent helpers to apply the PartnerFunction field to query operations.
|
static CustSalesPartnerFuncField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
Constructor and Description |
---|
CustSalesPartnerFunc() |
CustSalesPartnerFunc(String customer,
String salesOrganization,
String distributionChannel,
String division,
String partnerCounter,
String partnerFunction,
String bPCustomerNumber,
String customerPartnerDescription,
Boolean defaultPartner,
String authorizationGroup,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
static CustSalesPartnerFunc.CustSalesPartnerFuncBuilder |
builder() |
boolean |
equals(Object o) |
static <T> CustSalesPartnerFuncField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getAuthorizationGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getBPCustomerNumber()
Constraints: Not nullable, Maximum length: 10
|
String |
getCustomer()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerPartnerDescription()
Constraints: Not nullable, Maximum length: 30
|
Boolean |
getDefaultPartner()
Constraints: none
|
String |
getDistributionChannel()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
String |
getDivision()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getPartnerCounter()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getPartnerFunction()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
String |
getSalesOrganization()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
Class<CustSalesPartnerFunc> |
getType() |
int |
hashCode() |
void |
setAuthorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setBPCustomerNumber(String bPCustomerNumber)
Constraints: Not nullable, Maximum length: 10
|
void |
setCustomer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerPartnerDescription(String customerPartnerDescription)
Constraints: Not nullable, Maximum length: 30
|
void |
setDefaultPartner(Boolean defaultPartner)
Constraints: none
|
void |
setDistributionChannel(String distributionChannel)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
void |
setDivision(String division)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setPartnerCounter(String partnerCounter)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setPartnerFunction(String partnerFunction)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
void |
setSalesOrganization(String salesOrganization)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField
public static final CustSalesPartnerFuncSelectable ALL_FIELDS
public static final CustSalesPartnerFuncField<String> CUSTOMER
public static final CustSalesPartnerFuncField<String> SALES_ORGANIZATION
public static final CustSalesPartnerFuncField<String> DISTRIBUTION_CHANNEL
public static final CustSalesPartnerFuncField<String> DIVISION
public static final CustSalesPartnerFuncField<String> PARTNER_COUNTER
public static final CustSalesPartnerFuncField<String> PARTNER_FUNCTION
public static final CustSalesPartnerFuncField<String> BP_CUSTOMER_NUMBER
public static final CustSalesPartnerFuncField<String> CUSTOMER_PARTNER_DESCRIPTION
public static final CustSalesPartnerFuncField<Boolean> DEFAULT_PARTNER
public static final CustSalesPartnerFuncField<String> AUTHORIZATION_GROUP
@Generated(value="lombok") public CustSalesPartnerFunc()
@ConstructorProperties(value={"customer","salesOrganization","distributionChannel","division","partnerCounter","partnerFunction","bPCustomerNumber","customerPartnerDescription","defaultPartner","authorizationGroup","erpConfigContext"}) @Generated(value="lombok") public CustSalesPartnerFunc(@Nullable String customer, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String division, @Nullable String partnerCounter, @Nullable String partnerFunction, @Nullable String bPCustomerNumber, @Nullable String customerPartnerDescription, @Nullable Boolean defaultPartner, @Nullable String authorizationGroup, @Nullable ErpConfigContext erpConfigContext)
public Class<CustSalesPartnerFunc> getType()
getType
in class VdmObject<CustSalesPartnerFunc>
public static <T> CustSalesPartnerFuncField<T> field(String fieldName, Class<T> fieldType)
fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Generated(value="lombok") public static CustSalesPartnerFunc.CustSalesPartnerFuncBuilder builder()
@Nullable @Generated(value="lombok") public String getCustomer()
@Nullable @Generated(value="lombok") public String getSalesOrganization()
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.
@Nullable @Generated(value="lombok") public String getDistributionChannel()
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.
@Nullable @Generated(value="lombok") public String getDivision()
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.
@Nullable @Generated(value="lombok") public String getPartnerCounter()
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.
@Nullable @Generated(value="lombok") public String getPartnerFunction()
@Nullable @Generated(value="lombok") public String getBPCustomerNumber()
@Nullable @Generated(value="lombok") public String getCustomerPartnerDescription()
The system uses this number to automatically determine the ship-to party.
@Nullable @Generated(value="lombok") public Boolean getDefaultPartner()
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.
@Nullable @Generated(value="lombok") public String getAuthorizationGroup()
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setCustomer(@Nullable String customer)
customer
- @Generated(value="lombok") public void setSalesOrganization(@Nullable String 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.
salesOrganization
- @Generated(value="lombok") public void setDistributionChannel(@Nullable String 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.
distributionChannel
- @Generated(value="lombok") public void setDivision(@Nullable String 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.
division
- @Generated(value="lombok") public void setPartnerCounter(@Nullable String 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.
partnerCounter
- @Generated(value="lombok") public void setPartnerFunction(@Nullable String partnerFunction)
partnerFunction
- @Generated(value="lombok") public void setBPCustomerNumber(@Nullable String bPCustomerNumber)
bPCustomerNumber
- @Generated(value="lombok") public void setCustomerPartnerDescription(@Nullable String customerPartnerDescription)
The system uses this number to automatically determine the ship-to party.
customerPartnerDescription
- @Generated(value="lombok") public void setDefaultPartner(@Nullable Boolean 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.
defaultPartner
- @Generated(value="lombok") public void setAuthorizationGroup(@Nullable String authorizationGroup)
authorizationGroup
- @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext
- @Generated(value="lombok") public String toString()
toString
in class VdmObject<CustSalesPartnerFunc>
@Generated(value="lombok") public boolean equals(Object o)
equals
in class VdmObject<CustSalesPartnerFunc>
@Generated(value="lombok") public int hashCode()
hashCode
in class VdmObject<CustSalesPartnerFunc>
Copyright © 2018 SAP SE. All rights reserved.