SEPAMandate.SEPAMandateBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.contractaccountingsepamandate.SEPAMandate.SEPAMandateBuilder

Enclosing class:

SEPAMandate
```
public static final class SEPAMandate.SEPAMandateBuilder
extends Object
```
Helper class to allow for fluent creation of SEPAMandate instances.

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`SEPAMandate.SEPAMandateBuilder`	`alternativePayee(String alternativePayee)` Constraints: Not nullable, Maximum length: 70
`SEPAMandate.SEPAMandateBuilder`	`alternativePayeeName(String alternativePayeeName)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`alternativePayer(String alternativePayer)` Constraints: Not nullable, Maximum length: 70
`SEPAMandate.SEPAMandateBuilder`	`alternativePayerName(String alternativePayerName)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate`	`build()`
`SEPAMandate.SEPAMandateBuilder`	`createdByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`SEPAMandate.SEPAMandateBuilder`	`creationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 7
`SEPAMandate.SEPAMandateBuilder`	`creationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`SEPAMandate.SEPAMandateBuilder`	`creditor(String creditor)` (Key Field) Constraints: Not nullable, Maximum length: 35
`SEPAMandate.SEPAMandateBuilder`	`originalSEPAMandate(String originalSEPAMandate)` Constraints: Not nullable, Maximum length: 35
`SEPAMandate.SEPAMandateBuilder`	`recipient(String recipient)` Constraints: Not nullable, Maximum length: 70
`SEPAMandate.SEPAMandateBuilder`	`recipientCityName(String recipientCityName)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`recipientCountry(String recipientCountry)` Constraints: Not nullable, Maximum length: 3
`SEPAMandate.SEPAMandateBuilder`	`recipientHouseNumber(String recipientHouseNumber)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`recipientName1(String recipientName1)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`recipientName2(String recipientName2)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`recipientPostalCode(String recipientPostalCode)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`recipientStreetName(String recipientStreetName)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`recipientType(String recipientType)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`sender(String sender)` Constraints: Not nullable, Maximum length: 70
`SEPAMandate.SEPAMandateBuilder`	`senderBankSWIFTCode(String senderBankSWIFTCode)` Constraints: Not nullable, Maximum length: 11
`SEPAMandate.SEPAMandateBuilder`	`senderCityName(String senderCityName)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`senderCountry(String senderCountry)` Constraints: Not nullable, Maximum length: 3
`SEPAMandate.SEPAMandateBuilder`	`senderExternalID(String senderExternalID)` Constraints: Not nullable, Maximum length: 35
`SEPAMandate.SEPAMandateBuilder`	`senderFirstName(String senderFirstName)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`senderHouseNumber(String senderHouseNumber)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`senderIBAN(String senderIBAN)` Constraints: Not nullable, Maximum length: 34
`SEPAMandate.SEPAMandateBuilder`	`senderLanguage(String senderLanguage)` Constraints: Not nullable, Maximum length: 2
`SEPAMandate.SEPAMandateBuilder`	`senderLastName(String senderLastName)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`senderPostalCode(String senderPostalCode)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`senderStreetName(String senderStreetName)` Constraints: Not nullable, Maximum length: 60
`SEPAMandate.SEPAMandateBuilder`	`senderType(String senderType)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`sepaCreditorIdOrigin(String sepaCreditorIdOrigin)` Constraints: Not nullable, Maximum length: 35
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandate(String sEPAMandate)` (Key Field) Constraints: Not nullable, Maximum length: 35
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateApplication(String sEPAMandateApplication)` Constraints: Not nullable, Maximum length: 1
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateFirstUseDate(LocalDateTime sEPAMandateFirstUseDate)` Constraints: Not nullable, Precision: 7
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateFirstUseObjTypeCode(String sEPAMandateFirstUseObjTypeCode)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateFirstUsePaymentDoc(String sEPAMandateFirstUsePaymentDoc)` Constraints: Not nullable, Maximum length: 70
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateIsB2BMandate(Boolean sEPAMandateIsB2BMandate)` Constraints: Not nullable
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateLastUseDate(LocalDateTime sEPAMandateLastUseDate)` Constraints: Not nullable, Precision: 7
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateLastUseObjTypeCode(String sEPAMandateLastUseObjTypeCode)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateLastUsePaymentDoc(String sEPAMandateLastUsePaymentDoc)` Constraints: Not nullable, Maximum length: 70
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateOrganizationalUnit1(String sEPAMandateOrganizationalUnit1)` Constraints: Not nullable, Maximum length: 20
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateOrganizationalUnit2(String sEPAMandateOrganizationalUnit2)` Constraints: Not nullable, Maximum length: 20
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateOrganizationalUnit3(String sEPAMandateOrganizationalUnit3)` Constraints: Not nullable, Maximum length: 35
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateOrganizationalUnit4(String sEPAMandateOrganizationalUnit4)` Constraints: Not nullable, Maximum length: 35
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateReference(String sEPAMandateReference)` Constraints: Not nullable, Maximum length: 70
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateReferenceDesc(String sEPAMandateReferenceDesc)` Constraints: Not nullable, Maximum length: 50
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateReferenceType(String sEPAMandateReferenceType)` Constraints: Not nullable, Maximum length: 10
`SEPAMandate.SEPAMandateBuilder`	`sEPAMandateStatus(String sEPAMandateStatus)` Constraints: Not nullable, Maximum length: 1
`SEPAMandate.SEPAMandateBuilder`	`sepaMandateUsage(SEPAMandateUsage... value)` Navigation property SEPAMandateUsage for SEPAMandate to multiple SEPAMandateUsage.
`SEPAMandate.SEPAMandateBuilder`	`sEPAPaymentType(String sEPAPaymentType)` Constraints: Not nullable, Maximum length: 1
`SEPAMandate.SEPAMandateBuilder`	`sEPASignatureCityName(String sEPASignatureCityName)` Constraints: Not nullable, Maximum length: 40
`SEPAMandate.SEPAMandateBuilder`	`sEPASignatureDate(LocalDateTime sEPASignatureDate)` Constraints: Not nullable, Precision: 7
`String`	`toString()`
`SEPAMandate.SEPAMandateBuilder`	`validityEndDate(LocalDateTime validityEndDate)` Constraints: Not nullable, Precision: 7
`SEPAMandate.SEPAMandateBuilder`	`validityStartDate(LocalDateTime validityStartDate)` Constraints: Not nullable, Precision: 7
`SEPAMandate.SEPAMandateBuilder`	`version(String version)` Constraints: Not nullable, Maximum length: 4

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

- Method Detail
  - sepaMandateUsage
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sepaMandateUsage(SEPAMandateUsage... value)
```
    Navigation property SEPAMandateUsage for SEPAMandate to multiple SEPAMandateUsage.
    
    Parameters:
    
    value - The SEPAMandateUsages to build this SEPAMandate with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - sEPAMandateApplication
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateApplication(@Nullable
                                                                      String sEPAMandateApplication)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SEPAMandateApplication
    
    You can create SEPA mandates for various applications, such as business partners in contract accounts receivable and payable (FI-CA) or for customers in accounts receivable (FI-AR).The applications can:retain various data in the mandatescarry out various additional checksuse differing descriptions on the interfacesMandates can be identified by the application, mandate ID and creditor ID.An application that is used for the active creation of debit memos requires all of the data of a mandate document, and adjusts all of the checks made to it.An application that checks inbound debit memos for the existence of a mandate requires only a little data for the mandate, and adjusts all of the checks made to it.
    being used in.
    
    Returns:
    
    this.
  - creditor
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder creditor(@Nullable
                                                        String creditor)
```
    (Key Field) Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: Creditor
    
    The creditor ID number is cross-country and unique. It comprises the following elements:Characters 1-2: country key (for example, DE)Characters 3-4: check digit (is calculated the same way as the IBAN check digit)Characters 5-7: creditor business code (for example, for indicating individual business codes or branches of the creditor). The creditor business code is by default filled with the letters ZZZ. It is a non-identifying part of the SEPA mandate. This means that by changing the business code in the creditor ID no new mandate is created. Even after you have made such a change, a mandate search made by the system using the old creditor ID number still finds the corresponding mandates.Characters 8-35: national identification characteristic for the creditor, progressively numbered in ascending order.AT61ZZZ01234567890BE68ZZZ0123456789BG07ZZZ100064095CH13ZZZ00000012345CY34ZZZ123ACZ56ZZZ12345DE51ZZZ12345678901DK95ZZZ999912345678EE49ZZZEE00012345678ES50ZZZM23456789FI22BBB12345678FR72ZZZ123456GB49ZZZSDDBARC0000001UKGR44ZZZ12345HU54ZZZA09450512T123IE84ZZZ123456IS42ZZZ123456IT66ZZZA1B2C3D4E5F6G7H8LI26ZZZ00000012345LT30ZZZ123456789LU27ZZZ0000000000123456789LV29ZZZLV91122123459MC12ZZZ123456MT50ZZZ670169305TNL42ZZZ123456780001NO38ZZZ123456785PL18ZZZ0123456789PT73ZZZ123456RO25ZZZ1234567897SE41ZZZ1234567890SI13ZZZ12345674SK50ZZZ00000000001
    
    Returns:
    
    this.
  - sEPAMandate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandate(@Nullable
                                                           String sEPAMandate)
```
    (Key Field) Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: SEPAMandate
    
    The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment.Whether internal or external number assignment (or both) is possible depends on the application concerned.Once you have created the mandate, you can no longer change its mandate reference.At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field.Notes on Assigning Contract Accounts and Contracts to MandatesYou can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment.Notes on Using Alternative PayersIf you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen.ExampleYou enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1.Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects.Example - Assignment of a mandate to multiple contract accountsContract account Mandate (in Contract Acct) MeaningC1 M1 Mandate M1 is valid for C1.C2 M1 Mandate M1 is also valid for C2.C3 M2 Mandate M2 is valid for C3.C4 M2 Mandate M2 is also valid for C4.Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account.Example - Assignment of one contract account per mandateMandate Contract Account (in Mandate) MeaningM1 C1 Mandate M1 is only valid for items of contract account C1.M2 C2 Mandate M2 is only valid for items of contract account C2.If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects.The examples above apply in a similar manner to the assignment of contracts.Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate.If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details.If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment.If you do not make any specification, the system uses the first mandate that qualifies for the payment.
    
    Returns:
    
    this.
  - sEPAPaymentType
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAPaymentType(@Nullable
                                                               String sEPAPaymentType)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SEPAPaymentType
    
    The payment type describes whether the mandate is to be used for recurring payments or only used for a one-off payment.Once a one-off mandate has been used in the payment program (for FI-CA or FI-AP), this mandate cannot be used again, even if the payment is returned.
    
    Returns:
    
    this.
  - senderType
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderType(@Nullable
                                                          String senderType)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SenderType
    
    In the BOR, business objects are identified by the object category (for example, BUS2032) and a descriptive English name (for example, SalesOrder). Both names must be unique for all object categories.Business objects are frequently addressed via the descriptive name from external applications, whereas internally in the BOR by using the object category. Originally, only the internal key was used; but the need for a name arose due to the increased use of business objects. Both names are now stored for reasons of compatibility.The object category can have a maximum of 10 characters.Examples:BUS2032BUS6026
    
    Returns:
    
    this.
  - sender
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sender(@Nullable
                                                      String sender)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: Sender
    
    The key is made up by stringing together all key fields that are defined for objects of this category in the Business Object Repository.
    
    Returns:
    
    this.
  - senderLastName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderLastName(@Nullable
                                                              String senderLastName)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: SenderLastName
    
    Returns:
    
    this.
  - senderFirstName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderFirstName(@Nullable
                                                               String senderFirstName)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: SenderFirstName
    
    Returns:
    
    this.
  - senderStreetName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderStreetName(@Nullable
                                                                String senderStreetName)
```
    Constraints: Not nullable, Maximum length: 60
    Original property name from the Odata EDM: SenderStreetName
    
    The street name is saved, redundantly in upper case in another database field, for search help purposes.There are other fields for address parts which can be printed above or below the street. See Print the Street address.The house number and other supplements are usually maintained in their own fields. See Formatting the Street line.
    
    Returns:
    
    this.
  - senderHouseNumber
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderHouseNumber(@Nullable
                                                                 String senderHouseNumber)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SenderHouseNumber
    
    It is printed in the Street line.Other supplementary street information can be entered in the House number supplement or one of the Street2, Street3, Street4 or Street5 fields. See Print the Street address.A house number (e.g. 117) or a house number with supplement (e.g. 117a), or a house number range (e.g. 16-20), can be maintained in this field.
    
    Returns:
    
    this.
  - senderPostalCode
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderPostalCode(@Nullable
                                                                String senderPostalCode)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SenderPostalCode
    
    If different postal codes are maintained for the PO Box and Street address of an address, this field contains the Street address postal code.
    
    Returns:
    
    this.
  - senderCityName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderCityName(@Nullable
                                                              String senderCityName)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: SenderCityName
    
    The city name is saved redundantly in another database field in upper- case letters, for search help.If the Postal regional structure ('city file') is active, the city name is checked against the Cities defined in the regional structure.
    
    Returns:
    
    this.
  - senderCountry
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderCountry(@Nullable
                                                             String senderCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SenderCountry
    
    The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country-code or a typical country key, for example, in Germany the Federal statistics office key.The country keys are determined at system installation in the global settings.The definition of the country key in the SAP system does not have to match political or government entities.Since the country key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country key cannot query the country key T005-LAND1, but have to program based on the ISO code T005 INTCA.
    postal code or bank account number.
    
    Returns:
    
    this.
  - senderLanguage
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderLanguage(@Nullable
                                                              String senderLanguage)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: SenderLanguage
    
    In DISPLAY mode, this field identifies the language a record is written in.In CREATE mode, use this field to identify the language you will use to enter a description. To do so either:Type in the appropriate code, orRequest a list of language codes and make a selection by either:. Pressing F4, or. Clicking the down arrowNOTE: It is not possible to make entries in this field, everywhere in the system. Sometimes the system automatically completes the field, and you may not change it.
    
    Returns:
    
    this.
  - senderIBAN
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderIBAN(@Nullable
                                                          String senderIBAN)
```
    Constraints: Not nullable, Maximum length: 34
    Original property name from the Odata EDM: SenderIBAN
    
    Commitee for Banking Standards) to represent bank details. AN IBANcontains a maximum of 34 alphanumerical symbols and is made up acombination of hte following elements:The bank's country key (ISO code)A two-figure check digitCountry-specific account number (in Germany, for example, this consistsof the bank number and the account number, while in France it consistsof the bank number, the account number and the bank control key).The IBAN simplifies international payments and also provides benefitsfor domestic payments in some countries. In some countries, it alsoprovides advantages with respect to value dates and fees.The IBAN can be stored in parallel with the bank details, but does notreplace 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, whichcorresponds to one account number, the SAP system creates a proposalonly. You can either confirm or change this. If the system was not ableto create a proposal, enter the IBAN yourself.In Belgium, an IBAN might look like this:Electronic form:BE62510007547061Printed form, as it appears on the invoice:IBAN BE62 5100 0754 7061
    
    Returns:
    
    this.
  - senderBankSWIFTCode
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderBankSWIFTCode(@Nullable
                                                                   String senderBankSWIFTCode)
```
    Constraints: Not nullable, Maximum length: 11
    Original property name from the Odata EDM: SenderBankSWIFTCode
    
    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.
    
    Returns:
    
    this.
  - alternativePayerName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder alternativePayerName(@Nullable
                                                                    String alternativePayerName)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: AlternativePayerName
    
    If the mandate is used for collecting your own invoices, leave the field empty. .
    the Debtor Reference Party').
    
    Returns:
    
    this.
  - recipientType
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientType(@Nullable
                                                             String recipientType)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: RecipientType
    
    In the BOR, business objects are identified by the object category (for example, BUS2032) and a descriptive English name (for example, SalesOrder). Both names must be unique for all object categories.Business objects are frequently addressed via the descriptive name from external applications, whereas internally in the BOR by using the object category. Originally, only the internal key was used; but the need for a name arose due to the increased use of business objects. Both names are now stored for reasons of compatibility.The object category can have a maximum of 10 characters.Examples:BUS2032BUS6026
    
    Returns:
    
    this.
  - recipient
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipient(@Nullable
                                                         String recipient)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: Recipient
    
    The key is made up by stringing together all key fields that are defined for objects of this category in the Business Object Repository.
    
    Returns:
    
    this.
  - recipientName1
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientName1(@Nullable
                                                              String recipientName1)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: RecipientName1
    
    Returns:
    
    this.
  - recipientName2
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientName2(@Nullable
                                                              String recipientName2)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: RecipientName2
    
    Returns:
    
    this.
  - recipientStreetName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientStreetName(@Nullable
                                                                   String recipientStreetName)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: RecipientStreetName
    
    The street name is saved, redundantly in upper case in another database field, for search help purposes.There are other fields for address parts which can be printed above or below the street. See Print the Street address.The house number and other supplements are usually maintained in their own fields. See Formatting the Street line.
    
    Returns:
    
    this.
  - recipientHouseNumber
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientHouseNumber(@Nullable
                                                                    String recipientHouseNumber)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: RecipientHouseNumber
    
    It is printed in the Street line.Other supplementary street information can be entered in the House number supplement or one of the Street2, Street3, Street4 or Street5 fields. See Print the Street address.A house number (e.g. 117) or a house number with supplement (e.g. 117a), or a house number range (e.g. 16-20), can be maintained in this field.
    
    Returns:
    
    this.
  - recipientPostalCode
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientPostalCode(@Nullable
                                                                   String recipientPostalCode)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: RecipientPostalCode
    
    If different postal codes are maintained for the PO Box and Street address of an address, this field contains the Street address postal code.
    
    Returns:
    
    this.
  - recipientCityName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientCityName(@Nullable
                                                                 String recipientCityName)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: RecipientCityName
    
    The city name is saved redundantly in another database field in upper- case letters, for search help.If the Postal regional structure ('city file') is active, the city name is checked against the Cities defined in the regional structure.
    
    Returns:
    
    this.
  - recipientCountry
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder recipientCountry(@Nullable
                                                                String recipientCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: RecipientCountry
    
    The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country-code or a typical country key, for example, in Germany the Federal statistics office key.The country keys are determined at system installation in the global settings.The definition of the country key in the SAP system does not have to match political or government entities.Since the country key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country key cannot query the country key T005-LAND1, but have to program based on the ISO code T005 INTCA.
    postal code or bank account number.
    
    Returns:
    
    this.
  - sEPAMandateReferenceType
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateReferenceType(@Nullable
                                                                        String sEPAMandateReferenceType)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SEPAMandateReferenceType
    
    In the BOR, business objects are identified by the object category (for example, BUS2032) and a descriptive English name (for example, SalesOrder). Both names must be unique for all object categories.Business objects are frequently addressed via the descriptive name from external applications, whereas internally in the BOR by using the object category. Originally, only the internal key was used; but the need for a name arose due to the increased use of business objects. Both names are now stored for reasons of compatibility.The object category can have a maximum of 10 characters.Examples:BUS2032BUS6026
    
    Returns:
    
    this.
  - sEPAMandateReference
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateReference(@Nullable
                                                                    String sEPAMandateReference)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: SEPAMandateReference
    
    The key is made up by stringing together all key fields that are defined for objects of this category in the Business Object Repository.
    
    Returns:
    
    this.
  - sEPAMandateReferenceDesc
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateReferenceDesc(@Nullable
                                                                        String sEPAMandateReferenceDesc)
```
    Constraints: Not nullable, Maximum length: 50
    Original property name from the Odata EDM: SEPAMandateReferenceDesc
    
    Returns:
    
    this.
  - validityStartDate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder validityStartDate(@Nullable
                                                                 LocalDateTime validityStartDate)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: ValidityStartDate
    
    Enter the date here from which the mandate is valid. You can create a mandate today, for example, that is only to be used from the next month.This involves the validity of the mandate, and not, for example, the validity of a lock. For instance, a locked mandate with a validity from 01.03 to 01.08 cannot be used on 01.09 either (because it is only valid to 01.08).
    
    Returns:
    
    this.
  - validityEndDate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder validityEndDate(@Nullable
                                                               LocalDateTime validityEndDate)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: ValidityEndDate
    
    Enter the date here to which the mandate is valid. You can create a mandate, for example, that is only to be used up to a certain date.This involves the validity of the mandate, and not, for example, the validity of a lock. For instance, a locked mandate with a validity from 01.03 to 01.08 cannot be used on 01.09 either (because it is only valid to 01.08).
    
    Returns:
    
    this.
  - sEPASignatureCityName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPASignatureCityName(@Nullable
                                                                     String sEPASignatureCityName)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: SEPASignatureCityName
    
    Returns:
    
    this.
  - sEPASignatureDate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPASignatureDate(@Nullable
                                                                 LocalDateTime sEPASignatureDate)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: SEPASignatureDate
    
    The date on which the issuer of the mandate signed it. The date is retained in the creditor#s system in the mandate data.When you archive mandates, the date the mandate was created applies and not the date of the signature.19920301
    
    Returns:
    
    this.
  - sEPAMandateStatus
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateStatus(@Nullable
                                                                 String sEPAMandateStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SEPAMandateStatus
    
    A mandate can always take the following status:EnteredYou can use the status Entered to save the basic data of a mandate, for example, if you are dealing (in the case of the payer/debtor) with a potential customer who has not yet received any documents for mandate creation.To Be ConfirmedYou can use the status To Be Confirmed, for example, if you are dealing in the case of the payer (debtor) with a potential customer who has already received documentation for the mandate creation but whose signature is still missing, as a signed sales order is a prerequisite for the creation of a mandate.ActiveTo be able to use mandates in a payment program, they must have the status Active.LockedTo lock a mandate, either temporarily or permanently, set the status Locked.CanceledTo cancel a mandate created inadvertantly, set the status Canceled. It is possible for you to reactivate a canceled mandate.ObsoleteIf you have not used a mandate for at least 36 months or there are no postings for this mandate since then, the system changes the status to Obsolete.The mandate can no longer be used, and you cannot change its status. To find obsolete mandates, you can select them using transaction FSEPA_M4. You can also set this status manually.CompletedIf the application knows when you enter a mandate use that this use was the last intended use of the mandate (for example, direct debit of the last installment of a loan), the system can set the status to Completed. The mandate can then no longer be used. The system also sets this status if you are using a mandate for a one-off payment.Note that not all applications support all of these statuses.
    
    Returns:
    
    this.
  - alternativePayer
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder alternativePayer(@Nullable
                                                                String alternativePayer)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: AlternativePayer
    
    If the mandate is used for collecting your own invoices, leave the field empty.
    ('Identification Code of Debtor Reference Party').
    
    Returns:
    
    this.
  - alternativePayeeName
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder alternativePayeeName(@Nullable
                                                                    String alternativePayeeName)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: AlternativePayeeName
    field is only filled if the collecting payment is made on behalf of a third party.
    
    Returns:
    
    this.
  - alternativePayee
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder alternativePayee(@Nullable
                                                                String alternativePayee)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: AlternativePayee
    Party). This field is only filled if the collecting payment is made on behalf of a third party.
    
    Returns:
    
    this.
  - sEPAMandateIsB2BMandate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateIsB2BMandate(@Nullable
                                                                       Boolean sEPAMandateIsB2BMandate)
```
    Constraints: Not nullable
    Original property name from the Odata EDM: SEPAMandateIsB2BMandate
    
    ID of mandate as business-to business mandate. For B2B mandates specific rules apply regarding the deadlines and return option of payments.Payments with a B2B mandate are processed by the bank 1 day after presentation.For payments with core mandates of type Recurring Mandate 2 days apply, for payments with core mandates of type One-Time Mandate and for the first payment with a core mandate of type Recurring Mandate 5 days apply.
    
    Returns:
    
    this.
  - senderExternalID
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder senderExternalID(@Nullable
                                                                String senderExternalID)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: SenderExternalID
    
    The ID of the payer is any optional external number that is assigned to the payer and is passed on by the financial institution when you execute a SEPA debit memo.The ID number is not necessarily the customer number of the payer in the creditor#s system.
    
    Returns:
    
    this.
  - sEPAMandateOrganizationalUnit1
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateOrganizationalUnit1(@Nullable
                                                                              String sEPAMandateOrganizationalUnit1)
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: SEPAMandateOrganizationalUnit1
    
    Returns:
    
    this.
  - sEPAMandateOrganizationalUnit2
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateOrganizationalUnit2(@Nullable
                                                                              String sEPAMandateOrganizationalUnit2)
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: SEPAMandateOrganizationalUnit2
    
    Returns:
    
    this.
  - sEPAMandateOrganizationalUnit3
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateOrganizationalUnit3(@Nullable
                                                                              String sEPAMandateOrganizationalUnit3)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: SEPAMandateOrganizationalUnit3
    
    Returns:
    
    this.
  - sEPAMandateOrganizationalUnit4
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateOrganizationalUnit4(@Nullable
                                                                              String sEPAMandateOrganizationalUnit4)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: SEPAMandateOrganizationalUnit4
    
    Returns:
    
    this.
  - sEPAMandateFirstUseDate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateFirstUseDate(@Nullable
                                                                       LocalDateTime sEPAMandateFirstUseDate)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: SEPAMandateFirstUseDate
    
    Date in the form YYYYMMDD (where Y = year, M = month, D = day)19920301
    
    Returns:
    
    this.
  - sEPAMandateFirstUseObjTypeCode
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateFirstUseObjTypeCode(@Nullable
                                                                              String sEPAMandateFirstUseObjTypeCode)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SEPAMandateFirstUseObjTypeCode
    
    When the payment program uses a SEPA mandate in FI-CA or FI-AR, the technical key of the business object for the payment document or payment order created is entered here.UseExamples:FI-CA: payment document CA_DOC / payment order CA_PYORDFI-AR: payment document BKPF / payment order PYORD
    
    Returns:
    
    this.
  - sEPAMandateFirstUsePaymentDoc
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateFirstUsePaymentDoc(@Nullable
                                                                             String sEPAMandateFirstUsePaymentDoc)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: SEPAMandateFirstUsePaymentDoc
    
    When the payment program uses a SEPA mandate in FI-CA or FI-AR, the document number of the payment document posted is entered here.The use is entered by the payment program, and not later by the payment medium printout.
    
    Returns:
    
    this.
  - sEPAMandateLastUseDate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateLastUseDate(@Nullable
                                                                      LocalDateTime sEPAMandateLastUseDate)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: SEPAMandateLastUseDate
    
    Date in the form YYYYMMDD (where Y = year, M = month, D = day)19920301
    
    Returns:
    
    this.
  - sEPAMandateLastUseObjTypeCode
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateLastUseObjTypeCode(@Nullable
                                                                             String sEPAMandateLastUseObjTypeCode)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SEPAMandateLastUseObjTypeCode
    
    When the payment program uses a SEPA mandate in FI-CA or FI-AR, the technical key of the business object for the payment document or payment order created is entered here.FI-CA: payment document CA_DOC / payment order CA_PYORDFI-AR: payment document BKPF / payment order PYORD
    
    Returns:
    
    this.
  - sEPAMandateLastUsePaymentDoc
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sEPAMandateLastUsePaymentDoc(@Nullable
                                                                            String sEPAMandateLastUsePaymentDoc)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: SEPAMandateLastUsePaymentDoc
    
    When the payment program uses a SEPA mandate in FI-CA or FI-AR, the document number of the payment document posted is entered here.The use is entered by the payment program, and not later by the payment medium printout.
    
    Returns:
    
    this.
  - sepaCreditorIdOrigin
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder sepaCreditorIdOrigin(@Nullable
                                                                    String sepaCreditorIdOrigin)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: SepaCreditorIdOrigin
    
    Returns:
    
    this.
  - originalSEPAMandate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder originalSEPAMandate(@Nullable
                                                                   String originalSEPAMandate)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: OriginalSEPAMandate
    
    Returns:
    
    this.
  - version
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder version(@Nullable
                                                       String version)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Version
    
    For some fields, it is defined in the system that a new version is created when you change a field (for example, creditor, IBAN), as when you use the mandate following such a change the old values have to be sent as well ('amendment'). These fields are defined in table SEPA_SFIELDS for each application.In addition, you can specify in Customizing (SM30 / V_SEPA_FIELDS) that a new version of the mandate should be created when you change a field for other fields. For the Contract Accounts Receivable and Payable application you find this in Customizing under Business Transactions -> Payments -> Incoming/Outgoing Payment Creation -> Define Modifiable Fields.Mandate is created with version 0 and location = 'A'. If you make a change so the location = 'B, then:Version Location0 B (current version)1 A (first version)If you make a further change of location of 'B' to location = 'C', then:Version Location0 C (current version)1 A (first version)2 B (second version)
    the mandate is stored under a new version number. The version number is always increased by 1. The current SEPA mandate is always version 0 (zero).
    
    Returns:
    
    this.
  - createdByUser
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder createdByUser(@Nullable
                                                             String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Returns:
    
    this.
  - creationDate
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder creationDate(@Nullable
                                                            LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    this.
  - creationTime
```
@Nonnull
public SEPAMandate.SEPAMandateBuilder creationTime(@Nullable
                                                            LocalTime creationTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Returns:
    
    this.
  - build
```
@Nonnull
public SEPAMandate build()
```
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class Object

Class SEPAMandate.SEPAMandateBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

sepaMandateUsage

sEPAMandateApplication

creditor

sEPAMandate

sEPAPaymentType

senderType

sender

senderLastName

senderFirstName

senderStreetName

senderHouseNumber

senderPostalCode

senderCityName

senderCountry

senderLanguage

senderIBAN

senderBankSWIFTCode

alternativePayerName

recipientType

recipient

recipientName1

recipientName2

recipientStreetName

recipientHouseNumber

recipientPostalCode

recipientCityName

recipientCountry

sEPAMandateReferenceType

sEPAMandateReference

sEPAMandateReferenceDesc

validityStartDate

validityEndDate

sEPASignatureCityName

sEPASignatureDate

sEPAMandateStatus

alternativePayer

alternativePayeeName

alternativePayee

sEPAMandateIsB2BMandate

senderExternalID

sEPAMandateOrganizationalUnit1

sEPAMandateOrganizationalUnit2

sEPAMandateOrganizationalUnit3

sEPAMandateOrganizationalUnit4

sEPAMandateFirstUseDate

sEPAMandateFirstUseObjTypeCode

sEPAMandateFirstUsePaymentDoc

sEPAMandateLastUseDate

sEPAMandateLastUseObjTypeCode

sEPAMandateLastUsePaymentDoc

sepaCreditorIdOrigin

originalSEPAMandate

version

createdByUser

creationDate

creationTime

build

toString