public class CustomerSalesAreaTax extends VdmEntity<CustomerSalesAreaTax>
| Modifier and Type | Class and Description |
|---|---|
static class |
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
| Modifier and Type | Field and Description |
|---|---|
static CustomerSalesAreaTaxSelectable |
ALL_FIELDS
Selector for all available fields of CustomerSalesAreaTax.
|
static CustomerSalesAreaTaxField<String> |
CUSTOMER
Use with available fluent helpers to apply the Customer field to query operations.
|
static CustomerSalesAreaTaxField<String> |
CUSTOMER_TAX_CATEGORY
Use with available fluent helpers to apply the CustomerTaxCategory field to query operations.
|
static CustomerSalesAreaTaxField<String> |
CUSTOMER_TAX_CLASSIFICATION
Use with available fluent helpers to apply the CustomerTaxClassification field to query operations.
|
static CustomerSalesAreaTaxField<String> |
DEPARTURE_COUNTRY
Use with available fluent helpers to apply the DepartureCountry field to query operations.
|
static CustomerSalesAreaTaxField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static CustomerSalesAreaTaxField<String> |
DIVISION
Use with available fluent helpers to apply the Division field to query operations.
|
static CustomerSalesAreaTaxField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
| Constructor and Description |
|---|
CustomerSalesAreaTax() |
CustomerSalesAreaTax(String customer,
String salesOrganization,
String distributionChannel,
String division,
String departureCountry,
String customerTaxCategory,
String customerTaxClassification,
ErpConfigContext erpConfigContext) |
| Modifier and Type | Method and Description |
|---|---|
static CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
builder() |
boolean |
equals(Object o) |
static <T> CustomerSalesAreaTaxField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getCustomer()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerTaxCategory()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getCustomerTaxClassification()
Constraints: Not nullable, Maximum length: 1
|
String |
getDepartureCountry()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
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 |
getSalesOrganization()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
Class<CustomerSalesAreaTax> |
getType() |
int |
hashCode() |
void |
setCustomer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerTaxCategory(String customerTaxCategory)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setCustomerTaxClassification(String customerTaxClassification)
Constraints: Not nullable, Maximum length: 1
|
void |
setDepartureCountry(String departureCountry)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
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 |
setSalesOrganization(String salesOrganization)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final CustomerSalesAreaTaxSelectable ALL_FIELDS
public static final CustomerSalesAreaTaxField<String> CUSTOMER
public static final CustomerSalesAreaTaxField<String> SALES_ORGANIZATION
public static final CustomerSalesAreaTaxField<String> DISTRIBUTION_CHANNEL
public static final CustomerSalesAreaTaxField<String> DIVISION
public static final CustomerSalesAreaTaxField<String> DEPARTURE_COUNTRY
public static final CustomerSalesAreaTaxField<String> CUSTOMER_TAX_CATEGORY
public static final CustomerSalesAreaTaxField<String> CUSTOMER_TAX_CLASSIFICATION
@Generated(value="lombok") public CustomerSalesAreaTax()
@ConstructorProperties(value={"customer","salesOrganization","distributionChannel","division","departureCountry","customerTaxCategory","customerTaxClassification","erpConfigContext"}) @Generated(value="lombok") public CustomerSalesAreaTax(@Nullable String customer, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String division, @Nullable String departureCountry, @Nullable String customerTaxCategory, @Nullable String customerTaxClassification, @Nullable ErpConfigContext erpConfigContext)
public Class<CustomerSalesAreaTax> getType()
getType in class VdmObject<CustomerSalesAreaTax>public static <T> CustomerSalesAreaTaxField<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 CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder 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 specify one distribution channel as the source of customer and material master data for other distribution channels. You need then only to maintain the data in one place. Distrib.channel Ref.distrib.channel 01 01 02 01 03 01 04 04 In this example, only distribution channels 01 and 04 have customer and material master data defined. Distribution channels 01, 02, and 03 share the master data that you defined for distribution channel 01. Distribution channel 04 has its own master data. When you create a sales order in distribution channel 03, the system checks the customer and material master data against the data defined for distribution channel 01.
@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 getDepartureCountry()
You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key to help determine the relevant taxes during pricing determine important country-specific standards (the length of postal codes and bank account numbers, for example)
@Nullable @Generated(value="lombok") public String getCustomerTaxCategory()
You can define one or more tax categories for each country. During sales order processing, the system applies the tax category according to the geographical location of your delivering plant and the location of the customer receiving the goods tax classifications in the customer master record and the material master record. In the USA, for example, you can define tax categories for Federal Sales Tax and Federal Excise Tax. In the U.K., you can define a tax category for Value Added Tax (VAT).
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification()
You can use the tax classification to specify, for example, whether a customer is liable for sales taxes, such as VAT or state sales taxes. During sales order processing, the system copies the tax classification from the tax information stored in the customer master record of the payer, if the payer is different from the sold-to party and the sales tax identification number is maintained for the payer. ship to party, if the sales tax identification number of the ship-to party is maintained. sold-to party, if none of the criteria for the payer or the ship-to party are met. During pricing, the system calculates any relevant taxes by taking the following factors into account: The tax classification of the customer and the material The country keys of the customer and the delivering plant
@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 specify one distribution channel as the source of customer and material master data for other distribution channels. You need then only to maintain the data in one place. Distrib.channel Ref.distrib.channel 01 01 02 01 03 01 04 04 In this example, only distribution channels 01 and 04 have customer and material master data defined. Distribution channels 01, 02, and 03 share the master data that you defined for distribution channel 01. Distribution channel 04 has its own master data. When you create a sales order in distribution channel 03, the system checks the customer and material master data against the data defined for distribution channel 01.
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 setDepartureCountry(@Nullable String departureCountry)
You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key to help determine the relevant taxes during pricing determine important country-specific standards (the length of postal codes and bank account numbers, for example)
departureCountry - @Generated(value="lombok") public void setCustomerTaxCategory(@Nullable String customerTaxCategory)
You can define one or more tax categories for each country. During sales order processing, the system applies the tax category according to the geographical location of your delivering plant and the location of the customer receiving the goods tax classifications in the customer master record and the material master record. In the USA, for example, you can define tax categories for Federal Sales Tax and Federal Excise Tax. In the U.K., you can define a tax category for Value Added Tax (VAT).
customerTaxCategory - @Generated(value="lombok") public void setCustomerTaxClassification(@Nullable String customerTaxClassification)
You can use the tax classification to specify, for example, whether a customer is liable for sales taxes, such as VAT or state sales taxes. During sales order processing, the system copies the tax classification from the tax information stored in the customer master record of the payer, if the payer is different from the sold-to party and the sales tax identification number is maintained for the payer. ship to party, if the sales tax identification number of the ship-to party is maintained. sold-to party, if none of the criteria for the payer or the ship-to party are met. During pricing, the system calculates any relevant taxes by taking the following factors into account: The tax classification of the customer and the material The country keys of the customer and the delivering plant
customerTaxClassification - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<CustomerSalesAreaTax>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<CustomerSalesAreaTax>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<CustomerSalesAreaTax>Copyright © 2018 SAP SE. All rights reserved.