public class BusinessPartnerBank extends VdmEntity<BusinessPartnerBank>
Original entity name from the Odata EDM: A_BusinessPartnerBankType
Modifier and Type | Class and Description |
---|---|
static class |
BusinessPartnerBank.BusinessPartnerBankBuilder |
Modifier and Type | Field and Description |
---|---|
static BusinessPartnerBankSelectable |
ALL_FIELDS
Selector for all available fields of BusinessPartnerBank.
|
static BusinessPartnerBankField<String> |
AUTHORIZATION_GROUP
Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_ACCOUNT
Use with available fluent helpers to apply the BankAccount field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_ACCOUNT_HOLDER_NAME
Use with available fluent helpers to apply the BankAccountHolderName field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_ACCOUNT_NAME
Use with available fluent helpers to apply the BankAccountName field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_ACCOUNT_REFERENCE_TEXT
Use with available fluent helpers to apply the BankAccountReferenceText field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_CONTROL_KEY
Use with available fluent helpers to apply the BankControlKey field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_COUNTRY_KEY
Use with available fluent helpers to apply the BankCountryKey field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_IDENTIFICATION
Use with available fluent helpers to apply the BankIdentification field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_NAME
Use with available fluent helpers to apply the BankName field to query operations.
|
static BusinessPartnerBankField<String> |
BANK_NUMBER
Use with available fluent helpers to apply the BankNumber field to query operations.
|
static BusinessPartnerBankField<String> |
BUSINESS_PARTNER
Use with available fluent helpers to apply the BusinessPartner field to query operations.
|
static BusinessPartnerBankField<String> |
CITY_NAME
Use with available fluent helpers to apply the CityName field to query operations.
|
static BusinessPartnerBankField<Boolean> |
COLLECTION_AUTH_IND
Use with available fluent helpers to apply the CollectionAuthInd field to query operations.
|
static BusinessPartnerBankField<String> |
IBAN
Use with available fluent helpers to apply the IBAN field to query operations.
|
static BusinessPartnerBankField<LocalDateTime> |
IBAN_VALIDITY_START_DATE
Use with available fluent helpers to apply the IBANValidityStartDate field to query operations.
|
static BusinessPartnerBankField<String> |
SWIFT_CODE
Use with available fluent helpers to apply the SWIFTCode field to query operations.
|
static BusinessPartnerBankField<ZonedDateTime> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static BusinessPartnerBankField<ZonedDateTime> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
BusinessPartnerBank() |
BusinessPartnerBank(String businessPartner,
String bankIdentification,
String bankCountryKey,
String bankName,
String bankNumber,
String sWIFTCode,
String bankControlKey,
String bankAccountHolderName,
String bankAccountName,
ZonedDateTime validityStartDate,
ZonedDateTime validityEndDate,
String iBAN,
LocalDateTime iBANValidityStartDate,
String bankAccount,
String bankAccountReferenceText,
Boolean collectionAuthInd,
String cityName,
String authorizationGroup) |
Modifier and Type | Method and Description |
---|---|
void |
attachToService(String servicePath,
ErpConfigContext configContext)
Sets the service path and ERP configuration context for the fetch commands of this entity.
|
static BusinessPartnerBank.BusinessPartnerBankBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> BusinessPartnerBankField<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 |
getAuthorizationGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getBankAccount()
Constraints: Not nullable, Maximum length: 18
|
String |
getBankAccountHolderName()
Constraints: Not nullable, Maximum length: 60
|
String |
getBankAccountName()
Constraints: Not nullable, Maximum length: 40
|
String |
getBankAccountReferenceText()
Constraints: Not nullable, Maximum length: 20
|
String |
getBankControlKey()
Constraints: Not nullable, Maximum length: 2
|
String |
getBankCountryKey()
Constraints: Not nullable, Maximum length: 3
|
String |
getBankIdentification()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getBankName()
Constraints: Not nullable, Maximum length: 60
|
String |
getBankNumber()
Constraints: Not nullable, Maximum length: 15
|
String |
getBusinessPartner()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getCityName()
Constraints: Not nullable, Maximum length: 35
|
Boolean |
getCollectionAuthInd()
Constraints: none
|
protected String |
getDefaultServicePath() |
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getIBAN()
Constraints: Not nullable, Maximum length: 34
|
LocalDateTime |
getIBANValidityStartDate()
Constraints: Not nullable, Precision: 0
|
protected Map<String,Object> |
getKey() |
String |
getSWIFTCode()
Constraints: Not nullable, Maximum length: 11
|
Class<BusinessPartnerBank> |
getType() |
ZonedDateTime |
getValidityEndDate()
Constraints: Not nullable, Precision: 0
|
ZonedDateTime |
getValidityStartDate()
Constraints: Not nullable, Precision: 0
|
int |
hashCode() |
void |
setAuthorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setBankAccount(String bankAccount)
Constraints: Not nullable, Maximum length: 18
|
void |
setBankAccountHolderName(String bankAccountHolderName)
Constraints: Not nullable, Maximum length: 60
|
void |
setBankAccountName(String bankAccountName)
Constraints: Not nullable, Maximum length: 40
|
void |
setBankAccountReferenceText(String bankAccountReferenceText)
Constraints: Not nullable, Maximum length: 20
|
void |
setBankControlKey(String bankControlKey)
Constraints: Not nullable, Maximum length: 2
|
void |
setBankCountryKey(String bankCountryKey)
Constraints: Not nullable, Maximum length: 3
|
void |
setBankIdentification(String bankIdentification)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setBankName(String bankName)
Constraints: Not nullable, Maximum length: 60
|
void |
setBankNumber(String bankNumber)
Constraints: Not nullable, Maximum length: 15
|
void |
setBusinessPartner(String businessPartner)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setCityName(String cityName)
Constraints: Not nullable, Maximum length: 35
|
void |
setCollectionAuthInd(Boolean collectionAuthInd)
Constraints: none
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Deprecated.
Use
attachToService(String, ErpConfigContext) instead. |
void |
setIBAN(String iBAN)
Constraints: Not nullable, Maximum length: 34
|
void |
setIBANValidityStartDate(LocalDateTime iBANValidityStartDate)
Constraints: Not nullable, Precision: 0
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setSWIFTCode(String sWIFTCode)
Constraints: Not nullable, Maximum length: 11
|
void |
setValidityEndDate(ZonedDateTime validityEndDate)
Constraints: Not nullable, Precision: 0
|
void |
setValidityStartDate(ZonedDateTime validityStartDate)
Constraints: Not nullable, Precision: 0
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final BusinessPartnerBankSelectable ALL_FIELDS
public static final BusinessPartnerBankField<String> BUSINESS_PARTNER
public static final BusinessPartnerBankField<String> BANK_IDENTIFICATION
public static final BusinessPartnerBankField<String> BANK_COUNTRY_KEY
public static final BusinessPartnerBankField<String> BANK_NAME
public static final BusinessPartnerBankField<String> BANK_NUMBER
public static final BusinessPartnerBankField<String> SWIFT_CODE
public static final BusinessPartnerBankField<String> BANK_CONTROL_KEY
public static final BusinessPartnerBankField<String> BANK_ACCOUNT_HOLDER_NAME
public static final BusinessPartnerBankField<String> BANK_ACCOUNT_NAME
public static final BusinessPartnerBankField<ZonedDateTime> VALIDITY_START_DATE
public static final BusinessPartnerBankField<ZonedDateTime> VALIDITY_END_DATE
public static final BusinessPartnerBankField<String> IBAN
public static final BusinessPartnerBankField<LocalDateTime> IBAN_VALIDITY_START_DATE
public static final BusinessPartnerBankField<String> BANK_ACCOUNT
public static final BusinessPartnerBankField<String> BANK_ACCOUNT_REFERENCE_TEXT
public static final BusinessPartnerBankField<Boolean> COLLECTION_AUTH_IND
public static final BusinessPartnerBankField<String> CITY_NAME
public static final BusinessPartnerBankField<String> AUTHORIZATION_GROUP
public BusinessPartnerBank()
public BusinessPartnerBank(@Nullable String businessPartner, @Nullable String bankIdentification, @Nullable String bankCountryKey, @Nullable String bankName, @Nullable String bankNumber, @Nullable String sWIFTCode, @Nullable String bankControlKey, @Nullable String bankAccountHolderName, @Nullable String bankAccountName, @Nullable ZonedDateTime validityStartDate, @Nullable ZonedDateTime validityEndDate, @Nullable String iBAN, @Nullable LocalDateTime iBANValidityStartDate, @Nullable String bankAccount, @Nullable String bankAccountReferenceText, @Nullable Boolean collectionAuthInd, @Nullable String cityName, @Nullable String authorizationGroup)
@Nonnull public Class<BusinessPartnerBank> getType()
getType
in class VdmObject<BusinessPartnerBank>
public void setBusinessPartner(@Nullable String businessPartner)
Original property name from the Odata EDM: BusinessPartner
businessPartner
- Key identifying a business partner in the SAP system. The key is unique within a client.public void setBankIdentification(@Nullable String bankIdentification)
Original property name from the Odata EDM: BankIdentification
Enter a bank details ID for each separate set of bank details for a business partner.Business Partner: H. MillerBD-ID Fin.institution Acct no. 0001 Chemical Bank, NYC 56234560002 Chemical Bank, NYC 56231220003 First Bank of Pittsburgh ...Business partner: T.Wolsey and Co.BD-ID Fin.institution Acct no.GIR0 Citibank, Charleston ...GIR1 Chemical Bank, NYC ...
bankIdentification
- Key identifying a business partner's bank details.public void setBankCountryKey(@Nullable String bankCountryKey)
Original property name from the Odata EDM: BankCountryKey
The country key determines according to which rules the remaining bank data (for example, bank number and bank account number) is checked.
bankCountryKey
- Identifies the country in which the bank is based.public void setBankName(@Nullable String bankName)
Original property name from the Odata EDM: BankName
bankName
- The name under which the bank operates.public void setBankNumber(@Nullable String bankNumber)
Original property name from the Odata EDM: BankNumber
The country-specific meaning of this bank key is specified when defining country key.Normally banks have a bank number, which then also appears in the control data of the bank.In certain countries the bank account number assumes this function; in such a case there would be no bank numbers, the bank details are then under the account number.For data medium exchange it can be useful to be able create banks for foreign business partners without a bank number, even if the country in question has bank numbers. In such cases the bank key can be assigned internally.If the bank data is under another key, such as the SWIFT code for example, numbers can also be assigned externally.
bankNumber
- The bank key (under which the bank data is stored in the appropriate country) is specified in this
field.public void setSWIFTCode(@Nullable String sWIFTCode)
Original property name from the Odata EDM: SWIFTCode
SWIFT stands for Society for Worldwide Interbank Financial Telecommunication.BIC stands for Bank Identifier Code.This globally unique code can be used in international payment transactions to identify the bank without the need to specify an address or bank number. Specification of the SWIFT code/BIC is mainly relevant for automatic payment transactions.
sWIFTCode
- Uniquely identifies a bank throughout the world.public void setBankControlKey(@Nullable String bankControlKey)
Original property name from the Odata EDM: BankControlKey
The field contains a check key for the combination bank number and bank account number.USAIn USA this field is used to differentiate between a savings and a current account (if no value is entered, the default value 01 is used).01 Current account02 Savings account03 Loan account04 General ledgerJapanIn Japan this field specifies the type of account. This information is is copied from the payment medium print program into payment medium. The following is an example of the account types used:01 FUTSU (similar to a savings account)02 TOUZA (similar to a current account)04 CHOCHIKU (similar to an investment account)09 Other types of bank accountsSouth AfricaIn South Africa this field specifies the type of account. The information entered here is forwarded to the bank that carries out the payment order. The following account types are permitted in ABC format:01 Current (Cheque) Account02 Savings Account03 Transmission Account04 Bond Account06 Subscription Share AccountArgentinaIn Argentina this field specifies the type of account:CC Current Account (Cuenta corriente)CA Saving Account (Caja de ahorro)CE Special Saving Account (Caja de ahorro especial)CS Salary Account (Cuenta sueldos)VenezuelaIn Venezuela this field specifies the type of account:CC Checking Account (Cuenta corriente)CA Saving Account (Cuenta de ahorro)CE Special Saving Account (Cuenta de ahorro especial)CS Salary Account (Cuenta sueldos)MexicoIn Mexico this field contains a two-digit key for classifying the bank account (for example, as a savings or current account). This key have different definitions, depending on the bank.NoteFor countries that are not listed here, this field can be used for account-specific information.
bankControlKey
- Brazil, France, Spain, Portugal and Italypublic void setBankAccountHolderName(@Nullable String bankAccountHolderName)
Original property name from the Odata EDM: BankAccountHolderName
bankAccountHolderName
- Here you can enter another name that the payment program can use if the name of the account holder is
not the same as the name of the Business Partner.public void setBankAccountName(@Nullable String bankAccountName)
Original property name from the Odata EDM: BankAccountName
bankAccountName
- Name of Bank Accountpublic void setValidityStartDate(@Nullable ZonedDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
validityStartDate
- Validity Start of Business Partner Bank Detailspublic void setValidityEndDate(@Nullable ZonedDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
validityEndDate
- Validity End of Business Partner Bank Detailspublic void setIBAN(@Nullable String iBAN)
Original property name from the Odata EDM: IBAN
Country key of the bank (ISO code)Two-digit check numberCountry-specific account number (in Germany this consists of the bank number and account number, in France the bank number, account number and check key).The IBAN not only makes international payments easier, in some countries it has advantages for domestic payments as well. Depending on the country, it can mean advantages for value and fees.The IBAN can be maintained in parallel with the bank details but does not replace them. It is stored under the master data of the business partner and can then be used when creating the payment medium.Since it is only the bank that has the account that may generate the IBAN corresponding to an account number, the SAP system only generates a proposal. You can confirm or change this proposal. If no proposal is generated, enter the IBAN manually.An IBAN in Belgium may look like this:Electronic Form:BE62510007547061Printed form, as it would appear on an invoice:IBAN BE62 5100 0754 7061
iBAN
- A uniform standardized ID number for representing bank details that is in accordance with the ECBS
(European Committee for Banking Standards). An IBAN has a maximum of 34 alphanumeric characters and is
a combination of the following elements:public void setIBANValidityStartDate(@Nullable LocalDateTime iBANValidityStartDate)
Original property name from the Odata EDM: IBANValidityStartDate
iBANValidityStartDate
- Validity start of IBANpublic void setBankAccount(@Nullable String bankAccount)
Original property name from the Odata EDM: BankAccount
bankAccount
- This field contains the number under which the account is managed at the bank.public void setBankAccountReferenceText(@Nullable String bankAccountReferenceText)
Original property name from the Odata EDM: BankAccountReferenceText
In some countries the data for the bank details of the business partner (bank number, bank account number, name of the account holder) have to supplemented by other details in order to be able to use certain payment processes. This supplementary details are defined here.If additional data is required for the bank details for payment transactions in your country (see the following examples), enter the reference information.If for an automatic debit the bank requires the reference number of the collection authorization in Norway or Great Britain, specify this number here.In Great Britain when making payments to an account in a 'Building Society' you must specify which number payment recipient has. These details must be defined in the reference field, whereas the fields Bank Key and Account Number are to be used for the bank details of the 'Building Society'.In Great Britain when entering a building society account number, the name of the building society should also be maintained in the system.
bankAccountReferenceText
- Additional details for the bank details of the business partner.public void setCollectionAuthInd(@Nullable Boolean collectionAuthInd)
Original property name from the Odata EDM: CollectionAuthInd
Set this indicator if the bank has collection authorization.Note for Accounts Receivable (FI-AR)If this indicator is not set, there is no bank collection.Note for Contract Accounts Receivable and Payable (FI-CA)This indicator is not relevant.
collectionAuthInd
- States that the bank has collection authorization from the business partner for the account.public void setCityName(@Nullable String cityName)
Original property name from the Odata EDM: CityName
cityName
- Name of the city as a part of the address.public void setAuthorizationGroup(@Nullable String authorizationGroup)
Original property name from the Odata EDM: AuthorizationGroup
Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.
authorizationGroup
- You can use authorization groups to stipulate which business partners a user is allowed to process.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<BusinessPartnerBank>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<BusinessPartnerBank>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<BusinessPartnerBank>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<BusinessPartnerBank>
@Nonnull public static <T> BusinessPartnerBankField<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> BusinessPartnerBankField<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 ErpConfigContext getErpConfigContext()
VdmEntity
getErpConfigContext
in class VdmEntity<BusinessPartnerBank>
@Deprecated public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
attachToService(String, ErpConfigContext)
instead.VdmEntity
setErpConfigContext
in class VdmEntity<BusinessPartnerBank>
erpConfigContext
- New ERP configuration context to apply to this entityprotected 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<BusinessPartnerBank>
public void attachToService(@Nullable String servicePath, @Nullable ErpConfigContext configContext)
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<BusinessPartnerBank>
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
.protected String getDefaultServicePath()
getDefaultServicePath
in class VdmEntity<BusinessPartnerBank>
public static BusinessPartnerBank.BusinessPartnerBankBuilder builder()
@Nullable public String getBusinessPartner()
Original property name from the Odata EDM: BusinessPartner
@Nullable public String getBankIdentification()
Original property name from the Odata EDM: BankIdentification
Enter a bank details ID for each separate set of bank details for a business partner.Business Partner: H. MillerBD-ID Fin.institution Acct no. 0001 Chemical Bank, NYC 56234560002 Chemical Bank, NYC 56231220003 First Bank of Pittsburgh ...Business partner: T.Wolsey and Co.BD-ID Fin.institution Acct no.GIR0 Citibank, Charleston ...GIR1 Chemical Bank, NYC ...
@Nullable public String getBankCountryKey()
Original property name from the Odata EDM: BankCountryKey
The country key determines according to which rules the remaining bank data (for example, bank number and bank account number) is checked.
@Nullable public String getBankName()
Original property name from the Odata EDM: BankName
@Nullable public String getBankNumber()
Original property name from the Odata EDM: BankNumber
The country-specific meaning of this bank key is specified when defining country key.Normally banks have a bank number, which then also appears in the control data of the bank.In certain countries the bank account number assumes this function; in such a case there would be no bank numbers, the bank details are then under the account number.For data medium exchange it can be useful to be able create banks for foreign business partners without a bank number, even if the country in question has bank numbers. In such cases the bank key can be assigned internally.If the bank data is under another key, such as the SWIFT code for example, numbers can also be assigned externally.
@Nullable public String getSWIFTCode()
Original property name from the Odata EDM: SWIFTCode
SWIFT stands for Society for Worldwide Interbank Financial Telecommunication.BIC stands for Bank Identifier Code.This globally unique code can be used in international payment transactions to identify the bank without the need to specify an address or bank number. Specification of the SWIFT code/BIC is mainly relevant for automatic payment transactions.
@Nullable public String getBankControlKey()
Original property name from the Odata EDM: BankControlKey
The field contains a check key for the combination bank number and bank account number.USAIn USA this field is used to differentiate between a savings and a current account (if no value is entered, the default value 01 is used).01 Current account02 Savings account03 Loan account04 General ledgerJapanIn Japan this field specifies the type of account. This information is is copied from the payment medium print program into payment medium. The following is an example of the account types used:01 FUTSU (similar to a savings account)02 TOUZA (similar to a current account)04 CHOCHIKU (similar to an investment account)09 Other types of bank accountsSouth AfricaIn South Africa this field specifies the type of account. The information entered here is forwarded to the bank that carries out the payment order. The following account types are permitted in ABC format:01 Current (Cheque) Account02 Savings Account03 Transmission Account04 Bond Account06 Subscription Share AccountArgentinaIn Argentina this field specifies the type of account:CC Current Account (Cuenta corriente)CA Saving Account (Caja de ahorro)CE Special Saving Account (Caja de ahorro especial)CS Salary Account (Cuenta sueldos)VenezuelaIn Venezuela this field specifies the type of account:CC Checking Account (Cuenta corriente)CA Saving Account (Cuenta de ahorro)CE Special Saving Account (Cuenta de ahorro especial)CS Salary Account (Cuenta sueldos)MexicoIn Mexico this field contains a two-digit key for classifying the bank account (for example, as a savings or current account). This key have different definitions, depending on the bank.NoteFor countries that are not listed here, this field can be used for account-specific information.
@Nullable public String getBankAccountHolderName()
Original property name from the Odata EDM: BankAccountHolderName
@Nullable public String getBankAccountName()
Original property name from the Odata EDM: BankAccountName
@Nullable public ZonedDateTime getValidityStartDate()
Original property name from the Odata EDM: ValidityStartDate
@Nullable public ZonedDateTime getValidityEndDate()
Original property name from the Odata EDM: ValidityEndDate
@Nullable public String getIBAN()
Original property name from the Odata EDM: IBAN
Country key of the bank (ISO code)Two-digit check numberCountry-specific account number (in Germany this consists of the bank number and account number, in France the bank number, account number and check key).The IBAN not only makes international payments easier, in some countries it has advantages for domestic payments as well. Depending on the country, it can mean advantages for value and fees.The IBAN can be maintained in parallel with the bank details but does not replace them. It is stored under the master data of the business partner and can then be used when creating the payment medium.Since it is only the bank that has the account that may generate the IBAN corresponding to an account number, the SAP system only generates a proposal. You can confirm or change this proposal. If no proposal is generated, enter the IBAN manually.An IBAN in Belgium may look like this:Electronic Form:BE62510007547061Printed form, as it would appear on an invoice:IBAN BE62 5100 0754 7061
@Nullable public LocalDateTime getIBANValidityStartDate()
Original property name from the Odata EDM: IBANValidityStartDate
@Nullable public String getBankAccount()
Original property name from the Odata EDM: BankAccount
@Nullable public String getBankAccountReferenceText()
Original property name from the Odata EDM: BankAccountReferenceText
In some countries the data for the bank details of the business partner (bank number, bank account number, name of the account holder) have to supplemented by other details in order to be able to use certain payment processes. This supplementary details are defined here.If additional data is required for the bank details for payment transactions in your country (see the following examples), enter the reference information.If for an automatic debit the bank requires the reference number of the collection authorization in Norway or Great Britain, specify this number here.In Great Britain when making payments to an account in a 'Building Society' you must specify which number payment recipient has. These details must be defined in the reference field, whereas the fields Bank Key and Account Number are to be used for the bank details of the 'Building Society'.In Great Britain when entering a building society account number, the name of the building society should also be maintained in the system.
@Nullable public Boolean getCollectionAuthInd()
Original property name from the Odata EDM: CollectionAuthInd
Set this indicator if the bank has collection authorization.Note for Accounts Receivable (FI-AR)If this indicator is not set, there is no bank collection.Note for Contract Accounts Receivable and Payable (FI-CA)This indicator is not relevant.
@Nullable public String getCityName()
Original property name from the Odata EDM: CityName
@Nullable public String getAuthorizationGroup()
Original property name from the Odata EDM: AuthorizationGroup
Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.
public String toString()
toString
in class VdmObject<BusinessPartnerBank>
public boolean equals(Object o)
equals
in class VdmObject<BusinessPartnerBank>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<BusinessPartnerBank>
public int hashCode()
hashCode
in class VdmObject<BusinessPartnerBank>
Copyright © 2019 SAP SE. All rights reserved.