public class CustomerCompany extends VdmEntity<CustomerCompany>
Original entity name from the Odata EDM: A_CustomerCompanyType
Modifier and Type | Class and Description |
---|---|
static class |
CustomerCompany.CustomerCompanyBuilder
Helper class to allow for fluent creation of CustomerCompany instances.
|
Modifier and Type | Field and Description |
---|---|
static CustomerCompanyField<String> |
ACCOUNT_BY_CUSTOMER
Use with available fluent helpers to apply the AccountByCustomer field to query operations.
|
static CustomerCompanyField<String> |
ACCOUNTING_CLERK
Use with available fluent helpers to apply the AccountingClerk field to query operations.
|
static CustomerCompanyField<String> |
ACCOUNTING_CLERK_FAX_NUMBER
Use with available fluent helpers to apply the AccountingClerkFaxNumber field to query operations.
|
static CustomerCompanyField<String> |
ACCOUNTING_CLERK_INTERNET_ADDRESS
Use with available fluent helpers to apply the AccountingClerkInternetAddress field to query operations.
|
static CustomerCompanyField<String> |
ACCOUNTING_CLERK_PHONE_NUMBER
Use with available fluent helpers to apply the AccountingClerkPhoneNumber field to query operations.
|
static CustomerCompanySelectable |
ALL_FIELDS
Selector for all available fields of CustomerCompany.
|
static CustomerCompanyField<String> |
ALTERNATIVE_PAYER_ACCOUNT
Use with available fluent helpers to apply the AlternativePayerAccount field to query operations.
|
static CustomerCompanyField<String> |
APAR_TOLERANCE_GROUP
Use with available fluent helpers to apply the APARToleranceGroup field to query operations.
|
static CustomerCompanyField<String> |
AUTHORIZATION_GROUP
Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
|
static CustomerCompanyField<String> |
COLLECTIVE_INVOICE_VARIANT
Use with available fluent helpers to apply the CollectiveInvoiceVariant field to query operations.
|
static CustomerCompanyField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static CustomerCompanyField<String> |
CUSTOMER
Use with available fluent helpers to apply the Customer field to query operations.
|
static CustomerCompanyField<String> |
CUSTOMER_ACCOUNT_GROUP
Use with available fluent helpers to apply the CustomerAccountGroup field to query operations.
|
static CustomerCompanyField<String> |
CUSTOMER_ACCOUNT_NOTE
Use with available fluent helpers to apply the CustomerAccountNote field to query operations.
|
static CustomerCompanyField<String> |
CUSTOMER_HEAD_OFFICE
Use with available fluent helpers to apply the CustomerHeadOffice field to query operations.
|
static CustomerCompanyField<Boolean> |
CUSTOMER_SUPPLIER_CLEARING_IS_USED
Use with available fluent helpers to apply the CustomerSupplierClearingIsUsed field to query operations.
|
static CustomerCompanyField<Boolean> |
DELETION_INDICATOR
Use with available fluent helpers to apply the DeletionIndicator field to query operations.
|
static CustomerCompanyField<String> |
HOUSE_BANK
Use with available fluent helpers to apply the HouseBank field to query operations.
|
static CustomerCompanyField<String> |
INTEREST_CALCULATION_CODE
Use with available fluent helpers to apply the InterestCalculationCode field to query operations.
|
static CustomerCompanyField<LocalDateTime> |
INTEREST_CALCULATION_DATE
Use with available fluent helpers to apply the InterestCalculationDate field to query operations.
|
static CustomerCompanyField<String> |
INTRST_CALC_FREQUENCY_IN_MONTHS
Use with available fluent helpers to apply the IntrstCalcFrequencyInMonths field to query operations.
|
static CustomerCompanyField<Boolean> |
IS_TO_BE_LOCALLY_PROCESSED
Use with available fluent helpers to apply the IsToBeLocallyProcessed field to query operations.
|
static CustomerCompanyField<Boolean> |
ITEM_IS_TO_BE_PAID_SEPARATELY
Use with available fluent helpers to apply the ItemIsToBePaidSeparately field to query operations.
|
static CustomerCompanyField<String> |
LAYOUT_SORTING_RULE
Use with available fluent helpers to apply the LayoutSortingRule field to query operations.
|
static CustomerCompanyField<String> |
PAYMENT_BLOCKING_REASON
Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
|
static CustomerCompanyField<String> |
PAYMENT_METHODS_LIST
Use with available fluent helpers to apply the PaymentMethodsList field to query operations.
|
static CustomerCompanyField<String> |
PAYMENT_TERMS
Use with available fluent helpers to apply the PaymentTerms field to query operations.
|
static CustomerCompanyField<Boolean> |
PAYT_ADVICE_IS_SENTBY_EDI
Use with available fluent helpers to apply the PaytAdviceIsSentbyEDI field to query operations.
|
static CustomerCompanyField<Boolean> |
PHYSICAL_INVENTORY_BLOCK_IND
Use with available fluent helpers to apply the PhysicalInventoryBlockInd field to query operations.
|
static CustomerCompanyField<String> |
RECONCILIATION_ACCOUNT
Use with available fluent helpers to apply the ReconciliationAccount field to query operations.
|
static CustomerCompanyField<Boolean> |
RECORD_PAYMENT_HISTORY_INDICATOR
Use with available fluent helpers to apply the RecordPaymentHistoryIndicator field to query operations.
|
static CustomerCompanyLink<CustomerDunning> |
TO_CUSTOMER_DUNNING
Use with available fluent helpers to apply the to_CustomerDunning navigation property to query operations.
|
static CustomerCompanyLink<CustomerWithHoldingTax> |
TO_WITH_HOLDING_TAX
Use with available fluent helpers to apply the to_WithHoldingTax navigation property to query operations.
|
static CustomerCompanyField<String> |
USER_AT_CUSTOMER
Use with available fluent helpers to apply the UserAtCustomer field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
CustomerCompany() |
CustomerCompany(String customer,
String companyCode,
String aPARToleranceGroup,
String accountByCustomer,
String accountingClerk,
String accountingClerkFaxNumber,
String accountingClerkInternetAddress,
String accountingClerkPhoneNumber,
String alternativePayerAccount,
String authorizationGroup,
String collectiveInvoiceVariant,
String customerAccountNote,
String customerHeadOffice,
Boolean customerSupplierClearingIsUsed,
String houseBank,
String interestCalculationCode,
LocalDateTime interestCalculationDate,
String intrstCalcFrequencyInMonths,
Boolean isToBeLocallyProcessed,
Boolean itemIsToBePaidSeparately,
String layoutSortingRule,
String paymentBlockingReason,
String paymentMethodsList,
String paymentTerms,
Boolean paytAdviceIsSentbyEDI,
Boolean physicalInventoryBlockInd,
String reconciliationAccount,
Boolean recordPaymentHistoryIndicator,
String userAtCustomer,
Boolean deletionIndicator,
String customerAccountGroup,
List<CustomerDunning> toCustomerDunning,
List<CustomerWithHoldingTax> toWithHoldingTax) |
Modifier and Type | Method and Description |
---|---|
void |
addCustomerDunning(CustomerDunning... entity)
Adds elements to the list of associated CustomerDunning entities.
|
void |
addWithHoldingTax(CustomerWithHoldingTax... entity)
Adds elements to the list of associated CustomerWithHoldingTax entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static CustomerCompany.CustomerCompanyBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<CustomerDunning> |
fetchCustomerDunning()
Fetches the CustomerDunning entities (one to many) associated with this entity.
|
List<CustomerWithHoldingTax> |
fetchWithHoldingTax()
Fetches the CustomerWithHoldingTax entities (one to many) associated with this entity.
|
static <T> CustomerCompanyField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
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 |
getAccountByCustomer()
Constraints: Not nullable, Maximum length: 12
|
String |
getAccountingClerk()
Constraints: Not nullable, Maximum length: 2
|
String |
getAccountingClerkFaxNumber()
Constraints: Not nullable, Maximum length: 31
|
String |
getAccountingClerkInternetAddress()
Constraints: Not nullable, Maximum length: 130
|
String |
getAccountingClerkPhoneNumber()
Constraints: Not nullable, Maximum length: 30
|
String |
getAlternativePayerAccount()
Constraints: Not nullable, Maximum length: 10
|
String |
getAPARToleranceGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getAuthorizationGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getCollectiveInvoiceVariant()
Constraints: Not nullable, Maximum length: 1
|
String |
getCompanyCode()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getCustomer()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerAccountGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getCustomerAccountNote()
Constraints: Not nullable, Maximum length: 30
|
io.vavr.control.Option<List<CustomerDunning>> |
getCustomerDunningIfPresent()
Retrieval of associated CustomerDunning entities (one to many).
|
List<CustomerDunning> |
getCustomerDunningOrFetch()
Retrieval of associated CustomerDunning entities (one to many).
|
String |
getCustomerHeadOffice()
Constraints: Not nullable, Maximum length: 10
|
Boolean |
getCustomerSupplierClearingIsUsed()
Constraints: none
|
protected String |
getDefaultServicePath() |
Boolean |
getDeletionIndicator()
Constraints: none
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
protected String |
getEntityCollection() |
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 |
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
|
String |
getPaymentMethodsList()
Constraints: Not nullable, Maximum length: 10
|
String |
getPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
Boolean |
getPaytAdviceIsSentbyEDI()
Constraints: none
|
Boolean |
getPhysicalInventoryBlockInd()
Constraints: none
|
String |
getReconciliationAccount()
Constraints: Not nullable, Maximum length: 10
|
Boolean |
getRecordPaymentHistoryIndicator()
Constraints: none
|
Class<CustomerCompany> |
getType() |
String |
getUserAtCustomer()
Constraints: Not nullable, Maximum length: 15
|
io.vavr.control.Option<List<CustomerWithHoldingTax>> |
getWithHoldingTaxIfPresent()
Retrieval of associated CustomerWithHoldingTax entities (one to many).
|
List<CustomerWithHoldingTax> |
getWithHoldingTaxOrFetch()
Retrieval of associated CustomerWithHoldingTax entities (one to many).
|
int |
hashCode() |
void |
setAccountByCustomer(String accountByCustomer)
Constraints: Not nullable, Maximum length: 12
|
void |
setAccountingClerk(String accountingClerk)
Constraints: Not nullable, Maximum length: 2
|
void |
setAccountingClerkFaxNumber(String accountingClerkFaxNumber)
Constraints: Not nullable, Maximum length: 31
|
void |
setAccountingClerkInternetAddress(String accountingClerkInternetAddress)
Constraints: Not nullable, Maximum length: 130
|
void |
setAccountingClerkPhoneNumber(String accountingClerkPhoneNumber)
Constraints: Not nullable, Maximum length: 30
|
void |
setAlternativePayerAccount(String alternativePayerAccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setAPARToleranceGroup(String aPARToleranceGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setAuthorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setCollectiveInvoiceVariant(String collectiveInvoiceVariant)
Constraints: Not nullable, Maximum length: 1
|
void |
setCompanyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setCustomer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerAccountGroup(String customerAccountGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setCustomerAccountNote(String customerAccountNote)
Constraints: Not nullable, Maximum length: 30
|
void |
setCustomerDunning(List<CustomerDunning> value)
Overwrites the list of associated CustomerDunning entities for the loaded navigation property
to_CustomerDunning.
|
void |
setCustomerHeadOffice(String customerHeadOffice)
Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerSupplierClearingIsUsed(Boolean customerSupplierClearingIsUsed)
Constraints: none
|
void |
setDeletionIndicator(Boolean deletionIndicator)
Constraints: none
|
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 |
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 |
setPaymentMethodsList(String paymentMethodsList)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentTerms(String paymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setPaytAdviceIsSentbyEDI(Boolean paytAdviceIsSentbyEDI)
Constraints: none
|
void |
setPhysicalInventoryBlockInd(Boolean physicalInventoryBlockInd)
Constraints: none
|
void |
setReconciliationAccount(String reconciliationAccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setRecordPaymentHistoryIndicator(Boolean recordPaymentHistoryIndicator)
Constraints: none
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setUserAtCustomer(String userAtCustomer)
Constraints: Not nullable, Maximum length: 15
|
void |
setWithHoldingTax(List<CustomerWithHoldingTax> value)
Overwrites the list of associated CustomerWithHoldingTax entities for the loaded navigation property
to_WithHoldingTax.
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final CustomerCompanySelectable ALL_FIELDS
public static final CustomerCompanyField<String> CUSTOMER
public static final CustomerCompanyField<String> COMPANY_CODE
public static final CustomerCompanyField<String> APAR_TOLERANCE_GROUP
public static final CustomerCompanyField<String> ACCOUNT_BY_CUSTOMER
public static final CustomerCompanyField<String> ACCOUNTING_CLERK
public static final CustomerCompanyField<String> ACCOUNTING_CLERK_FAX_NUMBER
public static final CustomerCompanyField<String> ACCOUNTING_CLERK_INTERNET_ADDRESS
public static final CustomerCompanyField<String> ACCOUNTING_CLERK_PHONE_NUMBER
public static final CustomerCompanyField<String> ALTERNATIVE_PAYER_ACCOUNT
public static final CustomerCompanyField<String> AUTHORIZATION_GROUP
public static final CustomerCompanyField<String> COLLECTIVE_INVOICE_VARIANT
public static final CustomerCompanyField<String> CUSTOMER_ACCOUNT_NOTE
public static final CustomerCompanyField<String> CUSTOMER_HEAD_OFFICE
public static final CustomerCompanyField<Boolean> CUSTOMER_SUPPLIER_CLEARING_IS_USED
public static final CustomerCompanyField<String> HOUSE_BANK
public static final CustomerCompanyField<String> INTEREST_CALCULATION_CODE
public static final CustomerCompanyField<LocalDateTime> INTEREST_CALCULATION_DATE
public static final CustomerCompanyField<String> INTRST_CALC_FREQUENCY_IN_MONTHS
public static final CustomerCompanyField<Boolean> IS_TO_BE_LOCALLY_PROCESSED
public static final CustomerCompanyField<Boolean> ITEM_IS_TO_BE_PAID_SEPARATELY
public static final CustomerCompanyField<String> LAYOUT_SORTING_RULE
public static final CustomerCompanyField<String> PAYMENT_BLOCKING_REASON
public static final CustomerCompanyField<String> PAYMENT_METHODS_LIST
public static final CustomerCompanyField<String> PAYMENT_TERMS
public static final CustomerCompanyField<Boolean> PAYT_ADVICE_IS_SENTBY_EDI
public static final CustomerCompanyField<Boolean> PHYSICAL_INVENTORY_BLOCK_IND
public static final CustomerCompanyField<String> RECONCILIATION_ACCOUNT
public static final CustomerCompanyField<Boolean> RECORD_PAYMENT_HISTORY_INDICATOR
public static final CustomerCompanyField<String> USER_AT_CUSTOMER
public static final CustomerCompanyField<Boolean> DELETION_INDICATOR
public static final CustomerCompanyField<String> CUSTOMER_ACCOUNT_GROUP
public static final CustomerCompanyLink<CustomerDunning> TO_CUSTOMER_DUNNING
public static final CustomerCompanyLink<CustomerWithHoldingTax> TO_WITH_HOLDING_TAX
public CustomerCompany()
public CustomerCompany(@Nullable String customer, @Nullable String companyCode, @Nullable String aPARToleranceGroup, @Nullable String accountByCustomer, @Nullable String accountingClerk, @Nullable String accountingClerkFaxNumber, @Nullable String accountingClerkInternetAddress, @Nullable String accountingClerkPhoneNumber, @Nullable String alternativePayerAccount, @Nullable String authorizationGroup, @Nullable String collectiveInvoiceVariant, @Nullable String customerAccountNote, @Nullable String customerHeadOffice, @Nullable Boolean customerSupplierClearingIsUsed, @Nullable String houseBank, @Nullable String interestCalculationCode, @Nullable LocalDateTime interestCalculationDate, @Nullable String intrstCalcFrequencyInMonths, @Nullable Boolean isToBeLocallyProcessed, @Nullable Boolean itemIsToBePaidSeparately, @Nullable String layoutSortingRule, @Nullable String paymentBlockingReason, @Nullable String paymentMethodsList, @Nullable String paymentTerms, @Nullable Boolean paytAdviceIsSentbyEDI, @Nullable Boolean physicalInventoryBlockInd, @Nullable String reconciliationAccount, @Nullable Boolean recordPaymentHistoryIndicator, @Nullable String userAtCustomer, @Nullable Boolean deletionIndicator, @Nullable String customerAccountGroup, List<CustomerDunning> toCustomerDunning, List<CustomerWithHoldingTax> toWithHoldingTax)
@Nonnull public Class<CustomerCompany> getType()
getType
in class VdmObject<CustomerCompany>
public void setCustomer(@Nullable String customer)
Original property name from the Odata EDM: Customer
customer
- Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.public void setCompanyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
companyCode
- The company code is an organizational unit within financial accounting.public void setAPARToleranceGroup(@Nullable String aPARToleranceGroup)
Original property name from the Odata EDM: APARToleranceGroup
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.public void setAccountByCustomer(@Nullable String accountByCustomer)
Original property name from the Odata EDM: AccountByCustomer
accountByCustomer
- This field contains the account number the company is listed under at the customer.public void setAccountingClerk(@Nullable String accountingClerk)
Original property name from the Odata EDM: AccountingClerk
The name of the accounting clerk defined by this identification code can be used in the payment program for correspondence and reporting (for example, open item lists).
accountingClerk
- Identification code for the accounting clerk.public void setAccountingClerkFaxNumber(@Nullable String accountingClerkFaxNumber)
Original property name from the Odata EDM: AccountingClerkFaxNumber
accountingClerkFaxNumber
- Accounting clerk's fax number at the customer/vendorpublic void setAccountingClerkInternetAddress(@Nullable String accountingClerkInternetAddress)
Original property name from the Odata EDM: AccountingClerkInternetAddress
accountingClerkInternetAddress
- Internet address of partner company clerkpublic void setAccountingClerkPhoneNumber(@Nullable String accountingClerkPhoneNumber)
Original property name from the Odata EDM: AccountingClerkPhoneNumber
accountingClerkPhoneNumber
- Accounting clerk's telephone number at business partnerpublic void setAlternativePayerAccount(@Nullable String alternativePayerAccount)
Original property name from the Odata EDM: AlternativePayerAccount
Account number of the customer for whom automatic payment transactions are to be carried out.The account number is only needed if bank collections are not to be made via the customer who owes the receivables. The same applies to refunds of payables.The specification in this field only applies to this company code. There is another field in which you can enter an alternative payee for all company codes. If both fields are filled, the specification for the company code has priority.
alternativePayerAccount
- Account number of an alternative payerpublic void setAuthorizationGroup(@Nullable String authorizationGroup)
Original property name from the Odata EDM: AuthorizationGroup
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.public void setCollectiveInvoiceVariant(@Nullable String collectiveInvoiceVariant)
Original property name from the Odata EDM: CollectiveInvoiceVariant
collectiveInvoiceVariant
- Indicator which specifies at what intervals the collective invoices are to be created for the
customer.public void setCustomerAccountNote(@Nullable String customerAccountNote)
Original property name from the Odata EDM: CustomerAccountNote
The memo serves only as information on special features of the customer/vendor.
customerAccountNote
- Internal memo of the accounting department.public void setCustomerHeadOffice(@Nullable String customerHeadOffice)
Original property name from the Odata EDM: CustomerHeadOffice
This account number is only specified for branch accounts. All postings for which the account number of the branch is specified, are automatically posted to the head office account. The account number of the branch affected is noted in the line items.No line items or balances are managed in the branch account.
customerHeadOffice
- This field contains the account number of the head office.public void setCustomerSupplierClearingIsUsed(@Nullable Boolean customerSupplierClearingIsUsed)
Original property name from the Odata EDM: CustomerSupplierClearingIsUsed
To use this function in automatic payment transactions, you have toenter the vendor account number in the customer master record,enter the customer account number in the vendor master record, andselect the "Clearing with customer" indicator in the vendor master record.If you set this indicator, the system will also include items of the vendor account in customer dunning.
customerSupplierClearingIsUsed
- Indicates that during automatic payment transactions clearing is made with the corresponding vendor
account, and that during manual clearing procedures, the items of that vendor account are also
selected.public void setHouseBank(@Nullable String houseBank)
Original property name from the Odata EDM: HouseBank
houseBank
- All bank data is determined using this key.public void setInterestCalculationCode(@Nullable String interestCalculationCode)
Original property name from the Odata EDM: InterestCalculationCode
interestCalculationCode
- Enter an interest calculation indicator here if the account is to be included in automatic interest
calculation.public void setInterestCalculationDate(@Nullable LocalDateTime interestCalculationDate)
Original property name from the Odata EDM: InterestCalculationDate
Generally, this date is automatically maintained by the program (batch input). A manual entry in this field should only be made if an error has occurred or when implementing the interest calculation.
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.public void setIntrstCalcFrequencyInMonths(@Nullable String intrstCalcFrequencyInMonths)
Original property name from the Odata EDM: IntrstCalcFrequencyInMonths
Date of last interest calculation: 3/31.+ 01 month interest calculation frequency= 4/30 upper limit for the current interest runThe calculation period specified as a report parameter determines whether an account is included in an interest run.The upper limit of the interest run is calculated as in the above example and compared with the upper limit of the calculation entered in the interest run (report parameter). If the calculated upper limit is after the calculation period, the account is not included in interest calculation.If you maintain the interest calculation frequency in the account master record, this entry is used to calculate the upper limit. If not, the interest calculation frequency entered for the interest indicator is used.
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.public void setIsToBeLocallyProcessed(@Nullable Boolean isToBeLocallyProcessed)
Original property name from the Odata EDM: IsToBeLocallyProcessed
Normally automatic payment transactions and dunning notices are created for the head office.NoteSelect this indicator only if this account is a head office account.
isToBeLocallyProcessed
- Indicates that payment transactions and dunning notices are created for the branch.public void setItemIsToBePaidSeparately(@Nullable Boolean itemIsToBePaidSeparately)
Original property name from the Odata EDM: ItemIsToBePaidSeparately
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.public void setLayoutSortingRule(@Nullable String layoutSortingRule)
Original property name from the Odata EDM: LayoutSortingRule
The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.For this purpose, the system requires rules that determine which information is to be taken from the document header or from the document line item and placed in the field. The rules can be stored in the master record of an account which enables you to determine the standard sort sequence on an account-specific basis.NoteField information from another document line item cannot be adopted into the field of a particular item.
layoutSortingRule
- Indicates the layout rule for the Allocation field in the document line item.public void setPaymentBlockingReason(@Nullable String paymentBlockingReason)
Original property name from the Odata EDM: PaymentBlockingReason
You can use the block key as described below.Automatic Payment TransactionsIn automatic payment transactions, the block takes effect when it is entered in the system as follows:In the master recordIn the documentIf you enter the block in the master record then all open items for this account are contained in the exception list.The following block keys have a special meaning in the master record:The block key * has the effect that all items of the account are skipped in automatic payment transactions.The block key + has the effect that all items are skipped in which a payment method was not entered explicitly.The block key A is always set automatically when a down payment is entered. Therefore, you must not delete the block key A or use it for other purposes.Whether a block key can be set or removed in payment proposal processing depends on the attribute Changeable in payment proposal of the block key.Manual PaymentsManual payments are only affected by a block key in the document if you set the attribute Blocked for manual payments in the block key.A block key that was set in the master record does not have any effect on manual payments. You can have the system issue a warning message in that case. To do so, you have to make system settings. Set up message 671 of work area F5 in message control accordingly.
paymentBlockingReason
- Block key (enqueue key) that is used to block an open item or an account to payment transactions.public void setPaymentMethodsList(@Nullable String paymentMethodsList)
Original property name from the Odata EDM: PaymentMethodsList
If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the item which are not listed in the master record.
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.public void setPaymentTerms(@Nullable String paymentTerms)
Original property name from the Odata EDM: PaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
paymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setPaytAdviceIsSentbyEDI(@Nullable Boolean paytAdviceIsSentbyEDI)
Original property name from the Odata EDM: PaytAdviceIsSentbyEDI
paytAdviceIsSentbyEDI
- This indicator specifies that the customer/vendor should be sent all payment advice information by
EDI.public void setPhysicalInventoryBlockInd(@Nullable Boolean physicalInventoryBlockInd)
Original property name from the Odata EDM: PhysicalInventoryBlockInd
If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.
physicalInventoryBlockInd
- Indicates that the account is blocked for posting in the specified company code.public void setReconciliationAccount(@Nullable String reconciliationAccount)
Original property name from the Odata EDM: ReconciliationAccount
For special postings (for example, down payment or bill of exchange), this account is replaced by another account (for example, 'down payments received' instead of 'receivables').The replacement takes place due to the special G/L indicator which you must specify for these types of postings.
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).public void setRecordPaymentHistoryIndicator(@Nullable Boolean recordPaymentHistoryIndicator)
Original property name from the Odata EDM: RecordPaymentHistoryIndicator
The amount and number of payments are then recorded per calendar month, as well as the average days in arrears.Information about cash discount payments and net payments is recorded separately.The indicator should not be set for one-time accounts and accounts which are paid automatically (bank collection or bank bill in Germany, bill of exchange payment request in France).You can only carry out evaluation of the payment history, for example, with the report for customer evaluation with OI listing, if you have selected this field.
recordPaymentHistoryIndicator
- Indicator that the payment history of the customer is to be recorded.public void setUserAtCustomer(@Nullable String userAtCustomer)
Original property name from the Odata EDM: UserAtCustomer
userAtCustomer
- Name or identification code of the accounting clerk at the customer.public void setDeletionIndicator(@Nullable Boolean deletionIndicator)
Original property name from the Odata EDM: DeletionIndicator
To delete this data, you have to run the archiving program for Accounts Receivable or Payable. This program will archive all master records marked for deletion provided that there is no dependent data in them.This deletion flag cannot be used in the program that deletes master data. You should, however, run this program only to delete test data prior to production startup.
deletionIndicator
- Indicates that the company code data in this master record is to be deleted.public void setCustomerAccountGroup(@Nullable String customerAccountGroup)
Original property name from the Odata EDM: CustomerAccountGroup
in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
customerAccountGroup
- The account group is a classifying feature within customer master records. The account group
determines:protected String getEntityCollection()
getEntityCollection
in class VdmEntity<CustomerCompany>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<CustomerCompany>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<CustomerCompany>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<CustomerCompany>
@Nonnull public static <T> CustomerCompanyField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.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.@Nonnull public static <T,DomainT> CustomerCompanyField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<CustomerCompany>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
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.
setServicePathForFetch
in class VdmEntity<CustomerCompany>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
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.
attachToService
in class VdmEntity<CustomerCompany>
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.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
getDefaultServicePath
in class VdmEntity<CustomerCompany>
@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<CustomerCompany>
@Nonnull public List<CustomerDunning> fetchCustomerDunning() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
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.@Nonnull public List<CustomerDunning> getCustomerDunningOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_CustomerDunning of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
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.@Nonnull public io.vavr.control.Option<List<CustomerDunning>> getCustomerDunningIfPresent()
If the navigation property for an entity CustomerCompany has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setCustomerDunning(@Nonnull List<CustomerDunning> value)
If the navigation property to_CustomerDunning of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of CustomerDunning entities.public void addCustomerDunning(CustomerDunning... entity)
If the navigation property to_CustomerDunning of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of CustomerDunning entities.@Nonnull public List<CustomerWithHoldingTax> fetchWithHoldingTax() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
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.@Nonnull public List<CustomerWithHoldingTax> getWithHoldingTaxOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_WithHoldingTax of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
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.@Nonnull public io.vavr.control.Option<List<CustomerWithHoldingTax>> getWithHoldingTaxIfPresent()
If the navigation property for an entity CustomerCompany has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setWithHoldingTax(@Nonnull List<CustomerWithHoldingTax> value)
If the navigation property to_WithHoldingTax of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of CustomerWithHoldingTax entities.public void addWithHoldingTax(CustomerWithHoldingTax... entity)
If the navigation property to_WithHoldingTax of a queried CustomerCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of CustomerWithHoldingTax entities.public static CustomerCompany.CustomerCompanyBuilder builder()
@Nullable public String getCustomer()
Original property name from the Odata EDM: Customer
@Nullable public String getCompanyCode()
Original property name from the Odata EDM: CompanyCode
@Nullable public String getAPARToleranceGroup()
Original property name from the Odata EDM: APARToleranceGroup
@Nullable public String getAccountByCustomer()
Original property name from the Odata EDM: AccountByCustomer
@Nullable public String getAccountingClerk()
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).
@Nullable public String getAccountingClerkFaxNumber()
Original property name from the Odata EDM: AccountingClerkFaxNumber
@Nullable public String getAccountingClerkInternetAddress()
Original property name from the Odata EDM: AccountingClerkInternetAddress
@Nullable public String getAccountingClerkPhoneNumber()
Original property name from the Odata EDM: AccountingClerkPhoneNumber
@Nullable public String getAlternativePayerAccount()
Original property name from the Odata EDM: AlternativePayerAccount
Account number of the customer for whom automatic payment transactions are to be carried out.The account number is only needed if bank collections are not to be made via the customer who owes the receivables. The same applies to refunds of payables.The specification in this field only applies to this company code. There is another field in which you can enter an alternative payee for all company codes. If both fields are filled, the specification for the company code has priority.
@Nullable public String getAuthorizationGroup()
Original property name from the Odata EDM: AuthorizationGroup
@Nullable public String getCollectiveInvoiceVariant()
Original property name from the Odata EDM: CollectiveInvoiceVariant
@Nullable public String getCustomerAccountNote()
Original property name from the Odata EDM: CustomerAccountNote
The memo serves only as information on special features of the customer/vendor.
@Nullable public String getCustomerHeadOffice()
Original property name from the Odata EDM: CustomerHeadOffice
This account number is only specified for branch accounts. All postings for which the account number of the branch is specified, are automatically posted to the head office account. The account number of the branch affected is noted in the line items.No line items or balances are managed in the branch account.
@Nullable public Boolean getCustomerSupplierClearingIsUsed()
Original property name from the Odata EDM: CustomerSupplierClearingIsUsed
To use this function in automatic payment transactions, you have toenter the vendor account number in the customer master record,enter the customer account number in the vendor master record, andselect the "Clearing with customer" indicator in the vendor master record.If you set this indicator, the system will also include items of the vendor account in customer dunning.
@Nullable public String getHouseBank()
Original property name from the Odata EDM: HouseBank
@Nullable public String getInterestCalculationCode()
Original property name from the Odata EDM: InterestCalculationCode
@Nullable public LocalDateTime getInterestCalculationDate()
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.
@Nullable public String getIntrstCalcFrequencyInMonths()
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.
@Nullable public Boolean getIsToBeLocallyProcessed()
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.
@Nullable public Boolean getItemIsToBePaidSeparately()
Original property name from the Odata EDM: ItemIsToBePaidSeparately
@Nullable public String getLayoutSortingRule()
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.
@Nullable public String getPaymentBlockingReason()
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.
@Nullable public String getPaymentMethodsList()
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.
@Nullable public String getPaymentTerms()
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.
@Nullable public Boolean getPaytAdviceIsSentbyEDI()
Original property name from the Odata EDM: PaytAdviceIsSentbyEDI
@Nullable public Boolean getPhysicalInventoryBlockInd()
Original property name from the Odata EDM: PhysicalInventoryBlockInd
If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.
@Nullable public String getReconciliationAccount()
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.
@Nullable public Boolean getRecordPaymentHistoryIndicator()
Original property name from the Odata EDM: RecordPaymentHistoryIndicator
The amount and number of payments are then recorded per calendar month, as well as the average days in arrears.Information about cash discount payments and net payments is recorded separately.The indicator should not be set for one-time accounts and accounts which are paid automatically (bank collection or bank bill in Germany, bill of exchange payment request in France).You can only carry out evaluation of the payment history, for example, with the report for customer evaluation with OI listing, if you have selected this field.
@Nullable public String getUserAtCustomer()
Original property name from the Odata EDM: UserAtCustomer
@Nullable public Boolean getDeletionIndicator()
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.
@Nullable public String getCustomerAccountGroup()
Original property name from the Odata EDM: CustomerAccountGroup
in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
public String toString()
toString
in class VdmObject<CustomerCompany>
public boolean equals(Object o)
equals
in class VdmObject<CustomerCompany>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<CustomerCompany>
public int hashCode()
hashCode
in class VdmObject<CustomerCompany>
Copyright © 2019 SAP SE. All rights reserved.