SupplierCompany (SAP Cloud SDK - Parent POM 2.25.0 API)

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

```
public class SupplierCompany
extends VdmEntity<SupplierCompany>
```
Supplier Company

Original entity name from the Odata EDM: A_SupplierCompanyType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class SupplierCompany.SupplierCompanyBuilder
Helper class to allow for fluent creation of SupplierCompany instances.

Nested Classes
Modifier and Type	Class and Description
`static class`	`SupplierCompany.SupplierCompanyBuilder` Helper class to allow for fluent creation of SupplierCompany instances.

Field Summary

Fields
Modifier and Type	Field and Description
`static SupplierCompanyField<String>`	`ACCOUNTING_CLERK` Use with available fluent helpers to apply the AccountingClerk field to query operations.
`static SupplierCompanyField<String>`	`ACCOUNTING_CLERK_FAX_NUMBER` Use with available fluent helpers to apply the AccountingClerkFaxNumber field to query operations.
`static SupplierCompanyField<String>`	`ACCOUNTING_CLERK_PHONE_NUMBER` Use with available fluent helpers to apply the AccountingClerkPhoneNumber field to query operations.
`static SupplierCompanySelectable`	`ALL_FIELDS` Selector for all available fields of SupplierCompany.
`static SupplierCompanyField<String>`	`ALTERNATIVE_PAYEE` Use with available fluent helpers to apply the AlternativePayee field to query operations.
`static SupplierCompanyField<String>`	`APAR_TOLERANCE_GROUP` Use with available fluent helpers to apply the APARToleranceGroup field to query operations.
`static SupplierCompanyField<String>`	`AUTHORIZATION_GROUP` Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
`static SupplierCompanyField<BigDecimal>`	`BILL_OF_EXCH_LMT_AMT_IN_CO_CODE_CRCY` Use with available fluent helpers to apply the BillOfExchLmtAmtInCoCodeCrcy field to query operations.
`static SupplierCompanyField<String>`	`CASH_PLANNING_GROUP` Use with available fluent helpers to apply the CashPlanningGroup field to query operations.
`static SupplierCompanyField<BigDecimal>`	`CHECK_PAID_DURATION_IN_DAYS` Use with available fluent helpers to apply the CheckPaidDurationInDays field to query operations.
`static SupplierCompanyField<Boolean>`	`CLEAR_CUSTOMER_SUPPLIER` Use with available fluent helpers to apply the ClearCustomerSupplier field to query operations.
`static SupplierCompanyField<String>`	`COMPANY_CODE` Use with available fluent helpers to apply the CompanyCode field to query operations.
`static SupplierCompanyField<String>`	`COMPANY_CODE_NAME` Use with available fluent helpers to apply the CompanyCodeName field to query operations.
`static SupplierCompanyField<Boolean>`	`DELETION_INDICATOR` Use with available fluent helpers to apply the DeletionIndicator field to query operations.
`static SupplierCompanyField<String>`	`HOUSE_BANK` Use with available fluent helpers to apply the HouseBank field to query operations.
`static SupplierCompanyField<String>`	`INTEREST_CALCULATION_CODE` Use with available fluent helpers to apply the InterestCalculationCode field to query operations.
`static SupplierCompanyField<LocalDateTime>`	`INTEREST_CALCULATION_DATE` Use with available fluent helpers to apply the InterestCalculationDate field to query operations.
`static SupplierCompanyField<String>`	`INTRST_CALC_FREQUENCY_IN_MONTHS` Use with available fluent helpers to apply the IntrstCalcFrequencyInMonths field to query operations.
`static SupplierCompanyField<Boolean>`	`IS_TO_BE_CHECKED_FOR_DUPLICATES` Use with available fluent helpers to apply the IsToBeCheckedForDuplicates field to query operations.
`static SupplierCompanyField<Boolean>`	`IS_TO_BE_LOCALLY_PROCESSED` Use with available fluent helpers to apply the IsToBeLocallyProcessed field to query operations.
`static SupplierCompanyField<Boolean>`	`ITEM_IS_TO_BE_PAID_SEPARATELY` Use with available fluent helpers to apply the ItemIsToBePaidSeparately field to query operations.
`static SupplierCompanyField<String>`	`LAYOUT_SORTING_RULE` Use with available fluent helpers to apply the LayoutSortingRule field to query operations.
`static SupplierCompanyField<String>`	`PAYMENT_BLOCKING_REASON` Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
`static SupplierCompanyField<Boolean>`	`PAYMENT_IS_TO_BE_SENT_BY_EDI` Use with available fluent helpers to apply the PaymentIsToBeSentByEDI field to query operations.
`static SupplierCompanyField<String>`	`PAYMENT_METHODS_LIST` Use with available fluent helpers to apply the PaymentMethodsList field to query operations.
`static SupplierCompanyField<String>`	`PAYMENT_TERMS` Use with available fluent helpers to apply the PaymentTerms field to query operations.
`static SupplierCompanyField<String>`	`RECONCILIATION_ACCOUNT` Use with available fluent helpers to apply the ReconciliationAccount field to query operations.
`static SupplierCompanyField<String>`	`SUPPLIER` Use with available fluent helpers to apply the Supplier field to query operations.
`static SupplierCompanyField<String>`	`SUPPLIER_ACCOUNT_GROUP` Use with available fluent helpers to apply the SupplierAccountGroup field to query operations.
`static SupplierCompanyField<String>`	`SUPPLIER_ACCOUNT_NOTE` Use with available fluent helpers to apply the SupplierAccountNote field to query operations.
`static SupplierCompanyField<LocalDateTime>`	`SUPPLIER_CERTIFICATION_DATE` Use with available fluent helpers to apply the SupplierCertificationDate field to query operations.
`static SupplierCompanyField<String>`	`SUPPLIER_CLERK` Use with available fluent helpers to apply the SupplierClerk field to query operations.
`static SupplierCompanyField<String>`	`SUPPLIER_CLERK_ID_BY_SUPPLIER` Use with available fluent helpers to apply the SupplierClerkIDBySupplier field to query operations.
`static SupplierCompanyField<String>`	`SUPPLIER_CLERK_URL` Use with available fluent helpers to apply the SupplierClerkURL field to query operations.
`static SupplierCompanyField<String>`	`SUPPLIER_HEAD_OFFICE` Use with available fluent helpers to apply the SupplierHeadOffice field to query operations.
`static SupplierCompanyField<Boolean>`	`SUPPLIER_IS_BLOCKED_FOR_POSTING` Use with available fluent helpers to apply the SupplierIsBlockedForPosting field to query operations.
`static SupplierCompanyLink<SupplierDunning>`	`TO_SUPPLIER_DUNNING` Use with available fluent helpers to apply the to_SupplierDunning navigation property to query operations.
`static SupplierCompanyLink<SupplierWithHoldingTax>`	`TO_SUPPLIER_WITH_HOLDING_TAX` Use with available fluent helpers to apply the to_SupplierWithHoldingTax navigation property to query operations.
`static SupplierCompanyField<String>`	`WITHHOLDING_TAX_COUNTRY` Use with available fluent helpers to apply the WithholdingTaxCountry field to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`SupplierCompany()`
SupplierCompany(String supplier, String companyCode, String authorizationGroup, String companyCodeName, String paymentBlockingReason, Boolean supplierIsBlockedForPosting, String accountingClerk, String accountingClerkFaxNumber, String accountingClerkPhoneNumber, String supplierClerk, String supplierClerkURL, String paymentMethodsList, String paymentTerms, Boolean clearCustomerSupplier, Boolean isToBeLocallyProcessed, Boolean itemIsToBePaidSeparately, Boolean paymentIsToBeSentByEDI, String houseBank, BigDecimal checkPaidDurationInDays, BigDecimal billOfExchLmtAmtInCoCodeCrcy, String supplierClerkIDBySupplier, String reconciliationAccount, String interestCalculationCode, LocalDateTime interestCalculationDate, String intrstCalcFrequencyInMonths, String supplierHeadOffice, String alternativePayee, String layoutSortingRule, String aPARToleranceGroup, LocalDateTime supplierCertificationDate, String supplierAccountNote, String withholdingTaxCountry, Boolean deletionIndicator, String cashPlanningGroup, Boolean isToBeCheckedForDuplicates, String supplierAccountGroup, List<SupplierDunning> toSupplierDunning, List<SupplierWithHoldingTax> toSupplierWithHoldingTax)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods Deprecated Methods
Modifier and Type	Method and Description
`void`	`addSupplierDunning(SupplierDunning... entity)` Adds elements to the list of associated SupplierDunning entities.
`void`	`addSupplierWithHoldingTax(SupplierWithHoldingTax... entity)` Adds elements to the list of associated SupplierWithHoldingTax entities.
`void`	`attachToService(String servicePath, ErpConfigContext configContext)` Sets the service path and ERP configuration context for the fetch commands of this entity.
`static SupplierCompany.SupplierCompanyBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`List<SupplierDunning>`	`fetchSupplierDunning()` Fetches the SupplierDunning entities (one to many) associated with this entity.
`List<SupplierWithHoldingTax>`	`fetchSupplierWithHoldingTax()` Fetches the SupplierWithHoldingTax entities (one to many) associated with this entity.
`static <T> SupplierCompanyField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> SupplierCompanyField<T>`	`field(String fieldName, TypeConverter<T,DomainT> typeConverter)` Use with available fluent helpers to apply an extension field to query operations.
`protected void`	`fromMap(Map<String,Object> inputValues)`
`String`	`getAccountingClerk()` Constraints: Not nullable, Maximum length: 2
`String`	`getAccountingClerkFaxNumber()` Constraints: Not nullable, Maximum length: 31
`String`	`getAccountingClerkPhoneNumber()` Constraints: Not nullable, Maximum length: 30
`String`	`getAlternativePayee()` Constraints: Not nullable, Maximum length: 10
`String`	`getAPARToleranceGroup()` Constraints: Not nullable, Maximum length: 4
`String`	`getAuthorizationGroup()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getBillOfExchLmtAmtInCoCodeCrcy()` Constraints: Not nullable, Precision: 14, Scale: 3
`String`	`getCashPlanningGroup()` Constraints: Not nullable, Maximum length: 10
`BigDecimal`	`getCheckPaidDurationInDays()` Constraints: Not nullable, Precision: 3, Scale: 0
`Boolean`	`getClearCustomerSupplier()` Constraints: none
`String`	`getCompanyCode()` (Key Field) Constraints: Not nullable, Maximum length: 4
`String`	`getCompanyCodeName()` Constraints: Not nullable, Maximum length: 25
`protected String`	`getDefaultServicePath()`
`Boolean`	`getDeletionIndicator()` Constraints: none
`protected String`	`getEntityCollection()`
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g.
`String`	`getHouseBank()` Constraints: Not nullable, Maximum length: 5
`String`	`getInterestCalculationCode()` Constraints: Not nullable, Maximum length: 2
`LocalDateTime`	`getInterestCalculationDate()` Constraints: Not nullable, Precision: 0
`String`	`getIntrstCalcFrequencyInMonths()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getIsToBeCheckedForDuplicates()` Constraints: none
`Boolean`	`getIsToBeLocallyProcessed()` Constraints: none
`Boolean`	`getItemIsToBePaidSeparately()` Constraints: none
`protected Map<String,Object>`	`getKey()`
`String`	`getLayoutSortingRule()` Constraints: Not nullable, Maximum length: 3
`String`	`getPaymentBlockingReason()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getPaymentIsToBeSentByEDI()` Constraints: none
`String`	`getPaymentMethodsList()` Constraints: Not nullable, Maximum length: 10
`String`	`getPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`String`	`getReconciliationAccount()` Constraints: Not nullable, Maximum length: 10
`String`	`getSupplier()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getSupplierAccountGroup()` Constraints: Not nullable, Maximum length: 4
`String`	`getSupplierAccountNote()` Constraints: Not nullable, Maximum length: 30
`LocalDateTime`	`getSupplierCertificationDate()` Constraints: Not nullable, Precision: 0
`String`	`getSupplierClerk()` Constraints: Not nullable, Maximum length: 15
`String`	`getSupplierClerkIDBySupplier()` Constraints: Not nullable, Maximum length: 12
`String`	`getSupplierClerkURL()` Constraints: Not nullable, Maximum length: 130
`Optional<List<SupplierDunning>>`	`getSupplierDunningIfPresent()` Retrieval of associated SupplierDunning entities (one to many).
`List<SupplierDunning>`	`getSupplierDunningOrFetch()` Retrieval of associated SupplierDunning entities (one to many).
`String`	`getSupplierHeadOffice()` Constraints: Not nullable, Maximum length: 10
`Boolean`	`getSupplierIsBlockedForPosting()` Constraints: none
`Optional<List<SupplierWithHoldingTax>>`	`getSupplierWithHoldingTaxIfPresent()` Retrieval of associated SupplierWithHoldingTax entities (one to many).
`List<SupplierWithHoldingTax>`	`getSupplierWithHoldingTaxOrFetch()` Retrieval of associated SupplierWithHoldingTax entities (one to many).
`Class<SupplierCompany>`	`getType()`
`String`	`getWithholdingTaxCountry()` Constraints: Not nullable, Maximum length: 3
`int`	`hashCode()`
`void`	`setAccountingClerk(String accountingClerk)` Constraints: Not nullable, Maximum length: 2
`void`	`setAccountingClerkFaxNumber(String accountingClerkFaxNumber)` Constraints: Not nullable, Maximum length: 31
`void`	`setAccountingClerkPhoneNumber(String accountingClerkPhoneNumber)` Constraints: Not nullable, Maximum length: 30
`void`	`setAlternativePayee(String alternativePayee)` Constraints: Not nullable, Maximum length: 10
`void`	`setAPARToleranceGroup(String aPARToleranceGroup)` Constraints: Not nullable, Maximum length: 4
`void`	`setAuthorizationGroup(String authorizationGroup)` Constraints: Not nullable, Maximum length: 4
`void`	`setBillOfExchLmtAmtInCoCodeCrcy(BigDecimal billOfExchLmtAmtInCoCodeCrcy)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setCashPlanningGroup(String cashPlanningGroup)` Constraints: Not nullable, Maximum length: 10
`void`	`setCheckPaidDurationInDays(BigDecimal checkPaidDurationInDays)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setClearCustomerSupplier(Boolean clearCustomerSupplier)` Constraints: none
`void`	`setCompanyCode(String companyCode)` (Key Field) Constraints: Not nullable, Maximum length: 4
`void`	`setCompanyCodeName(String companyCodeName)` Constraints: Not nullable, Maximum length: 25
`void`	`setDeletionIndicator(Boolean deletionIndicator)` Constraints: none
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Deprecated. Use `attachToService(String, ErpConfigContext)` instead.
`void`	`setHouseBank(String houseBank)` Constraints: Not nullable, Maximum length: 5
`void`	`setInterestCalculationCode(String interestCalculationCode)` Constraints: Not nullable, Maximum length: 2
`void`	`setInterestCalculationDate(LocalDateTime interestCalculationDate)` Constraints: Not nullable, Precision: 0
`void`	`setIntrstCalcFrequencyInMonths(String intrstCalcFrequencyInMonths)` Constraints: Not nullable, Maximum length: 2
`void`	`setIsToBeCheckedForDuplicates(Boolean isToBeCheckedForDuplicates)` Constraints: none
`void`	`setIsToBeLocallyProcessed(Boolean isToBeLocallyProcessed)` Constraints: none
`void`	`setItemIsToBePaidSeparately(Boolean itemIsToBePaidSeparately)` Constraints: none
`void`	`setLayoutSortingRule(String layoutSortingRule)` Constraints: Not nullable, Maximum length: 3
`void`	`setPaymentBlockingReason(String paymentBlockingReason)` Constraints: Not nullable, Maximum length: 1
`void`	`setPaymentIsToBeSentByEDI(Boolean paymentIsToBeSentByEDI)` Constraints: none
`void`	`setPaymentMethodsList(String paymentMethodsList)` Constraints: Not nullable, Maximum length: 10
`void`	`setPaymentTerms(String paymentTerms)` Constraints: Not nullable, Maximum length: 4
`void`	`setReconciliationAccount(String reconciliationAccount)` Constraints: Not nullable, Maximum length: 10
`protected void`	`setServicePathForFetch(String servicePathForFetch)` The service path only used for the fetch commands of this entity.
`void`	`setSupplier(String supplier)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setSupplierAccountGroup(String supplierAccountGroup)` Constraints: Not nullable, Maximum length: 4
`void`	`setSupplierAccountNote(String supplierAccountNote)` Constraints: Not nullable, Maximum length: 30
`void`	`setSupplierCertificationDate(LocalDateTime supplierCertificationDate)` Constraints: Not nullable, Precision: 0
`void`	`setSupplierClerk(String supplierClerk)` Constraints: Not nullable, Maximum length: 15
`void`	`setSupplierClerkIDBySupplier(String supplierClerkIDBySupplier)` Constraints: Not nullable, Maximum length: 12
`void`	`setSupplierClerkURL(String supplierClerkURL)` Constraints: Not nullable, Maximum length: 130
`void`	`setSupplierDunning(List<SupplierDunning> value)` Overwrites the list of associated SupplierDunning entities for the loaded navigation property to_SupplierDunning.
`void`	`setSupplierHeadOffice(String supplierHeadOffice)` Constraints: Not nullable, Maximum length: 10
`void`	`setSupplierIsBlockedForPosting(Boolean supplierIsBlockedForPosting)` Constraints: none
`void`	`setSupplierWithHoldingTax(List<SupplierWithHoldingTax> value)` Overwrites the list of associated SupplierWithHoldingTax entities for the loaded navigation property to_SupplierWithHoldingTax.
`void`	`setWithholdingTaxCountry(String withholdingTaxCountry)` Constraints: Not nullable, Maximum length: 3
`protected Map<String,Object>`	`toMapOfFields()`
`protected Map<String,Object>`	`toMapOfNavigationProperties()`
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmEntity
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setVersionIdentifier

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields

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

- Field Detail
  - ALL_FIELDS
```
public static final SupplierCompanySelectable ALL_FIELDS
```
    Selector for all available fields of SupplierCompany.
  - SUPPLIER
```
public static final SupplierCompanyField<String> SUPPLIER
```
    Use with available fluent helpers to apply the Supplier field to query operations.
  - COMPANY_CODE
```
public static final SupplierCompanyField<String> COMPANY_CODE
```
    Use with available fluent helpers to apply the CompanyCode field to query operations.
  - AUTHORIZATION_GROUP
```
public static final SupplierCompanyField<String> AUTHORIZATION_GROUP
```
    Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
  - COMPANY_CODE_NAME
```
public static final SupplierCompanyField<String> COMPANY_CODE_NAME
```
    Use with available fluent helpers to apply the CompanyCodeName field to query operations.
  - PAYMENT_BLOCKING_REASON
```
public static final SupplierCompanyField<String> PAYMENT_BLOCKING_REASON
```
    Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
  - SUPPLIER_IS_BLOCKED_FOR_POSTING
```
public static final SupplierCompanyField<Boolean> SUPPLIER_IS_BLOCKED_FOR_POSTING
```
    Use with available fluent helpers to apply the SupplierIsBlockedForPosting field to query operations.
  - ACCOUNTING_CLERK
```
public static final SupplierCompanyField<String> ACCOUNTING_CLERK
```
    Use with available fluent helpers to apply the AccountingClerk field to query operations.
  - ACCOUNTING_CLERK_FAX_NUMBER
```
public static final SupplierCompanyField<String> ACCOUNTING_CLERK_FAX_NUMBER
```
    Use with available fluent helpers to apply the AccountingClerkFaxNumber field to query operations.
  - ACCOUNTING_CLERK_PHONE_NUMBER
```
public static final SupplierCompanyField<String> ACCOUNTING_CLERK_PHONE_NUMBER
```
    Use with available fluent helpers to apply the AccountingClerkPhoneNumber field to query operations.
  - SUPPLIER_CLERK
```
public static final SupplierCompanyField<String> SUPPLIER_CLERK
```
    Use with available fluent helpers to apply the SupplierClerk field to query operations.
  - SUPPLIER_CLERK_URL
```
public static final SupplierCompanyField<String> SUPPLIER_CLERK_URL
```
    Use with available fluent helpers to apply the SupplierClerkURL field to query operations.
  - PAYMENT_METHODS_LIST
```
public static final SupplierCompanyField<String> PAYMENT_METHODS_LIST
```
    Use with available fluent helpers to apply the PaymentMethodsList field to query operations.
  - PAYMENT_TERMS
```
public static final SupplierCompanyField<String> PAYMENT_TERMS
```
    Use with available fluent helpers to apply the PaymentTerms field to query operations.
  - CLEAR_CUSTOMER_SUPPLIER
```
public static final SupplierCompanyField<Boolean> CLEAR_CUSTOMER_SUPPLIER
```
    Use with available fluent helpers to apply the ClearCustomerSupplier field to query operations.
  - IS_TO_BE_LOCALLY_PROCESSED
```
public static final SupplierCompanyField<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 SupplierCompanyField<Boolean> ITEM_IS_TO_BE_PAID_SEPARATELY
```
    Use with available fluent helpers to apply the ItemIsToBePaidSeparately field to query operations.
  - PAYMENT_IS_TO_BE_SENT_BY_EDI
```
public static final SupplierCompanyField<Boolean> PAYMENT_IS_TO_BE_SENT_BY_EDI
```
    Use with available fluent helpers to apply the PaymentIsToBeSentByEDI field to query operations.
  - HOUSE_BANK
```
public static final SupplierCompanyField<String> HOUSE_BANK
```
    Use with available fluent helpers to apply the HouseBank field to query operations.
  - CHECK_PAID_DURATION_IN_DAYS
```
public static final SupplierCompanyField<BigDecimal> CHECK_PAID_DURATION_IN_DAYS
```
    Use with available fluent helpers to apply the CheckPaidDurationInDays field to query operations.
  - BILL_OF_EXCH_LMT_AMT_IN_CO_CODE_CRCY
```
public static final SupplierCompanyField<BigDecimal> BILL_OF_EXCH_LMT_AMT_IN_CO_CODE_CRCY
```
    Use with available fluent helpers to apply the BillOfExchLmtAmtInCoCodeCrcy field to query operations.
  - SUPPLIER_CLERK_ID_BY_SUPPLIER
```
public static final SupplierCompanyField<String> SUPPLIER_CLERK_ID_BY_SUPPLIER
```
    Use with available fluent helpers to apply the SupplierClerkIDBySupplier field to query operations.
  - RECONCILIATION_ACCOUNT
```
public static final SupplierCompanyField<String> RECONCILIATION_ACCOUNT
```
    Use with available fluent helpers to apply the ReconciliationAccount field to query operations.
  - INTEREST_CALCULATION_CODE
```
public static final SupplierCompanyField<String> INTEREST_CALCULATION_CODE
```
    Use with available fluent helpers to apply the InterestCalculationCode field to query operations.
  - INTEREST_CALCULATION_DATE
```
public static final SupplierCompanyField<LocalDateTime> INTEREST_CALCULATION_DATE
```
    Use with available fluent helpers to apply the InterestCalculationDate field to query operations.
  - INTRST_CALC_FREQUENCY_IN_MONTHS
```
public static final SupplierCompanyField<String> INTRST_CALC_FREQUENCY_IN_MONTHS
```
    Use with available fluent helpers to apply the IntrstCalcFrequencyInMonths field to query operations.
  - SUPPLIER_HEAD_OFFICE
```
public static final SupplierCompanyField<String> SUPPLIER_HEAD_OFFICE
```
    Use with available fluent helpers to apply the SupplierHeadOffice field to query operations.
  - ALTERNATIVE_PAYEE
```
public static final SupplierCompanyField<String> ALTERNATIVE_PAYEE
```
    Use with available fluent helpers to apply the AlternativePayee field to query operations.
  - LAYOUT_SORTING_RULE
```
public static final SupplierCompanyField<String> LAYOUT_SORTING_RULE
```
    Use with available fluent helpers to apply the LayoutSortingRule field to query operations.
  - APAR_TOLERANCE_GROUP
```
public static final SupplierCompanyField<String> APAR_TOLERANCE_GROUP
```
    Use with available fluent helpers to apply the APARToleranceGroup field to query operations.
  - SUPPLIER_CERTIFICATION_DATE
```
public static final SupplierCompanyField<LocalDateTime> SUPPLIER_CERTIFICATION_DATE
```
    Use with available fluent helpers to apply the SupplierCertificationDate field to query operations.
  - SUPPLIER_ACCOUNT_NOTE
```
public static final SupplierCompanyField<String> SUPPLIER_ACCOUNT_NOTE
```
    Use with available fluent helpers to apply the SupplierAccountNote field to query operations.
  - WITHHOLDING_TAX_COUNTRY
```
public static final SupplierCompanyField<String> WITHHOLDING_TAX_COUNTRY
```
    Use with available fluent helpers to apply the WithholdingTaxCountry field to query operations.
  - DELETION_INDICATOR
```
public static final SupplierCompanyField<Boolean> DELETION_INDICATOR
```
    Use with available fluent helpers to apply the DeletionIndicator field to query operations.
  - CASH_PLANNING_GROUP
```
public static final SupplierCompanyField<String> CASH_PLANNING_GROUP
```
    Use with available fluent helpers to apply the CashPlanningGroup field to query operations.
  - IS_TO_BE_CHECKED_FOR_DUPLICATES
```
public static final SupplierCompanyField<Boolean> IS_TO_BE_CHECKED_FOR_DUPLICATES
```
    Use with available fluent helpers to apply the IsToBeCheckedForDuplicates field to query operations.
  - SUPPLIER_ACCOUNT_GROUP
```
public static final SupplierCompanyField<String> SUPPLIER_ACCOUNT_GROUP
```
    Use with available fluent helpers to apply the SupplierAccountGroup field to query operations.
  - TO_SUPPLIER_DUNNING
```
public static final SupplierCompanyLink<SupplierDunning> TO_SUPPLIER_DUNNING
```
    Use with available fluent helpers to apply the to_SupplierDunning navigation property to query operations.
  - TO_SUPPLIER_WITH_HOLDING_TAX
```
public static final SupplierCompanyLink<SupplierWithHoldingTax> TO_SUPPLIER_WITH_HOLDING_TAX
```
    Use with available fluent helpers to apply the to_SupplierWithHoldingTax navigation property to query operations.
- Constructor Detail
  - SupplierCompany
```
public SupplierCompany()
```
  - SupplierCompany
```
public SupplierCompany(@Nullable
                       String supplier,
                       @Nullable
                       String companyCode,
                       @Nullable
                       String authorizationGroup,
                       @Nullable
                       String companyCodeName,
                       @Nullable
                       String paymentBlockingReason,
                       @Nullable
                       Boolean supplierIsBlockedForPosting,
                       @Nullable
                       String accountingClerk,
                       @Nullable
                       String accountingClerkFaxNumber,
                       @Nullable
                       String accountingClerkPhoneNumber,
                       @Nullable
                       String supplierClerk,
                       @Nullable
                       String supplierClerkURL,
                       @Nullable
                       String paymentMethodsList,
                       @Nullable
                       String paymentTerms,
                       @Nullable
                       Boolean clearCustomerSupplier,
                       @Nullable
                       Boolean isToBeLocallyProcessed,
                       @Nullable
                       Boolean itemIsToBePaidSeparately,
                       @Nullable
                       Boolean paymentIsToBeSentByEDI,
                       @Nullable
                       String houseBank,
                       @Nullable
                       BigDecimal checkPaidDurationInDays,
                       @Nullable
                       BigDecimal billOfExchLmtAmtInCoCodeCrcy,
                       @Nullable
                       String supplierClerkIDBySupplier,
                       @Nullable
                       String reconciliationAccount,
                       @Nullable
                       String interestCalculationCode,
                       @Nullable
                       LocalDateTime interestCalculationDate,
                       @Nullable
                       String intrstCalcFrequencyInMonths,
                       @Nullable
                       String supplierHeadOffice,
                       @Nullable
                       String alternativePayee,
                       @Nullable
                       String layoutSortingRule,
                       @Nullable
                       String aPARToleranceGroup,
                       @Nullable
                       LocalDateTime supplierCertificationDate,
                       @Nullable
                       String supplierAccountNote,
                       @Nullable
                       String withholdingTaxCountry,
                       @Nullable
                       Boolean deletionIndicator,
                       @Nullable
                       String cashPlanningGroup,
                       @Nullable
                       Boolean isToBeCheckedForDuplicates,
                       @Nullable
                       String supplierAccountGroup,
                       List<SupplierDunning> toSupplierDunning,
                       List<SupplierWithHoldingTax> toSupplierWithHoldingTax)
```
- Method Detail
  - getType
```
@Nonnull
public Class<SupplierCompany> getType()
```
    Specified by:
    
    getType in class VdmObject<SupplierCompany>
    
    Returns:
    
    The class of this object.
  - setSupplier
```
public void setSupplier(@Nullable
                        String supplier)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Supplier
    
    Parameters:
    
    supplier - Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.
  - setCompanyCode
```
public void setCompanyCode(@Nullable
                           String companyCode)
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CompanyCode
    
    Parameters:
    
    companyCode - The company code is an organizational unit within financial accounting.
  - setAuthorizationGroup
```
public void setAuthorizationGroup(@Nullable
                                  String authorizationGroup)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: AuthorizationGroup
    
    Parameters:
    
    authorizationGroup - 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.
  - setCompanyCodeName
```
public void setCompanyCodeName(@Nullable
                               String companyCodeName)
```
    Constraints: Not nullable, Maximum length: 25
    Original property name from the Odata EDM: CompanyCodeName
    
    Parameters:
    
    companyCodeName - Name of Company Code or Company
  - setPaymentBlockingReason
```
public void setPaymentBlockingReason(@Nullable
                                     String paymentBlockingReason)
```
    Constraints: Not nullable, Maximum length: 1
    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.
    
    Parameters:
    
    paymentBlockingReason - Block key (enqueue key) that is used to block an open item or an account to payment transactions.
  - setSupplierIsBlockedForPosting
```
public void setSupplierIsBlockedForPosting(@Nullable
                                           Boolean supplierIsBlockedForPosting)
```
    Constraints: none
    Original property name from the Odata EDM: SupplierIsBlockedForPosting
    
    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:
    
    supplierIsBlockedForPosting - Indicates that the account is blocked for posting in the specified company code.
  - setAccountingClerk
```
public void setAccountingClerk(@Nullable
                               String accountingClerk)
```
    Constraints: Not nullable, Maximum length: 2
    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).
    
    Parameters:
    
    accountingClerk - Identification code for the accounting clerk.
  - setAccountingClerkFaxNumber
```
public void setAccountingClerkFaxNumber(@Nullable
                                        String accountingClerkFaxNumber)
```
    Constraints: Not nullable, Maximum length: 31
    Original property name from the Odata EDM: AccountingClerkFaxNumber
    
    Parameters:
    
    accountingClerkFaxNumber - Accounting clerk's fax number at the customer/vendor
  - setAccountingClerkPhoneNumber
```
public void setAccountingClerkPhoneNumber(@Nullable
                                          String accountingClerkPhoneNumber)
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: AccountingClerkPhoneNumber
    
    Parameters:
    
    accountingClerkPhoneNumber - Accounting clerk's telephone number at business partner
  - setSupplierClerk
```
public void setSupplierClerk(@Nullable
                             String supplierClerk)
```
    Constraints: Not nullable, Maximum length: 15
    Original property name from the Odata EDM: SupplierClerk
    
    Parameters:
    
    supplierClerk - Name or identification code of the accounting clerk at the vendor.
  - setSupplierClerkURL
```
public void setSupplierClerkURL(@Nullable
                                String supplierClerkURL)
```
    Constraints: Not nullable, Maximum length: 130
    Original property name from the Odata EDM: SupplierClerkURL
    
    Parameters:
    
    supplierClerkURL - Internet address of partner company clerk
  - setPaymentMethodsList
```
public void setPaymentMethodsList(@Nullable
                                  String paymentMethodsList)
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Parameters:
    
    paymentMethodsList - 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.
  - setPaymentTerms
```
public void setPaymentTerms(@Nullable
                            String paymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Parameters:
    
    paymentTerms - Key for defining payment terms composed of cash discount percentages and payment periods.
  - setClearCustomerSupplier
```
public void setClearCustomerSupplier(@Nullable
                                     Boolean clearCustomerSupplier)
```
    Constraints: none
    Original property name from the Odata EDM: ClearCustomerSupplier
    
    To use this function in automatic payment transactions, you have toenter the customer account number in the vendor master record,enter the vendor account number in the customer master record, andselect the "Clearing with vendor" indicator in the customer master record.If this indicator is set, items belonging to the customer account will be included in any dunning run.
    
    Parameters:
    
    clearCustomerSupplier - Indicates that during automatic payment transactions, clearing is made with the corresponding customer account, and that during manual clearing procedures, the items of that customer account are also selected.
  - setIsToBeLocallyProcessed
```
public void setIsToBeLocallyProcessed(@Nullable
                                      Boolean isToBeLocallyProcessed)
```
    Constraints: none
    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.
    
    Parameters:
    
    isToBeLocallyProcessed - Indicates that payment transactions and dunning notices are created for the branch.
  - setItemIsToBePaidSeparately
```
public void setItemIsToBePaidSeparately(@Nullable
                                        Boolean itemIsToBePaidSeparately)
```
    Constraints: none
    Original property name from the Odata EDM: ItemIsToBePaidSeparately
    
    Parameters:
    
    itemIsToBePaidSeparately - 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.
  - setPaymentIsToBeSentByEDI
```
public void setPaymentIsToBeSentByEDI(@Nullable
                                      Boolean paymentIsToBeSentByEDI)
```
    Constraints: none
    Original property name from the Odata EDM: PaymentIsToBeSentByEDI
    
    Parameters:
    
    paymentIsToBeSentByEDI - This indicator specifies that the customer/vendor should be sent all payment advice information by EDI.
  - setHouseBank
```
public void setHouseBank(@Nullable
                         String houseBank)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: HouseBank
    
    Parameters:
    
    houseBank - All bank data is determined using this key.
  - setCheckPaidDurationInDays
```
public void setCheckPaidDurationInDays(@Nullable
                                       BigDecimal checkPaidDurationInDays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: CheckPaidDurationInDays
    
    During automatic payment transactions, the system calculates the value date for check payments using this information and stores the date in the line item. The date is calculated as follows:Value date = posting date + check cashing timeIn Cash Management, the value date is used as information about the expected cash outflow.
    
    Parameters:
    
    checkPaidDurationInDays - Number of days which usually pass until the vendor has cashed your check.
  - setBillOfExchLmtAmtInCoCodeCrcy
```
public void setBillOfExchLmtAmtInCoCodeCrcy(@Nullable
                                            BigDecimal billOfExchLmtAmtInCoCodeCrcy)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: BillOfExchLmtAmtInCoCodeCrcy
    
    The amount limit is taken into consideration in automatic payment transactions for payments by bill of exchange and bill of exchange payment requests. Several bill of exchange forms are created if the amount to be settled is higher than the maximum amount given here. Each of these bills of exchange is issued for the maximum amount or for a smaller amount.Amount limits for bills of exchange are used in Spain, for example.
    
    Parameters:
    
    billOfExchLmtAmtInCoCodeCrcy - Maximum amount which may be issued on a bill of exchange if it is to be used in payment transactions with the business partner.
  - setSupplierClerkIDBySupplier
```
public void setSupplierClerkIDBySupplier(@Nullable
                                         String supplierClerkIDBySupplier)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: SupplierClerkIDBySupplier
    
    Parameters:
    
    supplierClerkIDBySupplier - This field contains the account number the company is listed under at the vendor.
  - setReconciliationAccount
```
public void setReconciliationAccount(@Nullable
                                     String reconciliationAccount)
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    Parameters:
    
    reconciliationAccount - 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).
  - setInterestCalculationCode
```
public void setInterestCalculationCode(@Nullable
                                       String interestCalculationCode)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InterestCalculationCode
    
    Parameters:
    
    interestCalculationCode - Enter an interest calculation indicator here if the account is to be included in automatic interest calculation.
  - setInterestCalculationDate
```
public void setInterestCalculationDate(@Nullable
                                       LocalDateTime interestCalculationDate)
```
    Constraints: Not nullable, Precision: 0
    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.
    
    Parameters:
    
    interestCalculationDate - 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.
  - setIntrstCalcFrequencyInMonths
```
public void setIntrstCalcFrequencyInMonths(@Nullable
                                           String intrstCalcFrequencyInMonths)
```
    Constraints: Not nullable, Maximum length: 2
    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.
    
    Parameters:
    
    intrstCalcFrequencyInMonths - 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.
  - setSupplierHeadOffice
```
public void setSupplierHeadOffice(@Nullable
                                  String supplierHeadOffice)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SupplierHeadOffice
    
    You specify this account number only for branch accounts. Items that you post using the branch account number are automatically posted to the head office account. The system records the branch account number in the line items.Neither transactions nor balances are kept in the branch account.
    
    Parameters:
    
    supplierHeadOffice - This field contains the account number of the master record for the head office account.
  - setAlternativePayee
```
public void setAlternativePayee(@Nullable
                                String alternativePayee)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: AlternativePayee
    
    The field is only needed if payments are not to be made directly to the vendor to whom the payable is owed. The same applies to bank collections of receivables.The specification in this field applies only to the company code. There is a further field in which you can enter an alternative payee for each company code. If both fields are filled, the company code specified has priority.
    
    Parameters:
    
    alternativePayee - The account number of the vendor with whom automatic payment transactions are to be carried out.
  - setLayoutSortingRule
```
public void setLayoutSortingRule(@Nullable
                                 String layoutSortingRule)
```
    Constraints: Not nullable, Maximum length: 3
    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.
    
    Parameters:
    
    layoutSortingRule - Indicates the layout rule for the Allocation field in the document line item.
  - setAPARToleranceGroup
```
public void setAPARToleranceGroup(@Nullable
                                  String aPARToleranceGroup)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: APARToleranceGroup
    
    Parameters:
    
    aPARToleranceGroup - Contains settings that control how the system handles differences between the invoice amount and the amount received from a customer or the amount paid to a supplier. A tolerance group is unique within a company code.
  - setSupplierCertificationDate
```
public void setSupplierCertificationDate(@Nullable
                                         LocalDateTime supplierCertificationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SupplierCertificationDate
    
    Date field in which to enter certification date for small companies run by women or minorities. This certificate must be renewed every two years.
    
    Parameters:
    
    supplierCertificationDate - US government requirement.
  - setSupplierAccountNote
```
public void setSupplierAccountNote(@Nullable
                                   String supplierAccountNote)
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: SupplierAccountNote
    
    The memo serves only as information on special features of the customer/vendor.
    
    Parameters:
    
    supplierAccountNote - Internal memo of the accounting department.
  - setWithholdingTaxCountry
```
public void setWithholdingTaxCountry(@Nullable
                                     String withholdingTaxCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: WithholdingTaxCountry
    
    The calculation can depend on the payee's country.A particular country key can be required by law for reporting which may possibly be different to the key used in the address.Examples: Japan, USA (1042), Argentina
    
    Parameters:
    
    withholdingTaxCountry - In some countries, an additional country is needed for calculating or reporting withholding tax.
  - setDeletionIndicator
```
public void setDeletionIndicator(@Nullable
                                 Boolean deletionIndicator)
```
    Constraints: none
    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.
    
    Parameters:
    
    deletionIndicator - Indicates that the company code data in this master record is to be deleted.
  - setCashPlanningGroup
```
public void setCashPlanningGroup(@Nullable
                                 String cashPlanningGroup)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CashPlanningGroup
    
    You can define these planning groups in Customizing or the Implementation Guide (you will need to ensure that they are all the same length). In order to improve the liquidity forecast display for major customers and vendors, it can be advisable to enter their account number as the planning group.For the planning groups themselves a naming convention should be set up to improve liquidity forecasting. In the following examples, the customer planning groups begin with an "R" for receipts, and the vendor planning groups begin with an "E" for expenses.R1 Customers paying by bank collectionR2 Other domestic customersR3 Customers abroadR4 Affiliated company customersR5 High risk customersR6 Major customersR7 Rental incomeR8 Repayment of loans...E1 Domestic vendorsE2 Vendors abroadE3 Affiliated company vendorsE4 Major vendorsE5 Personnel costsE6 TaxesE7 Investments...
    
    Parameters:
    
    cashPlanningGroup - In cash management, customers and vendors are allocated to planning groups by means of an entry made in the master record.
  - setIsToBeCheckedForDuplicates
```
public void setIsToBeCheckedForDuplicates(@Nullable
                                          Boolean isToBeCheckedForDuplicates)
```
    Constraints: none
    Original property name from the Odata EDM: IsToBeCheckedForDuplicates
    
    Checking Logistics DocumentsThe system checks whether the invoice documents have already been entered in the Logistics invoice verification. For this, the system checks invoices that have been held or parked or that contain errors, or invoices that were entered for invoice verification in the background. The check is performed only if you specify the reference document number when you enter the invoices.When checking for duplicate invoices, the system compares the following specified characteristics:VendorCurrencyCompany CodeGross Invoice AmountReference Document NumberInvoice Document DateIf all of these characteristics are the same, the system issues a message for which you can change the message type in Customizing.When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.Exception: The exception is the Argentina country version, where the system checks for duplicate invoices and credit memos.No message is issued if you enter a document that has previously been reversed.In Customizing for Logistics Invoice Verification under Incoming Invoice -> Set Check for Duplicate Invoices, you can specify that the following characteristics are not checked:Reference Document NumberInvoice Document DateCompany CodeHaving fewer attributes to check increases the likelihood that the system will find a duplicate invoice.Example:The following document has already been entered and posted:Reference Document Number 333Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: ChicagoYou have set up the check for duplicate invoices as follows in Customizing:The characteristics Reference Document Number and Company Code are not activated. Consequently, these characteristics are not checked.Now you enter the following invoice:Reference Document Number 334Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: FlagstaffResultBecause you entered a reference document when you entered the invoice, the system checks for duplicate invoices. Compared against the invoice entered earlier, the invoice just entered has different values in the characteristics Reference and Company Code. However, these characteristics are not checked due to the settings that you have made in Customizing. All other characteristics are the same. The system issues a message telling you that an invoice has been entered twice.If the characteristic "Reference Document Number" had been selected in Customizing, the system would have checked the reference document number and established that it was different from the invoice entered earlier, and it consequently would not have issued a message.Checking FI DocumentsThe system checks whether there are FI documents that were posted or parked with the Logistics invoice verification or with an FI invoice transaction. Depending on the entry in the Reference field, one of the following checks is performed:If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateReference NumberIf no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateAmount in Document CurrencyIn Materials Management, the system applies the check for duplicate invoices for invoices only, not for credit memos.
    
    Parameters:
    
    isToBeCheckedForDuplicates - When incoming invoices are entered or when memos are entered in Financial Accounting (FI), the system checks whether an invoice or credit memo has already been entered for the same date.
  - setSupplierAccountGroup
```
public void setSupplierAccountGroup(@Nullable
                                    String supplierAccountGroup)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SupplierAccountGroup
    
    the number interval for the account number of the vendor,whether the number is assigned by the user or by the system,which specifications are necessary and/or possible in the master record.
    
    Parameters:
    
    supplierAccountGroup - The account group is a classifying feature within vendor master records. The account group determines:
  - getEntityCollection
```
protected String getEntityCollection()
```
    Specified by:
    
    getEntityCollection in class VdmEntity<SupplierCompany>
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<SupplierCompany>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<SupplierCompany>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<SupplierCompany>
  - field
```
@Nonnull
public static <T> SupplierCompanyField<T> field(@Nonnull
                                                         String fieldName,
                                                         @Nonnull
                                                         Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    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.
  - field
```
@Nonnull
public static <T,DomainT> SupplierCompanyField<T> field(@Nonnull
                                                                 String fieldName,
                                                                 @Nonnull
                                                                 TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    DomainT - The type of the extension field as returned by the OData service.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities). New ERP configuration context to apply to this entity
    
    Overrides:
    
    getErpConfigContext in class VdmEntity<SupplierCompany>
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setErpConfigContext
```
@Deprecated
public void setErpConfigContext(@Nullable
                                            ErpConfigContext erpConfigContext)
```
    Deprecated. Use attachToService(String, ErpConfigContext) instead.
    
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Overrides:
    
    setErpConfigContext in class VdmEntity<SupplierCompany>
    
    Parameters:
    
    erpConfigContext - New ERP configuration context to apply to this entity
  - setServicePathForFetch
```
protected void setServicePathForFetch(@Nullable
                                      String servicePathForFetch)
```
    Description copied from class: VdmEntity
    
    The service path only used for the fetch commands of this entity.
    Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    setServicePathForFetch in class VdmEntity<SupplierCompany>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nullable
                            ErpConfigContext configContext)
```
    Description copied from class: VdmEntity
    
    Sets the service path and ERP configuration context for the fetch commands of this entity. Ensures that both are set to some value by using defaults if null values are provided in the arguments. Existing values are preserved if null values are provided in the arguments. Also applies to any associated entities (navigation properties) that were previously fetched.
    Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    attachToService in class VdmEntity<SupplierCompany>
    
    Parameters:
    
    servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the service path has never been set, then the service path will be set to the default defined in the corresponding service interface.
    
    configContext - Optional parameter. New ERP configuration context to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the ERP configuration context has never been set, then the ERP configuration context will be set to a new instance of ErpConfigContext.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Overrides:
    
    getDefaultServicePath in class VdmEntity<SupplierCompany>
  - toMapOfNavigationProperties
```
@Nonnull
protected Map<String,Object> toMapOfNavigationProperties()
```
    Overrides:
    
    toMapOfNavigationProperties in class VdmObject<SupplierCompany>
  - fetchSupplierDunning
```
@Nonnull
public List<SupplierDunning> fetchSupplierDunning()
                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SupplierDunning entities (one to many) associated with this entity. This corresponds to the OData navigation property to_SupplierDunning.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SupplierDunning 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.
  - getSupplierDunningOrFetch
```
@Nonnull
public List<SupplierDunning> getSupplierDunningOrFetch()
                                                         throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SupplierDunning entities (one to many). This corresponds to the OData navigation property to_SupplierDunning.
    If the navigation property to_SupplierDunning of a queried SupplierCompany 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 SupplierDunning 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.
  - getSupplierDunningIfPresent
```
@Nonnull
public Optional<List<SupplierDunning>> getSupplierDunningIfPresent()
```
    Retrieval of associated SupplierDunning entities (one to many). This corresponds to the OData navigation property to_SupplierDunning.
    If the navigation property for an entity SupplierCompany has not been resolved yet, this method will not query further information. Instead its Optional result state will be empty.
    
    Returns:
    
    If the information for navigation property to_SupplierDunning is already loaded, the result will contain the SupplierDunning entities. If not, an Optional with result state empty is returned.
  - setSupplierDunning
```
public void setSupplierDunning(@Nonnull
                               List<SupplierDunning> value)
```
    Overwrites the list of associated SupplierDunning entities for the loaded navigation property to_SupplierDunning.
    If the navigation property to_SupplierDunning of a queried SupplierCompany 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 SupplierDunning entities.
  - addSupplierDunning
```
public void addSupplierDunning(SupplierDunning... entity)
```
    Adds elements to the list of associated SupplierDunning entities. This corresponds to the OData navigation property to_SupplierDunning.
    If the navigation property to_SupplierDunning of a queried SupplierCompany 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 SupplierDunning entities.
  - fetchSupplierWithHoldingTax
```
@Nonnull
public List<SupplierWithHoldingTax> fetchSupplierWithHoldingTax()
                                                                  throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SupplierWithHoldingTax entities (one to many) associated with this entity. This corresponds to the OData navigation property to_SupplierWithHoldingTax.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SupplierWithHoldingTax 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.
  - getSupplierWithHoldingTaxOrFetch
```
@Nonnull
public List<SupplierWithHoldingTax> getSupplierWithHoldingTaxOrFetch()
                                                                       throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SupplierWithHoldingTax entities (one to many). This corresponds to the OData navigation property to_SupplierWithHoldingTax.
    If the navigation property to_SupplierWithHoldingTax of a queried SupplierCompany 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 SupplierWithHoldingTax 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.
  - getSupplierWithHoldingTaxIfPresent
```
@Nonnull
public Optional<List<SupplierWithHoldingTax>> getSupplierWithHoldingTaxIfPresent()
```
    Retrieval of associated SupplierWithHoldingTax entities (one to many). This corresponds to the OData navigation property to_SupplierWithHoldingTax.
    If the navigation property for an entity SupplierCompany has not been resolved yet, this method will not query further information. Instead its Optional result state will be empty.
    
    Returns:
    
    If the information for navigation property to_SupplierWithHoldingTax is already loaded, the result will contain the SupplierWithHoldingTax entities. If not, an Optional with result state empty is returned.
  - setSupplierWithHoldingTax
```
public void setSupplierWithHoldingTax(@Nonnull
                                      List<SupplierWithHoldingTax> value)
```
    Overwrites the list of associated SupplierWithHoldingTax entities for the loaded navigation property to_SupplierWithHoldingTax.
    If the navigation property to_SupplierWithHoldingTax of a queried SupplierCompany 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 SupplierWithHoldingTax entities.
  - addSupplierWithHoldingTax
```
public void addSupplierWithHoldingTax(SupplierWithHoldingTax... entity)
```
    Adds elements to the list of associated SupplierWithHoldingTax entities. This corresponds to the OData navigation property to_SupplierWithHoldingTax.
    If the navigation property to_SupplierWithHoldingTax of a queried SupplierCompany 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 SupplierWithHoldingTax entities.
  - builder
```
public static SupplierCompany.SupplierCompanyBuilder builder()
```
  - getSupplier
```
@Nullable
public String getSupplier()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Supplier
    
    Returns:
    
    Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.
  - getCompanyCode
```
@Nullable
public String getCompanyCode()
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CompanyCode
    
    Returns:
    
    The company code is an organizational unit within financial accounting.
  - getAuthorizationGroup
```
@Nullable
public String getAuthorizationGroup()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: AuthorizationGroup
    
    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.
  - getCompanyCodeName
```
@Nullable
public String getCompanyCodeName()
```
    Constraints: Not nullable, Maximum length: 25
    Original property name from the Odata EDM: CompanyCodeName
    
    Returns:
    
    Name of Company Code or Company
  - getPaymentBlockingReason
```
@Nullable
public String getPaymentBlockingReason()
```
    Constraints: Not nullable, Maximum length: 1
    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.
    
    Returns:
    
    Block key (enqueue key) that is used to block an open item or an account to payment transactions.
  - getSupplierIsBlockedForPosting
```
@Nullable
public Boolean getSupplierIsBlockedForPosting()
```
    Constraints: none
    Original property name from the Odata EDM: SupplierIsBlockedForPosting
    
    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.
  - getAccountingClerk
```
@Nullable
public String getAccountingClerk()
```
    Constraints: Not nullable, Maximum length: 2
    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).
    
    Returns:
    
    Identification code for the accounting clerk.
  - getAccountingClerkFaxNumber
```
@Nullable
public String getAccountingClerkFaxNumber()
```
    Constraints: Not nullable, Maximum length: 31
    Original property name from the Odata EDM: AccountingClerkFaxNumber
    
    Returns:
    
    Accounting clerk's fax number at the customer/vendor
  - getAccountingClerkPhoneNumber
```
@Nullable
public String getAccountingClerkPhoneNumber()
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: AccountingClerkPhoneNumber
    
    Returns:
    
    Accounting clerk's telephone number at business partner
  - getSupplierClerk
```
@Nullable
public String getSupplierClerk()
```
    Constraints: Not nullable, Maximum length: 15
    Original property name from the Odata EDM: SupplierClerk
    
    Returns:
    
    Name or identification code of the accounting clerk at the vendor.
  - getSupplierClerkURL
```
@Nullable
public String getSupplierClerkURL()
```
    Constraints: Not nullable, Maximum length: 130
    Original property name from the Odata EDM: SupplierClerkURL
    
    Returns:
    
    Internet address of partner company clerk
  - getPaymentMethodsList
```
@Nullable
public String getPaymentMethodsList()
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    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
    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.
    
    Returns:
    
    Key for defining payment terms composed of cash discount percentages and payment periods.
  - getClearCustomerSupplier
```
@Nullable
public Boolean getClearCustomerSupplier()
```
    Constraints: none
    Original property name from the Odata EDM: ClearCustomerSupplier
    
    To use this function in automatic payment transactions, you have toenter the customer account number in the vendor master record,enter the vendor account number in the customer master record, andselect the "Clearing with vendor" indicator in the customer master record.If this indicator is set, items belonging to the customer account will be included in any dunning run.
    
    Returns:
    
    Indicates that during automatic payment transactions, clearing is made with the corresponding customer account, and that during manual clearing procedures, the items of that customer account are also selected.
  - getIsToBeLocallyProcessed
```
@Nullable
public Boolean getIsToBeLocallyProcessed()
```
    Constraints: none
    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.
    
    Returns:
    
    Indicates that payment transactions and dunning notices are created for the branch.
  - getItemIsToBePaidSeparately
```
@Nullable
public Boolean getItemIsToBePaidSeparately()
```
    Constraints: none
    Original property name from the Odata EDM: ItemIsToBePaidSeparately
    
    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.
  - getPaymentIsToBeSentByEDI
```
@Nullable
public Boolean getPaymentIsToBeSentByEDI()
```
    Constraints: none
    Original property name from the Odata EDM: PaymentIsToBeSentByEDI
    
    Returns:
    
    This indicator specifies that the customer/vendor should be sent all payment advice information by EDI.
  - getHouseBank
```
@Nullable
public String getHouseBank()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: HouseBank
    
    Returns:
    
    All bank data is determined using this key.
  - getCheckPaidDurationInDays
```
@Nullable
public BigDecimal getCheckPaidDurationInDays()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: CheckPaidDurationInDays
    
    During automatic payment transactions, the system calculates the value date for check payments using this information and stores the date in the line item. The date is calculated as follows:Value date = posting date + check cashing timeIn Cash Management, the value date is used as information about the expected cash outflow.
    
    Returns:
    
    Number of days which usually pass until the vendor has cashed your check.
  - getBillOfExchLmtAmtInCoCodeCrcy
```
@Nullable
public BigDecimal getBillOfExchLmtAmtInCoCodeCrcy()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: BillOfExchLmtAmtInCoCodeCrcy
    
    The amount limit is taken into consideration in automatic payment transactions for payments by bill of exchange and bill of exchange payment requests. Several bill of exchange forms are created if the amount to be settled is higher than the maximum amount given here. Each of these bills of exchange is issued for the maximum amount or for a smaller amount.Amount limits for bills of exchange are used in Spain, for example.
    
    Returns:
    
    Maximum amount which may be issued on a bill of exchange if it is to be used in payment transactions with the business partner.
  - getSupplierClerkIDBySupplier
```
@Nullable
public String getSupplierClerkIDBySupplier()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: SupplierClerkIDBySupplier
    
    Returns:
    
    This field contains the account number the company is listed under at the vendor.
  - getReconciliationAccount
```
@Nullable
public String getReconciliationAccount()
```
    Constraints: Not nullable, Maximum length: 10
    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.
    
    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).
  - getInterestCalculationCode
```
@Nullable
public String getInterestCalculationCode()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InterestCalculationCode
    
    Returns:
    
    Enter an interest calculation indicator here if the account is to be included in automatic interest calculation.
  - getInterestCalculationDate
```
@Nullable
public LocalDateTime getInterestCalculationDate()
```
    Constraints: Not nullable, Precision: 0
    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.
    
    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
    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.
    
    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.
  - getSupplierHeadOffice
```
@Nullable
public String getSupplierHeadOffice()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SupplierHeadOffice
    
    You specify this account number only for branch accounts. Items that you post using the branch account number are automatically posted to the head office account. The system records the branch account number in the line items.Neither transactions nor balances are kept in the branch account.
    
    Returns:
    
    This field contains the account number of the master record for the head office account.
  - getAlternativePayee
```
@Nullable
public String getAlternativePayee()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: AlternativePayee
    
    The field is only needed if payments are not to be made directly to the vendor to whom the payable is owed. The same applies to bank collections of receivables.The specification in this field applies only to the company code. There is a further field in which you can enter an alternative payee for each company code. If both fields are filled, the company code specified has priority.
    
    Returns:
    
    The account number of the vendor with whom automatic payment transactions are to be carried out.
  - getLayoutSortingRule
```
@Nullable
public String getLayoutSortingRule()
```
    Constraints: Not nullable, Maximum length: 3
    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.
    
    Returns:
    
    Indicates the layout rule for the Allocation field in the document line item.
  - getAPARToleranceGroup
```
@Nullable
public String getAPARToleranceGroup()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: APARToleranceGroup
    
    Returns:
    
    Contains settings that control how the system handles differences between the invoice amount and the amount received from a customer or the amount paid to a supplier. A tolerance group is unique within a company code.
  - getSupplierCertificationDate
```
@Nullable
public LocalDateTime getSupplierCertificationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SupplierCertificationDate
    
    Date field in which to enter certification date for small companies run by women or minorities. This certificate must be renewed every two years.
    
    Returns:
    
    US government requirement.
  - getSupplierAccountNote
```
@Nullable
public String getSupplierAccountNote()
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: SupplierAccountNote
    
    The memo serves only as information on special features of the customer/vendor.
    
    Returns:
    
    Internal memo of the accounting department.
  - getWithholdingTaxCountry
```
@Nullable
public String getWithholdingTaxCountry()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: WithholdingTaxCountry
    
    The calculation can depend on the payee's country.A particular country key can be required by law for reporting which may possibly be different to the key used in the address.Examples: Japan, USA (1042), Argentina
    
    Returns:
    
    In some countries, an additional country is needed for calculating or reporting withholding tax.
  - getDeletionIndicator
```
@Nullable
public Boolean getDeletionIndicator()
```
    Constraints: none
    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.
    
    Returns:
    
    Indicates that the company code data in this master record is to be deleted.
  - getCashPlanningGroup
```
@Nullable
public String getCashPlanningGroup()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CashPlanningGroup
    
    You can define these planning groups in Customizing or the Implementation Guide (you will need to ensure that they are all the same length). In order to improve the liquidity forecast display for major customers and vendors, it can be advisable to enter their account number as the planning group.For the planning groups themselves a naming convention should be set up to improve liquidity forecasting. In the following examples, the customer planning groups begin with an "R" for receipts, and the vendor planning groups begin with an "E" for expenses.R1 Customers paying by bank collectionR2 Other domestic customersR3 Customers abroadR4 Affiliated company customersR5 High risk customersR6 Major customersR7 Rental incomeR8 Repayment of loans...E1 Domestic vendorsE2 Vendors abroadE3 Affiliated company vendorsE4 Major vendorsE5 Personnel costsE6 TaxesE7 Investments...
    
    Returns:
    
    In cash management, customers and vendors are allocated to planning groups by means of an entry made in the master record.
  - getIsToBeCheckedForDuplicates
```
@Nullable
public Boolean getIsToBeCheckedForDuplicates()
```
    Constraints: none
    Original property name from the Odata EDM: IsToBeCheckedForDuplicates
    
    Checking Logistics DocumentsThe system checks whether the invoice documents have already been entered in the Logistics invoice verification. For this, the system checks invoices that have been held or parked or that contain errors, or invoices that were entered for invoice verification in the background. The check is performed only if you specify the reference document number when you enter the invoices.When checking for duplicate invoices, the system compares the following specified characteristics:VendorCurrencyCompany CodeGross Invoice AmountReference Document NumberInvoice Document DateIf all of these characteristics are the same, the system issues a message for which you can change the message type in Customizing.When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.Exception: The exception is the Argentina country version, where the system checks for duplicate invoices and credit memos.No message is issued if you enter a document that has previously been reversed.In Customizing for Logistics Invoice Verification under Incoming Invoice -> Set Check for Duplicate Invoices, you can specify that the following characteristics are not checked:Reference Document NumberInvoice Document DateCompany CodeHaving fewer attributes to check increases the likelihood that the system will find a duplicate invoice.Example:The following document has already been entered and posted:Reference Document Number 333Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: ChicagoYou have set up the check for duplicate invoices as follows in Customizing:The characteristics Reference Document Number and Company Code are not activated. Consequently, these characteristics are not checked.Now you enter the following invoice:Reference Document Number 334Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: FlagstaffResultBecause you entered a reference document when you entered the invoice, the system checks for duplicate invoices. Compared against the invoice entered earlier, the invoice just entered has different values in the characteristics Reference and Company Code. However, these characteristics are not checked due to the settings that you have made in Customizing. All other characteristics are the same. The system issues a message telling you that an invoice has been entered twice.If the characteristic "Reference Document Number" had been selected in Customizing, the system would have checked the reference document number and established that it was different from the invoice entered earlier, and it consequently would not have issued a message.Checking FI DocumentsThe system checks whether there are FI documents that were posted or parked with the Logistics invoice verification or with an FI invoice transaction. Depending on the entry in the Reference field, one of the following checks is performed:If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateReference NumberIf no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateAmount in Document CurrencyIn Materials Management, the system applies the check for duplicate invoices for invoices only, not for credit memos.
    
    Returns:
    
    When incoming invoices are entered or when memos are entered in Financial Accounting (FI), the system checks whether an invoice or credit memo has already been entered for the same date.
  - getSupplierAccountGroup
```
@Nullable
public String getSupplierAccountGroup()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SupplierAccountGroup
    
    the number interval for the account number of the vendor,whether the number is assigned by the user or by the system,which specifications are necessary and/or possible in the master record.
    
    Returns:
    
    The account group is a classifying feature within vendor master records. The account group determines:
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<SupplierCompany>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<SupplierCompany>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<SupplierCompany>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<SupplierCompany>

Class SupplierCompany

Nested Class Summary

Field Summary

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

Constructor Summary

Method Summary

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

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

SUPPLIER

COMPANY_CODE

AUTHORIZATION_GROUP

COMPANY_CODE_NAME

PAYMENT_BLOCKING_REASON

SUPPLIER_IS_BLOCKED_FOR_POSTING

ACCOUNTING_CLERK

ACCOUNTING_CLERK_FAX_NUMBER

ACCOUNTING_CLERK_PHONE_NUMBER

SUPPLIER_CLERK

SUPPLIER_CLERK_URL

PAYMENT_METHODS_LIST

PAYMENT_TERMS

CLEAR_CUSTOMER_SUPPLIER

IS_TO_BE_LOCALLY_PROCESSED

ITEM_IS_TO_BE_PAID_SEPARATELY

PAYMENT_IS_TO_BE_SENT_BY_EDI

HOUSE_BANK

CHECK_PAID_DURATION_IN_DAYS

BILL_OF_EXCH_LMT_AMT_IN_CO_CODE_CRCY

SUPPLIER_CLERK_ID_BY_SUPPLIER

RECONCILIATION_ACCOUNT

INTEREST_CALCULATION_CODE

INTEREST_CALCULATION_DATE

INTRST_CALC_FREQUENCY_IN_MONTHS

SUPPLIER_HEAD_OFFICE

ALTERNATIVE_PAYEE

LAYOUT_SORTING_RULE

APAR_TOLERANCE_GROUP

SUPPLIER_CERTIFICATION_DATE

SUPPLIER_ACCOUNT_NOTE

WITHHOLDING_TAX_COUNTRY

DELETION_INDICATOR

CASH_PLANNING_GROUP

IS_TO_BE_CHECKED_FOR_DUPLICATES

SUPPLIER_ACCOUNT_GROUP

TO_SUPPLIER_DUNNING

TO_SUPPLIER_WITH_HOLDING_TAX

Constructor Detail

SupplierCompany

SupplierCompany

Method Detail

getType

setSupplier

setCompanyCode

setAuthorizationGroup

setCompanyCodeName

setPaymentBlockingReason

setSupplierIsBlockedForPosting

setAccountingClerk

setAccountingClerkFaxNumber

setAccountingClerkPhoneNumber

setSupplierClerk

setSupplierClerkURL

setPaymentMethodsList

setPaymentTerms

setClearCustomerSupplier

setIsToBeLocallyProcessed

setItemIsToBePaidSeparately

setPaymentIsToBeSentByEDI

setHouseBank

setCheckPaidDurationInDays

setBillOfExchLmtAmtInCoCodeCrcy

setSupplierClerkIDBySupplier

setReconciliationAccount

setInterestCalculationCode

setInterestCalculationDate

setIntrstCalcFrequencyInMonths

setSupplierHeadOffice