public static final class CustomerSalesArea.CustomerSalesAreaBuilder extends Object
Modifier and Type | Method and Description |
---|---|
CustomerSalesArea.CustomerSalesAreaBuilder |
accountByCustomer(String accountByCustomer)
Constraints: Not nullable, Maximum length: 12
|
CustomerSalesArea.CustomerSalesAreaBuilder |
additionalCustomerGroup1(String additionalCustomerGroup1)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
additionalCustomerGroup2(String additionalCustomerGroup2)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
additionalCustomerGroup3(String additionalCustomerGroup3)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
additionalCustomerGroup4(String additionalCustomerGroup4)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
additionalCustomerGroup5(String additionalCustomerGroup5)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
authorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
billingIsBlockedForCustomer(String billingIsBlockedForCustomer)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea |
build() |
CustomerSalesArea.CustomerSalesAreaBuilder |
completeDeliveryIsDefined(Boolean completeDeliveryIsDefined)
Constraints: none
|
CustomerSalesArea.CustomerSalesAreaBuilder |
currency(String currency)
Constraints: Not nullable, Maximum length: 5
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customerABCClassification(String customerABCClassification)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customerAccountAssignmentGroup(String customerAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customerAccountGroup(String customerAccountGroup)
Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customerGroup(String customerGroup)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customerPriceGroup(String customerPriceGroup)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
customerPricingProcedure(String customerPricingProcedure)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
deletionIndicator(Boolean deletionIndicator)
Constraints: none
|
CustomerSalesArea.CustomerSalesAreaBuilder |
deliveryIsBlockedForCustomer(String deliveryIsBlockedForCustomer)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
deliveryPriority(String deliveryPriority)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
distributionChannel(String distributionChannel)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
division(String division)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
exchangeRateType(String exchangeRateType)
Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
incotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
incotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
CustomerSalesArea.CustomerSalesAreaBuilder |
incotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
CustomerSalesArea.CustomerSalesAreaBuilder |
incotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
CustomerSalesArea.CustomerSalesAreaBuilder |
incotermsVersion(String incotermsVersion)
Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
invoiceDate(String invoiceDate)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
invoiceListSchedule(String invoiceListSchedule)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
itemOrderProbabilityInPercent(String itemOrderProbabilityInPercent)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
orderCombinationIsAllowed(Boolean orderCombinationIsAllowed)
Constraints: none
|
CustomerSalesArea.CustomerSalesAreaBuilder |
orderIsBlockedForCustomer(String orderIsBlockedForCustomer)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
partialDeliveryIsAllowed(String partialDeliveryIsAllowed)
Constraints: Not nullable, Maximum length: 1
|
CustomerSalesArea.CustomerSalesAreaBuilder |
partnerFunction(CustSalesPartnerFunc... value)
Navigation property to_PartnerFunction for CustomerSalesArea to multiple
CustSalesPartnerFunc.
|
CustomerSalesArea.CustomerSalesAreaBuilder |
paymentGuaranteeProcedure(String paymentGuaranteeProcedure)
Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
priceListType(String priceListType)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
salesAreaTax(CustomerSalesAreaTax... value)
Navigation property to_SalesAreaTax for CustomerSalesArea to multiple
CustomerSalesAreaTax.
|
CustomerSalesArea.CustomerSalesAreaBuilder |
salesAreaText(CustomerSalesAreaText... value)
Navigation property to_SalesAreaText for CustomerSalesArea to multiple
CustomerSalesAreaText.
|
CustomerSalesArea.CustomerSalesAreaBuilder |
salesDistrict(String salesDistrict)
Constraints: Not nullable, Maximum length: 6
|
CustomerSalesArea.CustomerSalesAreaBuilder |
salesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
CustomerSalesArea.CustomerSalesAreaBuilder |
salesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
salesOrganization(String salesOrganization)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
CustomerSalesArea.CustomerSalesAreaBuilder |
shippingCondition(String shippingCondition)
Constraints: Not nullable, Maximum length: 2
|
CustomerSalesArea.CustomerSalesAreaBuilder |
supplyingPlant(String supplyingPlant)
Constraints: Not nullable, Maximum length: 4
|
String |
toString() |
@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder partnerFunction(CustSalesPartnerFunc... value)
value
- The CustSalesPartnerFuncs to build this CustomerSalesArea with.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder salesAreaTax(CustomerSalesAreaTax... value)
value
- The CustomerSalesAreaTaxs to build this CustomerSalesArea with.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder salesAreaText(CustomerSalesAreaText... value)
value
- The CustomerSalesAreaTexts to build this CustomerSalesArea with.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder 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 CustomerSalesArea.CustomerSalesAreaBuilder 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 CustomerSalesArea.CustomerSalesAreaBuilder 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.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder accountByCustomer(@Nullable String accountByCustomer)
Original property name from the Odata EDM: AccountByCustomer
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder authorizationGroup(@Nullable String authorizationGroup)
Original property name from the Odata EDM: AuthorizationGroup
In order to carry out a specific activity, the user must have authorization for the combination of the activity and the authorization group.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder billingIsBlockedForCustomer(@Nullable String billingIsBlockedForCustomer)
Original property name from the Odata EDM: BillingIsBlockedForCustomer
If you enter a blocking indicator, billing that is already underway is continued. However, you cannot process the document further.Enter one of the values predefined for your system. If you want to block billing for a customer throughout an entire sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block billing for a customer if, for example, there are credit-related or legal problems to be resolved.
specified sales area.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder completeDeliveryIsDefined(@Nullable Boolean completeDeliveryIsDefined)
Original property name from the Odata EDM: CompleteDeliveryIsDefined
can be partially delivered and completed over a number of deliveries.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder currency(@Nullable String currency)
Original property name from the Odata EDM: Currency
given sales organization.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customerABCClassification(@Nullable String customerABCClassification)
Original property name from the Odata EDM: CustomerABCClassification
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customerAccountAssignmentGroup(@Nullable String customerAccountAssignmentGroup)
Original property name from the Odata EDM: CustomerAccountAssignmentGroup
The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customerPriceGroup(@Nullable String customerPriceGroup)
Original property name from the Odata EDM: CustomerPriceGroup
You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customerPricingProcedure(@Nullable String customerPricingProcedure)
Original property name from the Odata EDM: CustomerPricingProcedure
You can define different pricing procedures for your system. A pricing procedure determines the type and sequence of conditions that the system uses for pricing in, for example, a sales order.
customer.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder deliveryIsBlockedForCustomer(@Nullable String deliveryIsBlockedForCustomer)
Original property name from the Odata EDM: DeliveryIsBlockedForCustomer
If you enter a blocking indicator, delivery processing that is already underway is continued. However, no new processing can take place.Enter one of the values predefined for your system. If you want to block delivery processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block delivery processing for a customer if, for example, there are credit-related or legal problems to be resolved.
specified sales area.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder deliveryPriority(@Nullable String deliveryPriority)
Original property name from the Odata EDM: DeliveryPriority
You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder incotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
Commerce (ICC).this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder incotermsLocation2(@Nullable String incotermsLocation2)
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
customized appropriately). Note the following for the incoterms versions below:this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder incotermsVersion(@Nullable String incotermsVersion)
Original property name from the Odata EDM: IncotermsVersion
defined by the International Chamber of Commerce (ICC).this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder incotermsLocation1(@Nullable String incotermsLocation1)
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder deletionIndicator(@Nullable Boolean deletionIndicator)
Original property name from the Odata EDM: DeletionIndicator
deletion is made, the system checks for dependent data that would prevent the deletion.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder incotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder invoiceDate(@Nullable String invoiceDate)
Original property name from the Odata EDM: InvoiceDate
If, for example, a customer wants to consolidate the invoices you send out, you can predefine the billing schedule in a calendar in the system. During billing, the system automatically proposes the appropriate billing date from the calendar.The system proposes the billing schedule from the customer master record of the payer. You can change the value manually in the sales document.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder itemOrderProbabilityInPercent(@Nullable String itemOrderProbabilityInPercent)
Original property name from the Odata EDM: ItemOrderProbabilityInPercent
The system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values. In this case, the system takes 50% of 80% and proposes 40% for the item.The system proposes the probability. You can change the value manually for the item.You can generate requirements from quotations. Accordingly, the probability of quotation items affects how requirements are passed on. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.
part of a sales order.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder orderCombinationIsAllowed(@Nullable Boolean orderCombinationIsAllowed)
Original property name from the Odata EDM: OrderCombinationIsAllowed
The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder orderIsBlockedForCustomer(@Nullable String orderIsBlockedForCustomer)
Original property name from the Odata EDM: OrderIsBlockedForCustomer
You can define blocks according to the needs of your organization. If you enter a blocking indicator, sales order processing that is already underway is continued. However, no new processing can occur.Enter one of the values predefined for your system. If you want to block sales order processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sale organization is defined.You can block sales order processing for a customer if, for example, there are credit-related or legal problems to be resolved.
specified sales area.this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder partialDeliveryIsAllowed(@Nullable String partialDeliveryIsAllowed)
Original property name from the Odata EDM: PartialDeliveryIsAllowed
You use this field to control partial deliveries at the item level. If the customer allows partial delivery, you can choose from different partial delivery options. For example, you can specify whether the customer allows you to make one delivery attempt only on the requested delivery date or whether unlimited delivery attempts are possible.When partial delivery indicator 'D' is set, the order can never have status 'fully delivered'. You must complete each item by entering a reason for rejection. This could be applied to scheduling agreements, for example.You can enter a value in this field only if the customer allows partial deliveries for the entire sales document.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder priceListType(@Nullable String priceListType)
Original property name from the Odata EDM: PriceListType
You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder 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 CustomerSalesArea.CustomerSalesAreaBuilder 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 CustomerSalesArea.CustomerSalesAreaBuilder shippingCondition(@Nullable String shippingCondition)
Original property name from the Odata EDM: ShippingCondition
You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder supplyingPlant(@Nullable String supplyingPlant)
Original property name from the Odata EDM: SupplyingPlant
This plant is automatically copied into the sales order item as the default value.If there is no default value when you process the sales order item, enter a delivering plant.The value proposed in the item is eitherfrom the customer master record of the goods recipient, orfrom the material master recordThe system checks whether it can propose a value (and for your own plants, whether the material has been created in the plant). If the system can propose a value, the plant is copied to the sales order item where you can change it as required.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder salesDistrict(@Nullable String salesDistrict)
Original property name from the Odata EDM: SalesDistrict
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder invoiceListSchedule(@Nullable String invoiceListSchedule)
Original property name from the Odata EDM: InvoiceListSchedule
An invoice list is a list of invoices (single or collective) that you create for the customer either periodically or on predefined dates. The periods and dates are defined in the customer's factory calendar. Typically, the recipient of an invoice list takes on the responsibility for collecting payments from numerous individual customers and receives a factoring or del credere discount for the service.If you want to create invoice lists for the customer, you must enter an identifier for a predefined factory calendar.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder exchangeRateType(@Nullable String exchangeRateType)
Original property name from the Odata EDM: ExchangeRateType
You enter the exchange rate type to store different exchange rates.You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder additionalCustomerGroup1(@Nullable String additionalCustomerGroup1)
Original property name from the Odata EDM: AdditionalCustomerGroup1
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder additionalCustomerGroup2(@Nullable String additionalCustomerGroup2)
Original property name from the Odata EDM: AdditionalCustomerGroup2
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder additionalCustomerGroup3(@Nullable String additionalCustomerGroup3)
Original property name from the Odata EDM: AdditionalCustomerGroup3
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder additionalCustomerGroup4(@Nullable String additionalCustomerGroup4)
Original property name from the Odata EDM: AdditionalCustomerGroup4
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder additionalCustomerGroup5(@Nullable String additionalCustomerGroup5)
Original property name from the Odata EDM: AdditionalCustomerGroup5
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder paymentGuaranteeProcedure(@Nullable String paymentGuaranteeProcedure)
Original property name from the Odata EDM: PaymentGuaranteeProcedure
The customer payment guarantee procedure determines which payment guarantee procedure the system automatically uses when you create a sales document for the customer.In receivables risk management, the system determines the payment guarantee procedure taking into account:the key for the document payment guarantee procedure in the header for the sales document type.the customer payment guarantee procedure key in the customer master.You can define different payment guarantee procedures for your system. The payment guarantee procedure defines the type and sequence of forms of payment guarantee that the system assigns to the sales document items.
this
.@Nonnull public CustomerSalesArea.CustomerSalesAreaBuilder customerAccountGroup(@Nullable String customerAccountGroup)
Original property name from the Odata EDM: CustomerAccountGroup
in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
this
.@Nonnull public CustomerSalesArea build()
Copyright © 2020 SAP SE. All rights reserved.