public static class CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder extends Object
| Modifier and Type | Method and Description |
|---|---|
CustomerSalesAreaTax |
build() |
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
customer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
customerTaxCategory(String customerTaxCategory)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
customerTaxClassification(String customerTaxClassification)
Constraints: Not nullable, Maximum length: 1
|
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
departureCountry(String departureCountry)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
distributionChannel(String distributionChannel)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
division(String division)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder |
salesOrganization(String salesOrganization)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
toString() |
public CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder 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 CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder distributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: 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.channel01 0102 0103 0104 04In 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.
data for other distribution channels.public CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder 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 CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder departureCountry(@Nullable String departureCountry)
Original property name from the Odata EDM: 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 tohelp determine the relevant taxes during pricingdetermine important country-specific standards (the length of postal codes and bank account numbers, for example)
public CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder customerTaxCategory(@Nullable String customerTaxCategory)
Original property name from the Odata EDM: CustomerTaxCategory
You can define one or more tax categories for each country. During sales order processing, the system applies the tax category according tothe geographical location of your delivering plant and the location of the customer receiving the goodstax 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).
pricing.public CustomerSalesAreaTax.CustomerSalesAreaTaxBuilder customerTaxClassification(@Nullable String customerTaxClassification)
Original property name from the Odata EDM: 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 thecustomer 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 materialThe country keys of the customer and the delivering plant
public CustomerSalesAreaTax build()
Copyright © 2019 SAP SE. All rights reserved.