public static final class CustomerCompany.CustomerCompanyBuilder extends Object
Modifier and Type | Method and Description |
---|---|
CustomerCompany.CustomerCompanyBuilder |
accountByCustomer(String accountByCustomer)
Constraints: Not nullable, Maximum length: 12
|
CustomerCompany.CustomerCompanyBuilder |
accountingClerk(String accountingClerk)
Constraints: Not nullable, Maximum length: 2
|
CustomerCompany.CustomerCompanyBuilder |
accountingClerkFaxNumber(String accountingClerkFaxNumber)
Constraints: Not nullable, Maximum length: 31
|
CustomerCompany.CustomerCompanyBuilder |
accountingClerkInternetAddress(String accountingClerkInternetAddress)
Constraints: Not nullable, Maximum length: 130
|
CustomerCompany.CustomerCompanyBuilder |
accountingClerkPhoneNumber(String accountingClerkPhoneNumber)
Constraints: Not nullable, Maximum length: 30
|
CustomerCompany.CustomerCompanyBuilder |
alternativePayerAccount(String alternativePayerAccount)
Constraints: Not nullable, Maximum length: 10
|
CustomerCompany.CustomerCompanyBuilder |
aPARToleranceGroup(String aPARToleranceGroup)
Constraints: Not nullable, Maximum length: 4
|
CustomerCompany.CustomerCompanyBuilder |
authorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
CustomerCompany |
build() |
CustomerCompany.CustomerCompanyBuilder |
collectiveInvoiceVariant(String collectiveInvoiceVariant)
Constraints: Not nullable, Maximum length: 1
|
CustomerCompany.CustomerCompanyBuilder |
companyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
CustomerCompany.CustomerCompanyBuilder |
customer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
CustomerCompany.CustomerCompanyBuilder |
customerAccountGroup(String customerAccountGroup)
Constraints: Not nullable, Maximum length: 4
|
CustomerCompany.CustomerCompanyBuilder |
customerAccountNote(String customerAccountNote)
Constraints: Not nullable, Maximum length: 30
|
CustomerCompany.CustomerCompanyBuilder |
customerDunning(CustomerDunning... value)
Navigation property to_CustomerDunning for CustomerCompany to multiple CustomerDunning.
|
CustomerCompany.CustomerCompanyBuilder |
customerHeadOffice(String customerHeadOffice)
Constraints: Not nullable, Maximum length: 10
|
CustomerCompany.CustomerCompanyBuilder |
customerSupplierClearingIsUsed(Boolean customerSupplierClearingIsUsed)
Constraints: none
|
CustomerCompany.CustomerCompanyBuilder |
deletionIndicator(Boolean deletionIndicator)
Constraints: none
|
CustomerCompany.CustomerCompanyBuilder |
houseBank(String houseBank)
Constraints: Not nullable, Maximum length: 5
|
CustomerCompany.CustomerCompanyBuilder |
interestCalculationCode(String interestCalculationCode)
Constraints: Not nullable, Maximum length: 2
|
CustomerCompany.CustomerCompanyBuilder |
interestCalculationDate(LocalDateTime interestCalculationDate)
Constraints: Not nullable, Precision: 0
|
CustomerCompany.CustomerCompanyBuilder |
intrstCalcFrequencyInMonths(String intrstCalcFrequencyInMonths)
Constraints: Not nullable, Maximum length: 2
|
CustomerCompany.CustomerCompanyBuilder |
isToBeLocallyProcessed(Boolean isToBeLocallyProcessed)
Constraints: none
|
CustomerCompany.CustomerCompanyBuilder |
itemIsToBePaidSeparately(Boolean itemIsToBePaidSeparately)
Constraints: none
|
CustomerCompany.CustomerCompanyBuilder |
layoutSortingRule(String layoutSortingRule)
Constraints: Not nullable, Maximum length: 3
|
CustomerCompany.CustomerCompanyBuilder |
paymentBlockingReason(String paymentBlockingReason)
Constraints: Not nullable, Maximum length: 1
|
CustomerCompany.CustomerCompanyBuilder |
paymentMethodsList(String paymentMethodsList)
Constraints: Not nullable, Maximum length: 10
|
CustomerCompany.CustomerCompanyBuilder |
paymentTerms(String paymentTerms)
Constraints: Not nullable, Maximum length: 4
|
CustomerCompany.CustomerCompanyBuilder |
paytAdviceIsSentbyEDI(Boolean paytAdviceIsSentbyEDI)
Constraints: none
|
CustomerCompany.CustomerCompanyBuilder |
physicalInventoryBlockInd(Boolean physicalInventoryBlockInd)
Constraints: none
|
CustomerCompany.CustomerCompanyBuilder |
reconciliationAccount(String reconciliationAccount)
Constraints: Not nullable, Maximum length: 10
|
CustomerCompany.CustomerCompanyBuilder |
recordPaymentHistoryIndicator(Boolean recordPaymentHistoryIndicator)
Constraints: none
|
String |
toString() |
CustomerCompany.CustomerCompanyBuilder |
userAtCustomer(String userAtCustomer)
Constraints: Not nullable, Maximum length: 15
|
CustomerCompany.CustomerCompanyBuilder |
withHoldingTax(CustomerWithHoldingTax... value)
Navigation property to_WithHoldingTax for CustomerCompany to multiple
CustomerWithHoldingTax.
|
@Nonnull public CustomerCompany.CustomerCompanyBuilder customerDunning(CustomerDunning... value)
value
- The CustomerDunnings to build this CustomerCompany with.@Nonnull public CustomerCompany.CustomerCompanyBuilder withHoldingTax(CustomerWithHoldingTax... value)
value
- The CustomerWithHoldingTaxs to build this CustomerCompany with.public CustomerCompany.CustomerCompanyBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public CustomerCompany.CustomerCompanyBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public CustomerCompany.CustomerCompanyBuilder aPARToleranceGroup(@Nullable String aPARToleranceGroup)
Original property name from the Odata EDM: APARToleranceGroup
Each tolerance group contains settings that affect cash discount and payment difference processing. These settings become effective during payment entry.
within a company code.public CustomerCompany.CustomerCompanyBuilder accountByCustomer(@Nullable String accountByCustomer)
Original property name from the Odata EDM: AccountByCustomer
public CustomerCompany.CustomerCompanyBuilder accountingClerk(@Nullable String accountingClerk)
Original property name from the Odata EDM: AccountingClerk
The name of the accounting clerk defined by this identification code can be used in the payment program for correspondence and reporting (for example, open item lists).
public CustomerCompany.CustomerCompanyBuilder accountingClerkFaxNumber(@Nullable String accountingClerkFaxNumber)
Original property name from the Odata EDM: AccountingClerkFaxNumber
public CustomerCompany.CustomerCompanyBuilder accountingClerkInternetAddress(@Nullable String accountingClerkInternetAddress)
Original property name from the Odata EDM: AccountingClerkInternetAddress
public CustomerCompany.CustomerCompanyBuilder accountingClerkPhoneNumber(@Nullable String accountingClerkPhoneNumber)
Original property name from the Odata EDM: AccountingClerkPhoneNumber
public CustomerCompany.CustomerCompanyBuilder alternativePayerAccount(@Nullable String alternativePayerAccount)
Original property name from the Odata EDM: AlternativePayerAccount
Account number of the customer for whom automatic payment transactions are to be carried out.The account number is only needed if bank collections are not to be made via the customer who owes the receivables. The same applies to refunds of payables.The specification in this field only applies to this company code. There is another field in which you can enter an alternative payee for all company codes. If both fields are filled, the specification for the company code has priority.
public CustomerCompany.CustomerCompanyBuilder 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 CustomerCompany.CustomerCompanyBuilder collectiveInvoiceVariant(@Nullable String collectiveInvoiceVariant)
Original property name from the Odata EDM: CollectiveInvoiceVariant
public CustomerCompany.CustomerCompanyBuilder customerAccountNote(@Nullable String customerAccountNote)
Original property name from the Odata EDM: CustomerAccountNote
The memo serves only as information on special features of the customer/vendor.
public CustomerCompany.CustomerCompanyBuilder customerHeadOffice(@Nullable String customerHeadOffice)
Original property name from the Odata EDM: CustomerHeadOffice
This account number is only specified for branch accounts. All postings for which the account number of the branch is specified, are automatically posted to the head office account. The account number of the branch affected is noted in the line items.No line items or balances are managed in the branch account.
public CustomerCompany.CustomerCompanyBuilder customerSupplierClearingIsUsed(@Nullable Boolean customerSupplierClearingIsUsed)
Original property name from the Odata EDM: CustomerSupplierClearingIsUsed
To use this function in automatic payment transactions, you have toenter the vendor account number in the customer master record,enter the customer account number in the vendor master record, andselect the "Clearing with customer" indicator in the vendor master record.If you set this indicator, the system will also include items of the vendor account in customer dunning.
account, and that during manual clearing procedures, the items of that vendor account are also selected.public CustomerCompany.CustomerCompanyBuilder houseBank(@Nullable String houseBank)
Original property name from the Odata EDM: HouseBank
public CustomerCompany.CustomerCompanyBuilder interestCalculationCode(@Nullable String interestCalculationCode)
Original property name from the Odata EDM: InterestCalculationCode
calculation.public CustomerCompany.CustomerCompanyBuilder interestCalculationDate(@Nullable LocalDateTime interestCalculationDate)
Original property name from the Odata EDM: InterestCalculationDate
Generally, this date is automatically maintained by the program (batch input). A manual entry in this field should only be made if an error has occurred or when implementing the interest calculation.
This is generally the upper limit of the last interest run.public CustomerCompany.CustomerCompanyBuilder intrstCalcFrequencyInMonths(@Nullable String intrstCalcFrequencyInMonths)
Original property name from the Odata EDM: IntrstCalcFrequencyInMonths
Date of last interest calculation: 3/31.+ 01 month interest calculation frequency= 4/30 upper limit for the current interest runThe calculation period specified as a report parameter determines whether an account is included in an interest run.The upper limit of the interest run is calculated as in the above example and compared with the upper limit of the calculation entered in the interest run (report parameter). If the calculated upper limit is after the calculation period, the account is not included in interest calculation.If you maintain the interest calculation frequency in the account master record, this entry is used to calculate the upper limit. If not, the interest calculation frequency entered for the interest indicator is used.
automatically for this account (account balance interest calculation). The interest calculation frequency is added to the date of the last interest calculation.public CustomerCompany.CustomerCompanyBuilder isToBeLocallyProcessed(@Nullable Boolean isToBeLocallyProcessed)
Original property name from the Odata EDM: IsToBeLocallyProcessed
Normally automatic payment transactions and dunning notices are created for the head office.NoteSelect this indicator only if this account is a head office account.
public CustomerCompany.CustomerCompanyBuilder itemIsToBePaidSeparately(@Nullable Boolean itemIsToBePaidSeparately)
Original property name from the Odata EDM: ItemIsToBePaidSeparately
transactions. This means that open items are not grouped together for payment.public CustomerCompany.CustomerCompanyBuilder layoutSortingRule(@Nullable String layoutSortingRule)
Original property name from the Odata EDM: LayoutSortingRule
The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.For this purpose, the system requires rules that determine which information is to be taken from the document header or from the document line item and placed in the field. The rules can be stored in the master record of an account which enables you to determine the standard sort sequence on an account-specific basis.NoteField information from another document line item cannot be adopted into the field of a particular item.
public CustomerCompany.CustomerCompanyBuilder paymentBlockingReason(@Nullable String paymentBlockingReason)
Original property name from the Odata EDM: PaymentBlockingReason
You can use the block key as described below.Automatic Payment TransactionsIn automatic payment transactions, the block takes effect when it is entered in the system as follows:In the master recordIn the documentIf you enter the block in the master record then all open items for this account are contained in the exception list.The following block keys have a special meaning in the master record:The block key * has the effect that all items of the account are skipped in automatic payment transactions.The block key + has the effect that all items are skipped in which a payment method was not entered explicitly.The block key A is always set automatically when a down payment is entered. Therefore, you must not delete the block key A or use it for other purposes.Whether a block key can be set or removed in payment proposal processing depends on the attribute Changeable in payment proposal of the block key.Manual PaymentsManual payments are only affected by a block key in the document if you set the attribute Blocked for manual payments in the block key.A block key that was set in the master record does not have any effect on manual payments. You can have the system issue a warning message in that case. To do so, you have to make system settings. Set up message 671 of work area F5 in message control accordingly.
public CustomerCompany.CustomerCompanyBuilder paymentMethodsList(@Nullable String paymentMethodsList)
Original property name from the Odata EDM: PaymentMethodsList
If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the item which are not listed in the master record.
you do not specify a payment method in the item to be paid.public CustomerCompany.CustomerCompanyBuilder paymentTerms(@Nullable String paymentTerms)
Original property name from the Odata EDM: PaymentTerms
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.
public CustomerCompany.CustomerCompanyBuilder paytAdviceIsSentbyEDI(@Nullable Boolean paytAdviceIsSentbyEDI)
Original property name from the Odata EDM: PaytAdviceIsSentbyEDI
public CustomerCompany.CustomerCompanyBuilder physicalInventoryBlockInd(@Nullable Boolean physicalInventoryBlockInd)
Original property name from the Odata EDM: PhysicalInventoryBlockInd
If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.
public CustomerCompany.CustomerCompanyBuilder reconciliationAccount(@Nullable String reconciliationAccount)
Original property name from the Odata EDM: ReconciliationAccount
For special postings (for example, down payment or bill of exchange), this account is replaced by another account (for example, 'down payments received' instead of 'receivables').The replacement takes place due to the special G/L indicator which you must specify for these types of postings.
account for normal postings (for example, invoice or payment).public CustomerCompany.CustomerCompanyBuilder recordPaymentHistoryIndicator(@Nullable Boolean recordPaymentHistoryIndicator)
Original property name from the Odata EDM: RecordPaymentHistoryIndicator
The amount and number of payments are then recorded per calendar month, as well as the average days in arrears.Information about cash discount payments and net payments is recorded separately.The indicator should not be set for one-time accounts and accounts which are paid automatically (bank collection or bank bill in Germany, bill of exchange payment request in France).You can only carry out evaluation of the payment history, for example, with the report for customer evaluation with OI listing, if you have selected this field.
public CustomerCompany.CustomerCompanyBuilder userAtCustomer(@Nullable String userAtCustomer)
Original property name from the Odata EDM: UserAtCustomer
public CustomerCompany.CustomerCompanyBuilder deletionIndicator(@Nullable Boolean deletionIndicator)
Original property name from the Odata EDM: DeletionIndicator
To delete this data, you have to run the archiving program for Accounts Receivable or Payable. This program will archive all master records marked for deletion provided that there is no dependent data in them.This deletion flag cannot be used in the program that deletes master data. You should, however, run this program only to delete test data prior to production startup.
public CustomerCompany.CustomerCompanyBuilder 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.
public CustomerCompany build()
Copyright © 2019 SAP SE. All rights reserved.