public static class SEPAMandateUsage.SEPAMandateUsageBuilder extends Object
| Modifier and Type | Method and Description |
|---|---|
SEPAMandateUsage |
build() |
SEPAMandateUsage.SEPAMandateUsageBuilder |
creditor(String creditor)
(Key Field) Constraints: Not nullable, Maximum length: 35
|
SEPAMandateUsage.SEPAMandateUsageBuilder |
sEPAMandate(String sEPAMandate)
(Key Field) Constraints: Not nullable, Maximum length: 35
|
SEPAMandateUsage.SEPAMandateUsageBuilder |
sEPAMandateApplication(String sEPAMandateApplication)
Constraints: Not nullable, Maximum length: 1
|
SEPAMandateUsage.SEPAMandateUsageBuilder |
sEPAMandateUseDate(LocalDateTime sEPAMandateUseDate)
(Key Field) Constraints: Not nullable, Precision: 7
|
SEPAMandateUsage.SEPAMandateUsageBuilder |
sEPAMandateUseObjectType(String sEPAMandateUseObjectType)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
SEPAMandateUsage.SEPAMandateUsageBuilder |
sEPAMandateUsePaymentDoc(String sEPAMandateUsePaymentDoc)
(Key Field) Constraints: Not nullable, Maximum length: 70
|
String |
toString() |
public SEPAMandateUsage.SEPAMandateUsageBuilder sEPAMandateApplication(@Nullable String sEPAMandateApplication)
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.public SEPAMandateUsage.SEPAMandateUsageBuilder creditor(@Nullable String creditor)
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
public SEPAMandateUsage.SEPAMandateUsageBuilder sEPAMandate(@Nullable String sEPAMandate)
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.
public SEPAMandateUsage.SEPAMandateUsageBuilder sEPAMandateUseDate(@Nullable LocalDateTime sEPAMandateUseDate)
Original property name from the Odata EDM: SEPAMandateUseDate
Date in the form YYYYMMDD (where Y = year, M = month, D = day)19920301
public SEPAMandateUsage.SEPAMandateUsageBuilder sEPAMandateUseObjectType(@Nullable String sEPAMandateUseObjectType)
Original property name from the Odata EDM: SEPAMandateUseObjectType
Business objects in the BOR are identified by the object type (for example BUS2032) and a descriptive English name (for example, SalesOrder). Both means of identification must be unique among all object types.Business objects are often addressed using the descriptive name from external applications, while internally in the BOR they are mostly identified using the object type. Initially, only the internal key was used, but the extensive use of business objects has given rise to the need for addressing them using names. For compatibility reasons, both identifiers are now used.The object type can have a maximum of 10 characters.Examples:BUS2032BUS6026
public SEPAMandateUsage.SEPAMandateUsageBuilder sEPAMandateUsePaymentDoc(@Nullable String sEPAMandateUsePaymentDoc)
Original property name from the Odata EDM: SEPAMandateUsePaymentDoc
The key is formed by linking all of the key fields together without any gaps. The key fields are defined for objects of this type in the Business Object Repository.
public SEPAMandateUsage build()
Copyright © 2019 SAP SE. All rights reserved.