public class BusinessPartnerBank extends Entity<BusinessPartnerBank>
| Modifier and Type | Class and Description |
|---|---|
static class |
BusinessPartnerBank.BusinessPartnerBankBuilder |
| Modifier and Type | Field and Description |
|---|---|
static EntityField<BusinessPartnerBank,String> |
AUTHORIZATION_GROUP
Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_ACCOUNT
Use with available fluent helpers to apply the BankAccount field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_ACCOUNT_HOLDER_NAME
Use with available fluent helpers to apply the BankAccountHolderName field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_ACCOUNT_NAME
Use with available fluent helpers to apply the BankAccountName field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_ACCOUNT_REFERENCE_TEXT
Use with available fluent helpers to apply the BankAccountReferenceText field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_CONTROL_KEY
Use with available fluent helpers to apply the BankControlKey field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_COUNTRY_KEY
Use with available fluent helpers to apply the BankCountryKey field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_IDENTIFICATION
Use with available fluent helpers to apply the BankIdentification field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_NAME
Use with available fluent helpers to apply the BankName field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BANK_NUMBER
Use with available fluent helpers to apply the BankNumber field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
BUSINESS_PARTNER
Use with available fluent helpers to apply the BusinessPartner field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
CITY_NAME
Use with available fluent helpers to apply the CityName field to query operations.
|
static EntityField<BusinessPartnerBank,Boolean> |
COLLECTION_AUTH_IND
Use with available fluent helpers to apply the CollectionAuthInd field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
I_B_A_N
Use with available fluent helpers to apply the IBAN field to query operations.
|
static EntityField<BusinessPartnerBank,Calendar> |
I_B_A_N_VALIDITY_START_DATE
Use with available fluent helpers to apply the IBANValidityStartDate field to query operations.
|
static EntityField<BusinessPartnerBank,String> |
S_W_I_F_T_CODE
Use with available fluent helpers to apply the SWIFTCode field to query operations.
|
static EntityField<BusinessPartnerBank,Calendar> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static EntityField<BusinessPartnerBank,Calendar> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
| Constructor and Description |
|---|
BusinessPartnerBank() |
BusinessPartnerBank(String businessPartner,
String bankIdentification,
String bankCountryKey,
String bankName,
String bankNumber,
String sWIFTCode,
String bankControlKey,
String bankAccountHolderName,
String bankAccountName,
Calendar validityStartDate,
Calendar validityEndDate,
String iBAN,
Calendar iBANValidityStartDate,
String bankAccount,
String bankAccountReferenceText,
Boolean collectionAuthInd,
String cityName,
String authorizationGroup,
ErpConfigContext erpConfigContext) |
| Modifier and Type | Method and Description |
|---|---|
static BusinessPartnerBank.BusinessPartnerBankBuilder |
builder() |
boolean |
equals(Object o) |
static <T> EntityField<BusinessPartnerBank,T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
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
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getIBAN()
Constraints: Not nullable, Maximum length: 34
|
Calendar |
getIBANValidityStartDate()
Constraints: Not nullable, Precision: 0
|
String |
getSWIFTCode()
Constraints: Not nullable, Maximum length: 11
|
Class<BusinessPartnerBank> |
getType() |
Calendar |
getValidityEndDate()
Constraints: Not nullable, Precision: 0
|
Calendar |
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)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setIBAN(String iBAN)
Constraints: Not nullable, Maximum length: 34
|
void |
setIBANValidityStartDate(Calendar iBANValidityStartDate)
Constraints: Not nullable, Precision: 0
|
void |
setSWIFTCode(String sWIFTCode)
Constraints: Not nullable, Maximum length: 11
|
void |
setValidityEndDate(Calendar validityEndDate)
Constraints: Not nullable, Precision: 0
|
void |
setValidityStartDate(Calendar validityStartDate)
Constraints: Not nullable, Precision: 0
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomFieldpublic static final EntityField<BusinessPartnerBank,String> BUSINESS_PARTNER
public static final EntityField<BusinessPartnerBank,String> BANK_IDENTIFICATION
public static final EntityField<BusinessPartnerBank,String> BANK_COUNTRY_KEY
public static final EntityField<BusinessPartnerBank,String> BANK_NAME
public static final EntityField<BusinessPartnerBank,String> BANK_NUMBER
public static final EntityField<BusinessPartnerBank,String> S_W_I_F_T_CODE
public static final EntityField<BusinessPartnerBank,String> BANK_CONTROL_KEY
public static final EntityField<BusinessPartnerBank,String> BANK_ACCOUNT_HOLDER_NAME
public static final EntityField<BusinessPartnerBank,String> BANK_ACCOUNT_NAME
public static final EntityField<BusinessPartnerBank,Calendar> VALIDITY_START_DATE
public static final EntityField<BusinessPartnerBank,Calendar> VALIDITY_END_DATE
public static final EntityField<BusinessPartnerBank,String> I_B_A_N
public static final EntityField<BusinessPartnerBank,Calendar> I_B_A_N_VALIDITY_START_DATE
public static final EntityField<BusinessPartnerBank,String> BANK_ACCOUNT
public static final EntityField<BusinessPartnerBank,String> BANK_ACCOUNT_REFERENCE_TEXT
public static final EntityField<BusinessPartnerBank,Boolean> COLLECTION_AUTH_IND
public static final EntityField<BusinessPartnerBank,String> CITY_NAME
public static final EntityField<BusinessPartnerBank,String> AUTHORIZATION_GROUP
@Generated(value="lombok") public BusinessPartnerBank()
@ConstructorProperties(value={"businessPartner","bankIdentification","bankCountryKey","bankName","bankNumber","sWIFTCode","bankControlKey","bankAccountHolderName","bankAccountName","validityStartDate","validityEndDate","iBAN","iBANValidityStartDate","bankAccount","bankAccountReferenceText","collectionAuthInd","cityName","authorizationGroup","erpConfigContext"}) @Generated(value="lombok") 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 Calendar validityStartDate, @Nullable Calendar validityEndDate, @Nullable String iBAN, @Nullable Calendar iBANValidityStartDate, @Nullable String bankAccount, @Nullable String bankAccountReferenceText, @Nullable Boolean collectionAuthInd, @Nullable String cityName, @Nullable String authorizationGroup, @Nullable ErpConfigContext erpConfigContext)
public Class<BusinessPartnerBank> getType()
getType in class Entity<BusinessPartnerBank>public static <T> EntityField<BusinessPartnerBank,T> field(String fieldName, Class<T> fieldType)
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.@Generated(value="lombok") public static BusinessPartnerBank.BusinessPartnerBankBuilder builder()
@Nullable @Generated(value="lombok") public String getBusinessPartner()
@Nullable @Generated(value="lombok") public String getBankIdentification()
Enter a bank details ID for each separate set of bank details for a business partner. Business Partner: H. Miller BD-ID Fin.institution Acct no. 0001 Chemical Bank, NYC 5623456 0002 Chemical Bank, NYC 5623122 0003 First Bank of Pittsburgh ... Business partner: T.Wolsey and Co. BD-ID Fin.institution Acct no. GIR0 Citibank, Charleston ... GIR1 Chemical Bank, NYC ...
@Nullable @Generated(value="lombok") public String getBankCountryKey()
The country key determines according to which rules the remaining bank data (for example, bank number and bank account number) is checked.
@Nullable @Generated(value="lombok") public String getBankName()
@Nullable @Generated(value="lombok") public String getBankNumber()
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 @Generated(value="lombok") public String getSWIFTCode()
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 @Generated(value="lombok") public String getBankControlKey()
The field contains a check key for the combination bank number and bank account number. USA In 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 account 02 Savings account 03 Loan account 04 General ledger Japan In 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 accounts South Africa In 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) Account 02 Savings Account 03 Transmission Account 04 Bond Account 06 Subscription Share Account Argentina In 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) Venezuela In 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) Mexico In 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. Note For countries that are not listed here, this field can be used for account-specific information.
@Nullable @Generated(value="lombok") public String getBankAccountHolderName()
@Nullable @Generated(value="lombok") public String getBankAccountName()
@Nullable @Generated(value="lombok") public Calendar getValidityStartDate()
@Nullable @Generated(value="lombok") public Calendar getValidityEndDate()
@Nullable @Generated(value="lombok") public String getIBAN()
Commitee for Banking Standards) to represent bank details. AN IBAN contains a maximum of 34 alphanumerical symbols and is made up a combination of hte following elements: The bank's country key (ISO code) A two-figure check digit Country-specific account number (in Germany, for example, this consists of the bank number and the account number, while in France it consists of the bank number, the account number and the bank control key). The IBAN simplifies international payments and also provides benefits for domestic payments in some countries. In some countries, it also provides advantages with respect to value dates and fees. The IBAN can be stored in parallel with the bank details, but does not replace them. It is stored under the business partner's master data, and can be used when settings up the payment medium. As only the bank managing the account can generate the IBAN, which corresponds to one account number, the SAP system creates a proposal only. You can either confirm or change this. If the system was not able to create a proposal, enter the IBAN yourself. In Belgium, an IBAN might look like this: Electronic form: BE62510007547061 Printed form, as it appears on the invoice: IBAN BE62 5100 0754 7061
@Nullable @Generated(value="lombok") public Calendar getIBANValidityStartDate()
@Nullable @Generated(value="lombok") public String getBankAccount()
@Nullable @Generated(value="lombok") public String getBankAccountReferenceText()
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 @Generated(value="lombok") public Boolean getCollectionAuthInd()
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 @Generated(value="lombok") public String getCityName()
@Nullable @Generated(value="lombok") public String getAuthorizationGroup()
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.
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setBusinessPartner(@Nullable String businessPartner)
businessPartner - @Generated(value="lombok") public void setBankIdentification(@Nullable String bankIdentification)
Enter a bank details ID for each separate set of bank details for a business partner. Business Partner: H. Miller BD-ID Fin.institution Acct no. 0001 Chemical Bank, NYC 5623456 0002 Chemical Bank, NYC 5623122 0003 First Bank of Pittsburgh ... Business partner: T.Wolsey and Co. BD-ID Fin.institution Acct no. GIR0 Citibank, Charleston ... GIR1 Chemical Bank, NYC ...
bankIdentification - @Generated(value="lombok") public void setBankCountryKey(@Nullable String bankCountryKey)
The country key determines according to which rules the remaining bank data (for example, bank number and bank account number) is checked.
bankCountryKey - @Generated(value="lombok") public void setBankName(@Nullable String bankName)
bankName - @Generated(value="lombok") public void setBankNumber(@Nullable String 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 - @Generated(value="lombok") public void setSWIFTCode(@Nullable String 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 - @Generated(value="lombok") public void setBankControlKey(@Nullable String bankControlKey)
The field contains a check key for the combination bank number and bank account number. USA In 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 account 02 Savings account 03 Loan account 04 General ledger Japan In 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 accounts South Africa In 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) Account 02 Savings Account 03 Transmission Account 04 Bond Account 06 Subscription Share Account Argentina In 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) Venezuela In 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) Mexico In 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. Note For countries that are not listed here, this field can be used for account-specific information.
bankControlKey - @Generated(value="lombok") public void setBankAccountHolderName(@Nullable String bankAccountHolderName)
bankAccountHolderName - @Generated(value="lombok") public void setBankAccountName(@Nullable String bankAccountName)
bankAccountName - @Generated(value="lombok") public void setValidityStartDate(@Nullable Calendar validityStartDate)
validityStartDate - @Generated(value="lombok") public void setValidityEndDate(@Nullable Calendar validityEndDate)
validityEndDate - @Generated(value="lombok") public void setIBAN(@Nullable String iBAN)
Commitee for Banking Standards) to represent bank details. AN IBAN contains a maximum of 34 alphanumerical symbols and is made up a combination of hte following elements: The bank's country key (ISO code) A two-figure check digit Country-specific account number (in Germany, for example, this consists of the bank number and the account number, while in France it consists of the bank number, the account number and the bank control key). The IBAN simplifies international payments and also provides benefits for domestic payments in some countries. In some countries, it also provides advantages with respect to value dates and fees. The IBAN can be stored in parallel with the bank details, but does not replace them. It is stored under the business partner's master data, and can be used when settings up the payment medium. As only the bank managing the account can generate the IBAN, which corresponds to one account number, the SAP system creates a proposal only. You can either confirm or change this. If the system was not able to create a proposal, enter the IBAN yourself. In Belgium, an IBAN might look like this: Electronic form: BE62510007547061 Printed form, as it appears on the invoice: IBAN BE62 5100 0754 7061
iBAN - @Generated(value="lombok") public void setIBANValidityStartDate(@Nullable Calendar iBANValidityStartDate)
iBANValidityStartDate - @Generated(value="lombok") public void setBankAccount(@Nullable String bankAccount)
bankAccount - @Generated(value="lombok") public void setBankAccountReferenceText(@Nullable String 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 - @Generated(value="lombok") public void setCollectionAuthInd(@Nullable Boolean 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 - @Generated(value="lombok") public void setCityName(@Nullable String cityName)
cityName - @Generated(value="lombok") public void setAuthorizationGroup(@Nullable String 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 - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class Entity<BusinessPartnerBank>@Generated(value="lombok") public boolean equals(Object o)
equals in class Entity<BusinessPartnerBank>@Generated(value="lombok") public int hashCode()
hashCode in class Entity<BusinessPartnerBank>Copyright © 2017 SAP SE. All rights reserved.