CustomerCompany (SAP S/4HANA Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject<EntityT>
- - com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmEntity<CustomerCompany>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.businesspartner.CustomerCompany

public class CustomerCompany
extends VdmEntity<CustomerCompany>

Customer Company

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class CustomerCompany.CustomerCompanyBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`CustomerCompany.CustomerCompanyBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static CustomerCompanyField<String>`	`ACCOUNT_BY_CUSTOMER` Use with available fluent helpers to apply the AccountByCustomer field to query operations.
`static CustomerCompanyField<String>`	`ACCOUNTING_CLERK` Use with available fluent helpers to apply the AccountingClerk field to query operations.
`static CustomerCompanyField<String>`	`ACCOUNTING_CLERK_FAX_NUMBER` Use with available fluent helpers to apply the AccountingClerkFaxNumber field to query operations.
`static CustomerCompanyField<String>`	`ACCOUNTING_CLERK_INTERNET_ADDRESS` Use with available fluent helpers to apply the AccountingClerkInternetAddress field to query operations.
`static CustomerCompanyField<String>`	`ACCOUNTING_CLERK_PHONE_NUMBER` Use with available fluent helpers to apply the AccountingClerkPhoneNumber field to query operations.
`static CustomerCompanySelectable`	`ALL_FIELDS` Selector for all available fields of CustomerCompany.
`static CustomerCompanyField<String>`	`ALTERNATIVE_PAYER_ACCOUNT` Use with available fluent helpers to apply the AlternativePayerAccount field to query operations.
`static CustomerCompanyField<String>`	`APAR_TOLERANCE_GROUP` Use with available fluent helpers to apply the APARToleranceGroup field to query operations.
`static CustomerCompanyField<String>`	`AUTHORIZATION_GROUP` Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
`static CustomerCompanyField<String>`	`COLLECTIVE_INVOICE_VARIANT` Use with available fluent helpers to apply the CollectiveInvoiceVariant field to query operations.
`static CustomerCompanyField<String>`	`COMPANY_CODE` Use with available fluent helpers to apply the CompanyCode field to query operations.
`static CustomerCompanyField<String>`	`CUSTOMER` Use with available fluent helpers to apply the Customer field to query operations.
`static CustomerCompanyField<String>`	`CUSTOMER_ACCOUNT_GROUP` Use with available fluent helpers to apply the CustomerAccountGroup field to query operations.
`static CustomerCompanyField<String>`	`CUSTOMER_ACCOUNT_NOTE` Use with available fluent helpers to apply the CustomerAccountNote field to query operations.
`static CustomerCompanyField<String>`	`CUSTOMER_HEAD_OFFICE` Use with available fluent helpers to apply the CustomerHeadOffice field to query operations.
`static CustomerCompanyField<Boolean>`	`CUSTOMER_SUPPLIER_CLEARING_IS_USED` Use with available fluent helpers to apply the CustomerSupplierClearingIsUsed field to query operations.
`static CustomerCompanyField<Boolean>`	`DELETION_INDICATOR` Use with available fluent helpers to apply the DeletionIndicator field to query operations.
`static CustomerCompanyField<String>`	`HOUSE_BANK` Use with available fluent helpers to apply the HouseBank field to query operations.
`static CustomerCompanyField<String>`	`INTEREST_CALCULATION_CODE` Use with available fluent helpers to apply the InterestCalculationCode field to query operations.
`static CustomerCompanyField<Calendar>`	`INTEREST_CALCULATION_DATE` Use with available fluent helpers to apply the InterestCalculationDate field to query operations.
`static CustomerCompanyField<String>`	`INTRST_CALC_FREQUENCY_IN_MONTHS` Use with available fluent helpers to apply the IntrstCalcFrequencyInMonths field to query operations.
`static CustomerCompanyField<Boolean>`	`IS_TO_BE_LOCALLY_PROCESSED` Use with available fluent helpers to apply the IsToBeLocallyProcessed field to query operations.
`static CustomerCompanyField<Boolean>`	`ITEM_IS_TO_BE_PAID_SEPARATELY` Use with available fluent helpers to apply the ItemIsToBePaidSeparately field to query operations.
`static CustomerCompanyField<String>`	`LAYOUT_SORTING_RULE` Use with available fluent helpers to apply the LayoutSortingRule field to query operations.
`static CustomerCompanyField<String>`	`PAYMENT_BLOCKING_REASON` Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
`static CustomerCompanyField<String>`	`PAYMENT_METHODS_LIST` Use with available fluent helpers to apply the PaymentMethodsList field to query operations.
`static CustomerCompanyField<String>`	`PAYMENT_TERMS` Use with available fluent helpers to apply the PaymentTerms field to query operations.
`static CustomerCompanyField<Boolean>`	`PAYT_ADVICE_IS_SENTBY_EDI` Use with available fluent helpers to apply the PaytAdviceIsSentbyEDI field to query operations.
`static CustomerCompanyField<Boolean>`	`PHYSICAL_INVENTORY_BLOCK_IND` Use with available fluent helpers to apply the PhysicalInventoryBlockInd field to query operations.
`static CustomerCompanyField<String>`	`RECONCILIATION_ACCOUNT` Use with available fluent helpers to apply the ReconciliationAccount field to query operations.
`static CustomerCompanyField<Boolean>`	`RECORD_PAYMENT_HISTORY_INDICATOR` Use with available fluent helpers to apply the RecordPaymentHistoryIndicator field to query operations.
`static CustomerCompanyLink<CustomerDunning>`	`TO_CUSTOMER_DUNNING` Use with available fluent helpers to apply the to_CustomerDunning navigation property to query operations.
`static CustomerCompanyLink<CustomerWithHoldingTax>`	`TO_WITH_HOLDING_TAX` Use with available fluent helpers to apply the to_WithHoldingTax navigation property to query operations.
`static CustomerCompanyField<String>`	`USER_AT_CUSTOMER` Use with available fluent helpers to apply the UserAtCustomer field to query operations.

Constructor Summary

Constructors
Constructor and Description
`CustomerCompany()`
CustomerCompany(String customer, String companyCode, String aPARToleranceGroup, String accountByCustomer, String accountingClerk, String accountingClerkFaxNumber, String accountingClerkInternetAddress, String accountingClerkPhoneNumber, String alternativePayerAccount, String authorizationGroup, String collectiveInvoiceVariant, String customerAccountNote, String customerHeadOffice, Boolean customerSupplierClearingIsUsed, String houseBank, String interestCalculationCode, Calendar interestCalculationDate, String intrstCalcFrequencyInMonths, Boolean isToBeLocallyProcessed, Boolean itemIsToBePaidSeparately, String layoutSortingRule, String paymentBlockingReason, String paymentMethodsList, String paymentTerms, Boolean paytAdviceIsSentbyEDI, Boolean physicalInventoryBlockInd, String reconciliationAccount, Boolean recordPaymentHistoryIndicator, String userAtCustomer, Boolean deletionIndicator, String customerAccountGroup, ErpConfigContext erpConfigContext, List<CustomerDunning> toCustomerDunning, List<CustomerWithHoldingTax> toWithHoldingTax)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addCustomerDunning(CustomerDunning... entity)` Adds elements to the list of associated CustomerDunning entities.
`void`	`addWithHoldingTax(CustomerWithHoldingTax... entity)` Adds elements to the list of associated CustomerWithHoldingTax entities.
`static CustomerCompany.CustomerCompanyBuilder`	`builder()`
`boolean`	`equals(Object o)`
`List<CustomerDunning>`	`fetchCustomerDunning()` Fetches the CustomerDunning entities (one to many) associated with this entity.
`List<CustomerWithHoldingTax>`	`fetchWithHoldingTax()` Fetches the CustomerWithHoldingTax entities (one to many) associated with this entity.
`static <T> CustomerCompanyField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`String`	`getAccountByCustomer()` Constraints: Not nullable, Maximum length: 12
`String`	`getAccountingClerk()` Constraints: Not nullable, Maximum length: 2 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).
`String`	`getAccountingClerkFaxNumber()` Constraints: Not nullable, Maximum length: 31
`String`	`getAccountingClerkInternetAddress()` Constraints: Not nullable, Maximum length: 130
`String`	`getAccountingClerkPhoneNumber()` Constraints: Not nullable, Maximum length: 30
`String`	`getAlternativePayerAccount()` Constraints: Not nullable, Maximum length: 10 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.
`String`	`getAPARToleranceGroup()` Constraints: Not nullable, Maximum length: 4 Each tolerance group contains settings that affect cash discount and payment difference processing.
`String`	`getAuthorizationGroup()` Constraints: Not nullable, Maximum length: 4
`String`	`getCollectiveInvoiceVariant()` Constraints: Not nullable, Maximum length: 1
`String`	`getCompanyCode()` (Key Field) Constraints: Not nullable, Maximum length: 4
`String`	`getCustomer()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getCustomerAccountGroup()` Constraints: Not nullable, Maximum length: 4 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.
`String`	`getCustomerAccountNote()` Constraints: Not nullable, Maximum length: 30 The memo serves only as information on special features of the customer/vendor.
`List<CustomerDunning>`	`getCustomerDunningOrFetch()` Retrieval of associated CustomerDunning entities (one to many).
`com.google.common.base.Optional<List<CustomerDunning>>`	`getCustomerDunningOrNull()` Retrieval of associated CustomerDunning entities (one to many).
`String`	`getCustomerHeadOffice()` Constraints: Not nullable, Maximum length: 10 This account number is only specified for branch accounts.
`Boolean`	`getCustomerSupplierClearingIsUsed()` Constraints: noneTo 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.
`Boolean`	`getDeletionIndicator()` Constraints: noneTo delete this data, you have to run the archiving program for Accounts Receivable or Payable.
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`String`	`getHouseBank()` Constraints: Not nullable, Maximum length: 5
`String`	`getInterestCalculationCode()` Constraints: Not nullable, Maximum length: 2
`Calendar`	`getInterestCalculationDate()` Constraints: Not nullable, Precision: 0 Generally, this date is automatically maintained by the program (batch input).
`String`	`getIntrstCalcFrequencyInMonths()` Constraints: Not nullable, Maximum length: 2 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).
`Boolean`	`getIsToBeLocallyProcessed()` Constraints: noneNormally automatic payment transactions and dunning notices are created for the head office.NoteSelect this indicator only if this account is a head office account.
`Boolean`	`getItemIsToBePaidSeparately()` Constraints: none
`String`	`getLayoutSortingRule()` Constraints: Not nullable, Maximum length: 3 The system uses a standard sort sequence for displaying line items.
`String`	`getPaymentBlockingReason()` Constraints: Not nullable, Maximum length: 1 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.
`String`	`getPaymentMethodsList()` Constraints: Not nullable, Maximum length: 10 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.
`String`	`getPaymentTerms()` Constraints: Not nullable, Maximum length: 4 It is used in sales orders, purchase orders, and invoices.
`Boolean`	`getPaytAdviceIsSentbyEDI()` Constraints: none
`Boolean`	`getPhysicalInventoryBlockInd()` Constraints: noneIf 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.
`String`	`getReconciliationAccount()` Constraints: Not nullable, Maximum length: 10 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.
`Boolean`	`getRecordPaymentHistoryIndicator()` Constraints: noneThe 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.
`Class<CustomerCompany>`	`getType()`
`String`	`getUserAtCustomer()` Constraints: Not nullable, Maximum length: 15
`List<CustomerWithHoldingTax>`	`getWithHoldingTaxOrFetch()` Retrieval of associated CustomerWithHoldingTax entities (one to many).
`com.google.common.base.Optional<List<CustomerWithHoldingTax>>`	`getWithHoldingTaxOrNull()` Retrieval of associated CustomerWithHoldingTax entities (one to many).
`int`	`hashCode()`
`void`	`setAccountByCustomer(String accountByCustomer)` Constraints: Not nullable, Maximum length: 12
`void`	`setAccountingClerk(String accountingClerk)` Constraints: Not nullable, Maximum length: 2 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).
`void`	`setAccountingClerkFaxNumber(String accountingClerkFaxNumber)` Constraints: Not nullable, Maximum length: 31
`void`	`setAccountingClerkInternetAddress(String accountingClerkInternetAddress)` Constraints: Not nullable, Maximum length: 130
`void`	`setAccountingClerkPhoneNumber(String accountingClerkPhoneNumber)` Constraints: Not nullable, Maximum length: 30
`void`	`setAlternativePayerAccount(String alternativePayerAccount)` Constraints: Not nullable, Maximum length: 10 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.
`void`	`setAPARToleranceGroup(String aPARToleranceGroup)` Constraints: Not nullable, Maximum length: 4 Each tolerance group contains settings that affect cash discount and payment difference processing.
`void`	`setAuthorizationGroup(String authorizationGroup)` Constraints: Not nullable, Maximum length: 4
`void`	`setCollectiveInvoiceVariant(String collectiveInvoiceVariant)` Constraints: Not nullable, Maximum length: 1
`void`	`setCompanyCode(String companyCode)` (Key Field) Constraints: Not nullable, Maximum length: 4
`void`	`setCustomer(String customer)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setCustomerAccountGroup(String customerAccountGroup)` Constraints: Not nullable, Maximum length: 4 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.
`void`	`setCustomerAccountNote(String customerAccountNote)` Constraints: Not nullable, Maximum length: 30 The memo serves only as information on special features of the customer/vendor.
`void`	`setCustomerDunning(List<CustomerDunning> value)` Overwrites the list of associated CustomerDunning entities for the loaded navigation property to_CustomerDunning.
`void`	`setCustomerHeadOffice(String customerHeadOffice)` Constraints: Not nullable, Maximum length: 10 This account number is only specified for branch accounts.
`void`	`setCustomerSupplierClearingIsUsed(Boolean customerSupplierClearingIsUsed)` Constraints: noneTo 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.
`void`	`setDeletionIndicator(Boolean deletionIndicator)` Constraints: noneTo delete this data, you have to run the archiving program for Accounts Receivable or Payable.
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`void`	`setHouseBank(String houseBank)` Constraints: Not nullable, Maximum length: 5
`void`	`setInterestCalculationCode(String interestCalculationCode)` Constraints: Not nullable, Maximum length: 2
`void`	`setInterestCalculationDate(Calendar interestCalculationDate)` Constraints: Not nullable, Precision: 0 Generally, this date is automatically maintained by the program (batch input).
`void`	`setIntrstCalcFrequencyInMonths(String intrstCalcFrequencyInMonths)` Constraints: Not nullable, Maximum length: 2 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).
`void`	`setIsToBeLocallyProcessed(Boolean isToBeLocallyProcessed)` Constraints: noneNormally automatic payment transactions and dunning notices are created for the head office.NoteSelect this indicator only if this account is a head office account.
`void`	`setItemIsToBePaidSeparately(Boolean itemIsToBePaidSeparately)` Constraints: none
`void`	`setLayoutSortingRule(String layoutSortingRule)` Constraints: Not nullable, Maximum length: 3 The system uses a standard sort sequence for displaying line items.
`void`	`setPaymentBlockingReason(String paymentBlockingReason)` Constraints: Not nullable, Maximum length: 1 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.
`void`	`setPaymentMethodsList(String paymentMethodsList)` Constraints: Not nullable, Maximum length: 10 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.
`void`	`setPaymentTerms(String paymentTerms)` Constraints: Not nullable, Maximum length: 4 It is used in sales orders, purchase orders, and invoices.
`void`	`setPaytAdviceIsSentbyEDI(Boolean paytAdviceIsSentbyEDI)` Constraints: none
`void`	`setPhysicalInventoryBlockInd(Boolean physicalInventoryBlockInd)` Constraints: noneIf 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.
`void`	`setReconciliationAccount(String reconciliationAccount)` Constraints: Not nullable, Maximum length: 10 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.
`void`	`setRecordPaymentHistoryIndicator(Boolean recordPaymentHistoryIndicator)` Constraints: noneThe 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.
`void`	`setUserAtCustomer(String userAtCustomer)` Constraints: Not nullable, Maximum length: 15
`void`	`setWithHoldingTax(List<CustomerWithHoldingTax> value)` Overwrites the list of associated CustomerWithHoldingTax entities for the loaded navigation property to_WithHoldingTax.
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField

Methods inherited from class java.lang.Object
getClass, notify, notifyAll, wait, wait, wait

- Field Detail
  - ALL_FIELDS
```
public static final CustomerCompanySelectable ALL_FIELDS
```
    Selector for all available fields of CustomerCompany.
  - CUSTOMER
```
public static final CustomerCompanyField<String> CUSTOMER
```
    Use with available fluent helpers to apply the Customer field to query operations.
  - COMPANY_CODE
```
public static final CustomerCompanyField<String> COMPANY_CODE
```
    Use with available fluent helpers to apply the CompanyCode field to query operations.
  - APAR_TOLERANCE_GROUP
```
public static final CustomerCompanyField<String> APAR_TOLERANCE_GROUP
```
    Use with available fluent helpers to apply the APARToleranceGroup field to query operations.
  - ACCOUNT_BY_CUSTOMER
```
public static final CustomerCompanyField<String> ACCOUNT_BY_CUSTOMER
```
    Use with available fluent helpers to apply the AccountByCustomer field to query operations.
  - ACCOUNTING_CLERK
```
public static final CustomerCompanyField<String> ACCOUNTING_CLERK
```
    Use with available fluent helpers to apply the AccountingClerk field to query operations.
  - ACCOUNTING_CLERK_FAX_NUMBER
```
public static final CustomerCompanyField<String> ACCOUNTING_CLERK_FAX_NUMBER
```
    Use with available fluent helpers to apply the AccountingClerkFaxNumber field to query operations.
  - ACCOUNTING_CLERK_INTERNET_ADDRESS
```
public static final CustomerCompanyField<String> ACCOUNTING_CLERK_INTERNET_ADDRESS
```
    Use with available fluent helpers to apply the AccountingClerkInternetAddress field to query operations.
  - ACCOUNTING_CLERK_PHONE_NUMBER
```
public static final CustomerCompanyField<String> ACCOUNTING_CLERK_PHONE_NUMBER
```
    Use with available fluent helpers to apply the AccountingClerkPhoneNumber field to query operations.
  - ALTERNATIVE_PAYER_ACCOUNT
```
public static final CustomerCompanyField<String> ALTERNATIVE_PAYER_ACCOUNT
```
    Use with available fluent helpers to apply the AlternativePayerAccount field to query operations.
  - AUTHORIZATION_GROUP
```
public static final CustomerCompanyField<String> AUTHORIZATION_GROUP
```
    Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
  - COLLECTIVE_INVOICE_VARIANT
```
public static final CustomerCompanyField<String> COLLECTIVE_INVOICE_VARIANT
```
    Use with available fluent helpers to apply the CollectiveInvoiceVariant field to query operations.
  - CUSTOMER_ACCOUNT_NOTE
```
public static final CustomerCompanyField<String> CUSTOMER_ACCOUNT_NOTE
```
    Use with available fluent helpers to apply the CustomerAccountNote field to query operations.
  - CUSTOMER_HEAD_OFFICE
```
public static final CustomerCompanyField<String> CUSTOMER_HEAD_OFFICE
```
    Use with available fluent helpers to apply the CustomerHeadOffice field to query operations.
  - CUSTOMER_SUPPLIER_CLEARING_IS_USED
```
public static final CustomerCompanyField<Boolean> CUSTOMER_SUPPLIER_CLEARING_IS_USED
```
    Use with available fluent helpers to apply the CustomerSupplierClearingIsUsed field to query operations.
  - HOUSE_BANK
```
public static final CustomerCompanyField<String> HOUSE_BANK
```
    Use with available fluent helpers to apply the HouseBank field to query operations.
  - INTEREST_CALCULATION_CODE
```
public static final CustomerCompanyField<String> INTEREST_CALCULATION_CODE
```
    Use with available fluent helpers to apply the InterestCalculationCode field to query operations.
  - INTEREST_CALCULATION_DATE
```
public static final CustomerCompanyField<Calendar> INTEREST_CALCULATION_DATE
```
    Use with available fluent helpers to apply the InterestCalculationDate field to query operations.
  - INTRST_CALC_FREQUENCY_IN_MONTHS
```
public static final CustomerCompanyField<String> INTRST_CALC_FREQUENCY_IN_MONTHS
```
    Use with available fluent helpers to apply the IntrstCalcFrequencyInMonths field to query operations.
  - IS_TO_BE_LOCALLY_PROCESSED
```
public static final CustomerCompanyField<Boolean> IS_TO_BE_LOCALLY_PROCESSED
```
    Use with available fluent helpers to apply the IsToBeLocallyProcessed field to query operations.
  - ITEM_IS_TO_BE_PAID_SEPARATELY
```
public static final CustomerCompanyField<Boolean> ITEM_IS_TO_BE_PAID_SEPARATELY
```
    Use with available fluent helpers to apply the ItemIsToBePaidSeparately field to query operations.
  - LAYOUT_SORTING_RULE
```
public static final CustomerCompanyField<String> LAYOUT_SORTING_RULE
```
    Use with available fluent helpers to apply the LayoutSortingRule field to query operations.
  - PAYMENT_BLOCKING_REASON
```
public static final CustomerCompanyField<String> PAYMENT_BLOCKING_REASON
```
    Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
  - PAYMENT_METHODS_LIST
```
public static final CustomerCompanyField<String> PAYMENT_METHODS_LIST
```
    Use with available fluent helpers to apply the PaymentMethodsList field to query operations.
  - PAYMENT_TERMS
```
public static final CustomerCompanyField<String> PAYMENT_TERMS
```
    Use with available fluent helpers to apply the PaymentTerms field to query operations.
  - PAYT_ADVICE_IS_SENTBY_EDI
```
public static final CustomerCompanyField<Boolean> PAYT_ADVICE_IS_SENTBY_EDI
```
    Use with available fluent helpers to apply the PaytAdviceIsSentbyEDI field to query operations.
  - PHYSICAL_INVENTORY_BLOCK_IND
```
public static final CustomerCompanyField<Boolean> PHYSICAL_INVENTORY_BLOCK_IND
```
    Use with available fluent helpers to apply the PhysicalInventoryBlockInd field to query operations.
  - RECONCILIATION_ACCOUNT
```
public static final CustomerCompanyField<String> RECONCILIATION_ACCOUNT
```
    Use with available fluent helpers to apply the ReconciliationAccount field to query operations.
  - RECORD_PAYMENT_HISTORY_INDICATOR
```
public static final CustomerCompanyField<Boolean> RECORD_PAYMENT_HISTORY_INDICATOR
```
    Use with available fluent helpers to apply the RecordPaymentHistoryIndicator field to query operations.
  - USER_AT_CUSTOMER
```
public static final CustomerCompanyField<String> USER_AT_CUSTOMER
```
    Use with available fluent helpers to apply the UserAtCustomer field to query operations.
  - DELETION_INDICATOR
```
public static final CustomerCompanyField<Boolean> DELETION_INDICATOR
```
    Use with available fluent helpers to apply the DeletionIndicator field to query operations.
  - CUSTOMER_ACCOUNT_GROUP
```
public static final CustomerCompanyField<String> CUSTOMER_ACCOUNT_GROUP
```
    Use with available fluent helpers to apply the CustomerAccountGroup field to query operations.
  - TO_CUSTOMER_DUNNING
```
public static final CustomerCompanyLink<CustomerDunning> TO_CUSTOMER_DUNNING
```
    Use with available fluent helpers to apply the to_CustomerDunning navigation property to query operations.
  - TO_WITH_HOLDING_TAX
```
public static final CustomerCompanyLink<CustomerWithHoldingTax> TO_WITH_HOLDING_TAX
```
    Use with available fluent helpers to apply the to_WithHoldingTax navigation property to query operations.
- Constructor Detail
  - CustomerCompany
```
public CustomerCompany()
```
  - CustomerCompany
```
public CustomerCompany(@Nullable
                       String customer,
                       @Nullable
                       String companyCode,
                       @Nullable
                       String aPARToleranceGroup,
                       @Nullable
                       String accountByCustomer,
                       @Nullable
                       String accountingClerk,
                       @Nullable
                       String accountingClerkFaxNumber,
                       @Nullable
                       String accountingClerkInternetAddress,
                       @Nullable
                       String accountingClerkPhoneNumber,
                       @Nullable
                       String alternativePayerAccount,
                       @Nullable
                       String authorizationGroup,
                       @Nullable
                       String collectiveInvoiceVariant,
                       @Nullable
                       String customerAccountNote,
                       @Nullable
                       String customerHeadOffice,
                       @Nullable
                       Boolean customerSupplierClearingIsUsed,
                       @Nullable
                       String houseBank,
                       @Nullable
                       String interestCalculationCode,
                       @Nullable
                       Calendar interestCalculationDate,
                       @Nullable
                       String intrstCalcFrequencyInMonths,
                       @Nullable
                       Boolean isToBeLocallyProcessed,
                       @Nullable
                       Boolean itemIsToBePaidSeparately,
                       @Nullable
                       String layoutSortingRule,
                       @Nullable
                       String paymentBlockingReason,
                       @Nullable
                       String paymentMethodsList,
                       @Nullable
                       String paymentTerms,
                       @Nullable
                       Boolean paytAdviceIsSentbyEDI,
                       @Nullable
                       Boolean physicalInventoryBlockInd,
                       @Nullable
                       String reconciliationAccount,
                       @Nullable
                       Boolean recordPaymentHistoryIndicator,
                       @Nullable
                       String userAtCustomer,
                       @Nullable
                       Boolean deletionIndicator,
                       @Nullable
                       String customerAccountGroup,
                       @Nullable
                       ErpConfigContext erpConfigContext,
                       List<CustomerDunning> toCustomerDunning,
                       List<CustomerWithHoldingTax> toWithHoldingTax)
```
- Method Detail
  - getType
```
public Class<CustomerCompany> getType()
```
    Specified by:
    
    getType in class VdmObject<CustomerCompany>
    
    Returns:
    
    The class of this object.
  - field
```
public static <T> CustomerCompanyField<T> field(String fieldName,
                                                Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Parameters:
    
    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.
    
    Returns:
    
    A representation of an extension field from this entity.
  - fetchCustomerDunning
```
public List<CustomerDunning> fetchCustomerDunning()
                                           throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerDunning entities (one to many) associated with this entity. This corresponds to the OData navigation property to_CustomerDunning.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustomerDunning entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getCustomerDunningOrFetch
```
public List<CustomerDunning> getCustomerDunningOrFetch()
                                                throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerDunning entities (one to many).
    If the navigation property to_CustomerDunning of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated CustomerDunning entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getCustomerDunningOrNull
```
public com.google.common.base.Optional<List<CustomerDunning>> getCustomerDunningOrNull()
```
    Retrieval of associated CustomerDunning entities (one to many).
    If the navigation property to_CustomerDunning for an entity CustomerCompany has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_CustomerDunning is already loaded, the result will contain the CustomerDunning entities. If not, a null value state is returned.
  - setCustomerDunning
```
public void setCustomerDunning(@NonNull
                               List<CustomerDunning> value)
```
    Overwrites the list of associated CustomerDunning entities for the loaded navigation property to_CustomerDunning.
    If the navigation property to_CustomerDunning of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of CustomerDunning entities.
  - addCustomerDunning
```
public void addCustomerDunning(CustomerDunning... entity)
```
    Adds elements to the list of associated CustomerDunning entities.
    If the navigation property to_CustomerDunning of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of CustomerDunning entities.
  - fetchWithHoldingTax
```
public List<CustomerWithHoldingTax> fetchWithHoldingTax()
                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerWithHoldingTax entities (one to many) associated with this entity. This corresponds to the OData navigation property to_WithHoldingTax.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustomerWithHoldingTax entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getWithHoldingTaxOrFetch
```
public List<CustomerWithHoldingTax> getWithHoldingTaxOrFetch()
                                                      throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerWithHoldingTax entities (one to many).
    If the navigation property to_WithHoldingTax of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated CustomerWithHoldingTax entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getWithHoldingTaxOrNull
```
public com.google.common.base.Optional<List<CustomerWithHoldingTax>> getWithHoldingTaxOrNull()
```
    Retrieval of associated CustomerWithHoldingTax entities (one to many).
    If the navigation property to_WithHoldingTax for an entity CustomerCompany has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_WithHoldingTax is already loaded, the result will contain the CustomerWithHoldingTax entities. If not, a null value state is returned.
  - setWithHoldingTax
```
public void setWithHoldingTax(@NonNull
                              List<CustomerWithHoldingTax> value)
```
    Overwrites the list of associated CustomerWithHoldingTax entities for the loaded navigation property to_WithHoldingTax.
    If the navigation property to_WithHoldingTax of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of CustomerWithHoldingTax entities.
  - addWithHoldingTax
```
public void addWithHoldingTax(CustomerWithHoldingTax... entity)
```
    Adds elements to the list of associated CustomerWithHoldingTax entities.
    If the navigation property to_WithHoldingTax of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of CustomerWithHoldingTax entities.
  - builder
```
public static CustomerCompany.CustomerCompanyBuilder builder()
```
  - getCustomer
```
@Nullable
public String getCustomer()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.
  - getCompanyCode
```
@Nullable
public String getCompanyCode()
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    The company code is an organizational unit within financial accounting.
  - getAPARToleranceGroup
```
@Nullable
public String getAPARToleranceGroup()
```
    Constraints: Not nullable, Maximum length: 4
    Each tolerance group contains settings that affect cash discount and payment difference processing. These settings become effective during payment entry.
    
    Returns:
    
    Freely definable group code for customers and vendors, or G/L accounts. Tolerance groups are unique within a company code.
  - getAccountByCustomer
```
@Nullable
public String getAccountByCustomer()
```
    Constraints: Not nullable, Maximum length: 12
    
    Returns:
    
    This field contains the account number the company is listed under at the customer.
  - getAccountingClerk
```
@Nullable
public String getAccountingClerk()
```
    Constraints: Not nullable, Maximum length: 2
    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).
    
    Returns:
    
    Identification code for the accounting clerk.
  - getAccountingClerkFaxNumber
```
@Nullable
public String getAccountingClerkFaxNumber()
```
    Constraints: Not nullable, Maximum length: 31
    
    Returns:
    
    Accounting clerk's fax number at the customer/vendor
  - getAccountingClerkInternetAddress
```
@Nullable
public String getAccountingClerkInternetAddress()
```
    Constraints: Not nullable, Maximum length: 130
    
    Returns:
    
    Internet address of partner company clerk
  - getAccountingClerkPhoneNumber
```
@Nullable
public String getAccountingClerkPhoneNumber()
```
    Constraints: Not nullable, Maximum length: 30
    
    Returns:
    
    Accounting clerk's telephone number at business partner
  - getAlternativePayerAccount
```
@Nullable
public String getAlternativePayerAccount()
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Returns:
    
    Account number of an alternative payer
  - getAuthorizationGroup
```
@Nullable
public String getAuthorizationGroup()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.
  - getCollectiveInvoiceVariant
```
@Nullable
public String getCollectiveInvoiceVariant()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Indicator which specifies at what intervals the collective invoices are to be created for the customer.
  - getCustomerAccountNote
```
@Nullable
public String getCustomerAccountNote()
```
    Constraints: Not nullable, Maximum length: 30
    The memo serves only as information on special features of the customer/vendor.
    
    Returns:
    
    Internal memo of the accounting department.
  - getCustomerHeadOffice
```
@Nullable
public String getCustomerHeadOffice()
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Returns:
    
    This field contains the account number of the head office.
  - getCustomerSupplierClearingIsUsed
```
@Nullable
public Boolean getCustomerSupplierClearingIsUsed()
```
    Constraints: none
    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.
    
    Returns:
    
    Indicates that during automatic payment transactions clearing is made with the corresponding vendor account, and that during manual clearing procedures, the items of that vendor account are also selected.
  - getHouseBank
```
@Nullable
public String getHouseBank()
```
    Constraints: Not nullable, Maximum length: 5
    
    Returns:
    
    All bank data is determined using this key.
  - getInterestCalculationCode
```
@Nullable
public String getInterestCalculationCode()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Enter an interest calculation indicator here if the account is to be included in automatic interest calculation.
  - getInterestCalculationDate
```
@Nullable
public Calendar getInterestCalculationDate()
```
    Constraints: Not nullable, Precision: 0
    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.
    
    Returns:
    
    The date in this field displays the last time the interest calculation program processed this account. This is generally the upper limit of the last interest run.
  - getIntrstCalcFrequencyInMonths
```
@Nullable
public String getIntrstCalcFrequencyInMonths()
```
    Constraints: Not nullable, Maximum length: 2
    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.
    
    Returns:
    
    An entry in this field determines the intervals (in months) at which interest is to be calculated automatically for this account (account balance interest calculation). The interest calculation frequency is added to the date of the last interest calculation.
  - getIsToBeLocallyProcessed
```
@Nullable
public Boolean getIsToBeLocallyProcessed()
```
    Constraints: none
    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.
    
    Returns:
    
    Indicates that payment transactions and dunning notices are created for the branch.
  - getItemIsToBePaidSeparately
```
@Nullable
public Boolean getItemIsToBePaidSeparately()
```
    Constraints: none
    
    Returns:
    
    If this indicator is set, every customer/vendor open item is paid separately during automatic payment transactions. This means that open items are not grouped together for payment.
  - getLayoutSortingRule
```
@Nullable
public String getLayoutSortingRule()
```
    Constraints: Not nullable, Maximum length: 3
    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.
    
    Returns:
    
    Indicates the layout rule for the Allocation field in the document line item.
  - getPaymentBlockingReason
```
@Nullable
public String getPaymentBlockingReason()
```
    Constraints: Not nullable, Maximum length: 1
    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.
    
    Returns:
    
    Block key (enqueue key) that is used to block an open item or an account to payment transactions.
  - getPaymentMethodsList
```
@Nullable
public String getPaymentMethodsList()
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Returns:
    
    List of payment methods which may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid.
  - getPaymentTerms
```
@Nullable
public String getPaymentTerms()
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Returns:
    
    Key for defining payment terms composed of cash discount percentages and payment periods.
  - getPaytAdviceIsSentbyEDI
```
@Nullable
public Boolean getPaytAdviceIsSentbyEDI()
```
    Constraints: none
    
    Returns:
    
    This indicator specifies that the customer/vendor should be sent all payment advice information by EDI.
  - getPhysicalInventoryBlockInd
```
@Nullable
public Boolean getPhysicalInventoryBlockInd()
```
    Constraints: none
    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.
    
    Returns:
    
    Indicates that the account is blocked for posting in the specified company code.
  - getReconciliationAccount
```
@Nullable
public String getReconciliationAccount()
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Returns:
    
    The reconciliation account in G/L accounting is the account which is updated parallel to the subledger account for normal postings (for example, invoice or payment).
  - getRecordPaymentHistoryIndicator
```
@Nullable
public Boolean getRecordPaymentHistoryIndicator()
```
    Constraints: none
    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.
    
    Returns:
    
    Indicator that the payment history of the customer is to be recorded.
  - getUserAtCustomer
```
@Nullable
public String getUserAtCustomer()
```
    Constraints: Not nullable, Maximum length: 15
    
    Returns:
    
    Name or identification code of the accounting clerk at the customer.
  - getDeletionIndicator
```
@Nullable
public Boolean getDeletionIndicator()
```
    Constraints: none
    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.
    
    Returns:
    
    Indicates that the company code data in this master record is to be deleted.
  - getCustomerAccountGroup
```
@Nullable
public String getCustomerAccountGroup()
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Returns:
    
    The account group is a classifying feature within customer master records. The account group determines:
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setCustomer
```
public void setCustomer(@Nullable
                        String customer)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    customer -
  - setCompanyCode
```
public void setCompanyCode(@Nullable
                           String companyCode)
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    companyCode -
  - setAPARToleranceGroup
```
public void setAPARToleranceGroup(@Nullable
                                  String aPARToleranceGroup)
```
    Constraints: Not nullable, Maximum length: 4
    Each tolerance group contains settings that affect cash discount and payment difference processing. These settings become effective during payment entry.
    
    Parameters:
    
    aPARToleranceGroup -
  - setAccountByCustomer
```
public void setAccountByCustomer(@Nullable
                                 String accountByCustomer)
```
    Constraints: Not nullable, Maximum length: 12
    
    Parameters:
    
    accountByCustomer -
  - setAccountingClerk
```
public void setAccountingClerk(@Nullable
                               String accountingClerk)
```
    Constraints: Not nullable, Maximum length: 2
    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).
    
    Parameters:
    
    accountingClerk -
  - setAccountingClerkFaxNumber
```
public void setAccountingClerkFaxNumber(@Nullable
                                        String accountingClerkFaxNumber)
```
    Constraints: Not nullable, Maximum length: 31
    
    Parameters:
    
    accountingClerkFaxNumber -
  - setAccountingClerkInternetAddress
```
public void setAccountingClerkInternetAddress(@Nullable
                                              String accountingClerkInternetAddress)
```
    Constraints: Not nullable, Maximum length: 130
    
    Parameters:
    
    accountingClerkInternetAddress -
  - setAccountingClerkPhoneNumber
```
public void setAccountingClerkPhoneNumber(@Nullable
                                          String accountingClerkPhoneNumber)
```
    Constraints: Not nullable, Maximum length: 30
    
    Parameters:
    
    accountingClerkPhoneNumber -
  - setAlternativePayerAccount
```
public void setAlternativePayerAccount(@Nullable
                                       String alternativePayerAccount)
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Parameters:
    
    alternativePayerAccount -
  - setAuthorizationGroup
```
public void setAuthorizationGroup(@Nullable
                                  String authorizationGroup)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    authorizationGroup -
  - setCollectiveInvoiceVariant
```
public void setCollectiveInvoiceVariant(@Nullable
                                        String collectiveInvoiceVariant)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    collectiveInvoiceVariant -
  - setCustomerAccountNote
```
public void setCustomerAccountNote(@Nullable
                                   String customerAccountNote)
```
    Constraints: Not nullable, Maximum length: 30
    The memo serves only as information on special features of the customer/vendor.
    
    Parameters:
    
    customerAccountNote -
  - setCustomerHeadOffice
```
public void setCustomerHeadOffice(@Nullable
                                  String customerHeadOffice)
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Parameters:
    
    customerHeadOffice -
  - setCustomerSupplierClearingIsUsed
```
public void setCustomerSupplierClearingIsUsed(@Nullable
                                              Boolean customerSupplierClearingIsUsed)
```
    Constraints: none
    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.
    
    Parameters:
    
    customerSupplierClearingIsUsed -
  - setHouseBank
```
public void setHouseBank(@Nullable
                         String houseBank)
```
    Constraints: Not nullable, Maximum length: 5
    
    Parameters:
    
    houseBank -
  - setInterestCalculationCode
```
public void setInterestCalculationCode(@Nullable
                                       String interestCalculationCode)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    interestCalculationCode -
  - setInterestCalculationDate
```
public void setInterestCalculationDate(@Nullable
                                       Calendar interestCalculationDate)
```
    Constraints: Not nullable, Precision: 0
    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.
    
    Parameters:
    
    interestCalculationDate -
  - setIntrstCalcFrequencyInMonths
```
public void setIntrstCalcFrequencyInMonths(@Nullable
                                           String intrstCalcFrequencyInMonths)
```
    Constraints: Not nullable, Maximum length: 2
    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.
    
    Parameters:
    
    intrstCalcFrequencyInMonths -
  - setIsToBeLocallyProcessed
```
public void setIsToBeLocallyProcessed(@Nullable
                                      Boolean isToBeLocallyProcessed)
```
    Constraints: none
    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.
    
    Parameters:
    
    isToBeLocallyProcessed -
  - setItemIsToBePaidSeparately
```
public void setItemIsToBePaidSeparately(@Nullable
                                        Boolean itemIsToBePaidSeparately)
```
    Constraints: none
    
    Parameters:
    
    itemIsToBePaidSeparately -
  - setLayoutSortingRule
```
public void setLayoutSortingRule(@Nullable
                                 String layoutSortingRule)
```
    Constraints: Not nullable, Maximum length: 3
    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.
    
    Parameters:
    
    layoutSortingRule -
  - setPaymentBlockingReason
```
public void setPaymentBlockingReason(@Nullable
                                     String paymentBlockingReason)
```
    Constraints: Not nullable, Maximum length: 1
    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.
    
    Parameters:
    
    paymentBlockingReason -
  - setPaymentMethodsList
```
public void setPaymentMethodsList(@Nullable
                                  String paymentMethodsList)
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Parameters:
    
    paymentMethodsList -
  - setPaymentTerms
```
public void setPaymentTerms(@Nullable
                            String paymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Parameters:
    
    paymentTerms -
  - setPaytAdviceIsSentbyEDI
```
public void setPaytAdviceIsSentbyEDI(@Nullable
                                     Boolean paytAdviceIsSentbyEDI)
```
    Constraints: none
    
    Parameters:
    
    paytAdviceIsSentbyEDI -
  - setPhysicalInventoryBlockInd
```
public void setPhysicalInventoryBlockInd(@Nullable
                                         Boolean physicalInventoryBlockInd)
```
    Constraints: none
    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.
    
    Parameters:
    
    physicalInventoryBlockInd -
  - setReconciliationAccount
```
public void setReconciliationAccount(@Nullable
                                     String reconciliationAccount)
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Parameters:
    
    reconciliationAccount -
  - setRecordPaymentHistoryIndicator
```
public void setRecordPaymentHistoryIndicator(@Nullable
                                             Boolean recordPaymentHistoryIndicator)
```
    Constraints: none
    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.
    
    Parameters:
    
    recordPaymentHistoryIndicator -
  - setUserAtCustomer
```
public void setUserAtCustomer(@Nullable
                              String userAtCustomer)
```
    Constraints: Not nullable, Maximum length: 15
    
    Parameters:
    
    userAtCustomer -
  - setDeletionIndicator
```
public void setDeletionIndicator(@Nullable
                                 Boolean deletionIndicator)
```
    Constraints: none
    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.
    
    Parameters:
    
    deletionIndicator -
  - setCustomerAccountGroup
```
public void setCustomerAccountGroup(@Nullable
                                    String customerAccountGroup)
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Parameters:
    
    customerAccountGroup -
  - setErpConfigContext
```
public void setErpConfigContext(@Nullable
                                ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Parameters:
    
    erpConfigContext -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<CustomerCompany>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<CustomerCompany>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<CustomerCompany>

Class CustomerCompany

Nested Class Summary

Field Summary

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

CUSTOMER

COMPANY_CODE

APAR_TOLERANCE_GROUP

ACCOUNT_BY_CUSTOMER

ACCOUNTING_CLERK

ACCOUNTING_CLERK_FAX_NUMBER

ACCOUNTING_CLERK_INTERNET_ADDRESS

ACCOUNTING_CLERK_PHONE_NUMBER

ALTERNATIVE_PAYER_ACCOUNT

AUTHORIZATION_GROUP

COLLECTIVE_INVOICE_VARIANT

CUSTOMER_ACCOUNT_NOTE

CUSTOMER_HEAD_OFFICE

CUSTOMER_SUPPLIER_CLEARING_IS_USED

HOUSE_BANK

INTEREST_CALCULATION_CODE

INTEREST_CALCULATION_DATE

INTRST_CALC_FREQUENCY_IN_MONTHS

IS_TO_BE_LOCALLY_PROCESSED

ITEM_IS_TO_BE_PAID_SEPARATELY

LAYOUT_SORTING_RULE

PAYMENT_BLOCKING_REASON

PAYMENT_METHODS_LIST

PAYMENT_TERMS

PAYT_ADVICE_IS_SENTBY_EDI

PHYSICAL_INVENTORY_BLOCK_IND

RECONCILIATION_ACCOUNT

RECORD_PAYMENT_HISTORY_INDICATOR

USER_AT_CUSTOMER

DELETION_INDICATOR

CUSTOMER_ACCOUNT_GROUP

TO_CUSTOMER_DUNNING

TO_WITH_HOLDING_TAX

Constructor Detail

CustomerCompany

CustomerCompany

Method Detail

getType

field

fetchCustomerDunning

getCustomerDunningOrFetch

getCustomerDunningOrNull

setCustomerDunning

addCustomerDunning

fetchWithHoldingTax

getWithHoldingTaxOrFetch

getWithHoldingTaxOrNull

setWithHoldingTax

addWithHoldingTax

builder

getCustomer

getCompanyCode

getAPARToleranceGroup

getAccountByCustomer

getAccountingClerk

getAccountingClerkFaxNumber

getAccountingClerkInternetAddress

getAccountingClerkPhoneNumber

getAlternativePayerAccount

getAuthorizationGroup

getCollectiveInvoiceVariant

getCustomerAccountNote

getCustomerHeadOffice

getCustomerSupplierClearingIsUsed

getHouseBank

getInterestCalculationCode

getInterestCalculationDate

getIntrstCalcFrequencyInMonths

getIsToBeLocallyProcessed

getItemIsToBePaidSeparately

getLayoutSortingRule