public class SEPAMandate extends VdmEntity<SEPAMandate>
Original entity name from the Odata EDM: SEPAMandateType
Modifier and Type | Class and Description |
---|---|
static class |
SEPAMandate.SEPAMandateBuilder
Helper class to allow for fluent creation of SEPAMandate instances.
|
Modifier and Type | Field and Description |
---|---|
static SEPAMandateSelectable |
ALL_FIELDS
Selector for all available fields of SEPAMandate.
|
static SEPAMandateField<String> |
ALTERNATIVE_PAYEE
Use with available fluent helpers to apply the AlternativePayee field to query operations.
|
static SEPAMandateField<String> |
ALTERNATIVE_PAYEE_NAME
Use with available fluent helpers to apply the AlternativePayeeName field to query operations.
|
static SEPAMandateField<String> |
ALTERNATIVE_PAYER
Use with available fluent helpers to apply the AlternativePayer field to query operations.
|
static SEPAMandateField<String> |
ALTERNATIVE_PAYER_NAME
Use with available fluent helpers to apply the AlternativePayerName field to query operations.
|
static SEPAMandateField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static SEPAMandateField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static SEPAMandateField<LocalTime> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static SEPAMandateField<String> |
CREDITOR
Use with available fluent helpers to apply the Creditor field to query operations.
|
static SEPAMandateField<String> |
ORIGINAL_SEPA_MANDATE
Use with available fluent helpers to apply the OriginalSEPAMandate field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT
Use with available fluent helpers to apply the Recipient field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_CITY_NAME
Use with available fluent helpers to apply the RecipientCityName field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_COUNTRY
Use with available fluent helpers to apply the RecipientCountry field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_HOUSE_NUMBER
Use with available fluent helpers to apply the RecipientHouseNumber field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_NAME1
Use with available fluent helpers to apply the RecipientName1 field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_NAME2
Use with available fluent helpers to apply the RecipientName2 field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_POSTAL_CODE
Use with available fluent helpers to apply the RecipientPostalCode field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_STREET_NAME
Use with available fluent helpers to apply the RecipientStreetName field to query operations.
|
static SEPAMandateField<String> |
RECIPIENT_TYPE
Use with available fluent helpers to apply the RecipientType field to query operations.
|
static SEPAMandateField<String> |
SENDER
Use with available fluent helpers to apply the Sender field to query operations.
|
static SEPAMandateField<String> |
SENDER_BANK_SWIFT_CODE
Use with available fluent helpers to apply the SenderBankSWIFTCode field to query operations.
|
static SEPAMandateField<String> |
SENDER_CITY_NAME
Use with available fluent helpers to apply the SenderCityName field to query operations.
|
static SEPAMandateField<String> |
SENDER_COUNTRY
Use with available fluent helpers to apply the SenderCountry field to query operations.
|
static SEPAMandateField<String> |
SENDER_EXTERNAL_ID
Use with available fluent helpers to apply the SenderExternalID field to query operations.
|
static SEPAMandateField<String> |
SENDER_FIRST_NAME
Use with available fluent helpers to apply the SenderFirstName field to query operations.
|
static SEPAMandateField<String> |
SENDER_HOUSE_NUMBER
Use with available fluent helpers to apply the SenderHouseNumber field to query operations.
|
static SEPAMandateField<String> |
SENDER_IBAN
Use with available fluent helpers to apply the SenderIBAN field to query operations.
|
static SEPAMandateField<String> |
SENDER_LANGUAGE
Use with available fluent helpers to apply the SenderLanguage field to query operations.
|
static SEPAMandateField<String> |
SENDER_LAST_NAME
Use with available fluent helpers to apply the SenderLastName field to query operations.
|
static SEPAMandateField<String> |
SENDER_POSTAL_CODE
Use with available fluent helpers to apply the SenderPostalCode field to query operations.
|
static SEPAMandateField<String> |
SENDER_STREET_NAME
Use with available fluent helpers to apply the SenderStreetName field to query operations.
|
static SEPAMandateField<String> |
SENDER_TYPE
Use with available fluent helpers to apply the SenderType field to query operations.
|
static SEPAMandateField<String> |
SEPA_CREDITOR_ID_ORIGIN
Use with available fluent helpers to apply the SepaCreditorIdOrigin field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE
Use with available fluent helpers to apply the SEPAMandate field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_APPLICATION
Use with available fluent helpers to apply the SEPAMandateApplication field to query operations.
|
static SEPAMandateField<LocalDateTime> |
SEPA_MANDATE_FIRST_USE_DATE
Use with available fluent helpers to apply the SEPAMandateFirstUseDate field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_FIRST_USE_OBJ_TYPE_CODE
Use with available fluent helpers to apply the SEPAMandateFirstUseObjTypeCode field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_FIRST_USE_PAYMENT_DOC
Use with available fluent helpers to apply the SEPAMandateFirstUsePaymentDoc field to query operations.
|
static SEPAMandateField<Boolean> |
SEPA_MANDATE_IS_B2_B_MANDATE
Use with available fluent helpers to apply the SEPAMandateIsB2BMandate field to query operations.
|
static SEPAMandateField<LocalDateTime> |
SEPA_MANDATE_LAST_USE_DATE
Use with available fluent helpers to apply the SEPAMandateLastUseDate field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_LAST_USE_OBJ_TYPE_CODE
Use with available fluent helpers to apply the SEPAMandateLastUseObjTypeCode field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_LAST_USE_PAYMENT_DOC
Use with available fluent helpers to apply the SEPAMandateLastUsePaymentDoc field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_ORGANIZATIONAL_UNIT1
Use with available fluent helpers to apply the SEPAMandateOrganizationalUnit1 field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_ORGANIZATIONAL_UNIT2
Use with available fluent helpers to apply the SEPAMandateOrganizationalUnit2 field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_ORGANIZATIONAL_UNIT3
Use with available fluent helpers to apply the SEPAMandateOrganizationalUnit3 field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_ORGANIZATIONAL_UNIT4
Use with available fluent helpers to apply the SEPAMandateOrganizationalUnit4 field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_REFERENCE
Use with available fluent helpers to apply the SEPAMandateReference field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_REFERENCE_DESC
Use with available fluent helpers to apply the SEPAMandateReferenceDesc field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_REFERENCE_TYPE
Use with available fluent helpers to apply the SEPAMandateReferenceType field to query operations.
|
static SEPAMandateField<String> |
SEPA_MANDATE_STATUS
Use with available fluent helpers to apply the SEPAMandateStatus field to query operations.
|
static SEPAMandateField<String> |
SEPA_PAYMENT_TYPE
Use with available fluent helpers to apply the SEPAPaymentType field to query operations.
|
static SEPAMandateField<String> |
SEPA_SIGNATURE_CITY_NAME
Use with available fluent helpers to apply the SEPASignatureCityName field to query operations.
|
static SEPAMandateField<LocalDateTime> |
SEPA_SIGNATURE_DATE
Use with available fluent helpers to apply the SEPASignatureDate field to query operations.
|
static SEPAMandateLink<SEPAMandateUsage> |
TO_SEPA_MANDATE_USAGE
Use with available fluent helpers to apply the SEPAMandateUsage navigation property to query operations.
|
static SEPAMandateField<LocalDateTime> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static SEPAMandateField<LocalDateTime> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
static SEPAMandateField<String> |
VERSION
Use with available fluent helpers to apply the Version field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SEPAMandate() |
SEPAMandate(String sEPAMandateApplication,
String creditor,
String sEPAMandate,
String sEPAPaymentType,
String senderType,
String sender,
String senderLastName,
String senderFirstName,
String senderStreetName,
String senderHouseNumber,
String senderPostalCode,
String senderCityName,
String senderCountry,
String senderLanguage,
String senderIBAN,
String senderBankSWIFTCode,
String alternativePayerName,
String recipientType,
String recipient,
String recipientName1,
String recipientName2,
String recipientStreetName,
String recipientHouseNumber,
String recipientPostalCode,
String recipientCityName,
String recipientCountry,
String sEPAMandateReferenceType,
String sEPAMandateReference,
String sEPAMandateReferenceDesc,
LocalDateTime validityStartDate,
LocalDateTime validityEndDate,
String sEPASignatureCityName,
LocalDateTime sEPASignatureDate,
String sEPAMandateStatus,
String alternativePayer,
String alternativePayeeName,
String alternativePayee,
Boolean sEPAMandateIsB2BMandate,
String senderExternalID,
String sEPAMandateOrganizationalUnit1,
String sEPAMandateOrganizationalUnit2,
String sEPAMandateOrganizationalUnit3,
String sEPAMandateOrganizationalUnit4,
LocalDateTime sEPAMandateFirstUseDate,
String sEPAMandateFirstUseObjTypeCode,
String sEPAMandateFirstUsePaymentDoc,
LocalDateTime sEPAMandateLastUseDate,
String sEPAMandateLastUseObjTypeCode,
String sEPAMandateLastUsePaymentDoc,
String sepaCreditorIdOrigin,
String originalSEPAMandate,
String version,
String createdByUser,
LocalDateTime creationDate,
LocalTime creationTime,
List<SEPAMandateUsage> toSEPAMandateUsage) |
Modifier and Type | Method and Description |
---|---|
void |
addSEPAMandateUsage(SEPAMandateUsage... entity)
Adds elements to the list of associated SEPAMandateUsage entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static SEPAMandate.SEPAMandateBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SEPAMandateUsage> |
fetchSEPAMandateUsage()
Fetches the SEPAMandateUsage entities (one to many) associated with this entity.
|
static <T> SEPAMandateField<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 |
getAlternativePayee()
Constraints: Not nullable, Maximum length: 70
|
String |
getAlternativePayeeName()
Constraints: Not nullable, Maximum length: 40
|
String |
getAlternativePayer()
Constraints: Not nullable, Maximum length: 70
|
String |
getAlternativePayerName()
Constraints: Not nullable, Maximum length: 40
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 7
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCreditor()
(Key Field) Constraints: Not nullable, Maximum length: 35
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
protected Map<String,Object> |
getKey() |
String |
getOriginalSEPAMandate()
Constraints: Not nullable, Maximum length: 35
|
String |
getRecipient()
Constraints: Not nullable, Maximum length: 70
|
String |
getRecipientCityName()
Constraints: Not nullable, Maximum length: 40
|
String |
getRecipientCountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getRecipientHouseNumber()
Constraints: Not nullable, Maximum length: 10
|
String |
getRecipientName1()
Constraints: Not nullable, Maximum length: 40
|
String |
getRecipientName2()
Constraints: Not nullable, Maximum length: 40
|
String |
getRecipientPostalCode()
Constraints: Not nullable, Maximum length: 10
|
String |
getRecipientStreetName()
Constraints: Not nullable, Maximum length: 10
|
String |
getRecipientType()
Constraints: Not nullable, Maximum length: 10
|
String |
getSender()
Constraints: Not nullable, Maximum length: 70
|
String |
getSenderBankSWIFTCode()
Constraints: Not nullable, Maximum length: 11
|
String |
getSenderCityName()
Constraints: Not nullable, Maximum length: 40
|
String |
getSenderCountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getSenderExternalID()
Constraints: Not nullable, Maximum length: 35
|
String |
getSenderFirstName()
Constraints: Not nullable, Maximum length: 40
|
String |
getSenderHouseNumber()
Constraints: Not nullable, Maximum length: 10
|
String |
getSenderIBAN()
Constraints: Not nullable, Maximum length: 34
|
String |
getSenderLanguage()
Constraints: Not nullable, Maximum length: 2
|
String |
getSenderLastName()
Constraints: Not nullable, Maximum length: 40
|
String |
getSenderPostalCode()
Constraints: Not nullable, Maximum length: 10
|
String |
getSenderStreetName()
Constraints: Not nullable, Maximum length: 60
|
String |
getSenderType()
Constraints: Not nullable, Maximum length: 10
|
String |
getSepaCreditorIdOrigin()
Constraints: Not nullable, Maximum length: 35
|
String |
getSEPAMandate()
(Key Field) Constraints: Not nullable, Maximum length: 35
|
String |
getSEPAMandateApplication()
Constraints: Not nullable, Maximum length: 1
|
LocalDateTime |
getSEPAMandateFirstUseDate()
Constraints: Not nullable, Precision: 7
|
String |
getSEPAMandateFirstUseObjTypeCode()
Constraints: Not nullable, Maximum length: 10
|
String |
getSEPAMandateFirstUsePaymentDoc()
Constraints: Not nullable, Maximum length: 70
|
Boolean |
getSEPAMandateIsB2BMandate()
Constraints: Not nullable
|
LocalDateTime |
getSEPAMandateLastUseDate()
Constraints: Not nullable, Precision: 7
|
String |
getSEPAMandateLastUseObjTypeCode()
Constraints: Not nullable, Maximum length: 10
|
String |
getSEPAMandateLastUsePaymentDoc()
Constraints: Not nullable, Maximum length: 70
|
String |
getSEPAMandateOrganizationalUnit1()
Constraints: Not nullable, Maximum length: 20
|
String |
getSEPAMandateOrganizationalUnit2()
Constraints: Not nullable, Maximum length: 20
|
String |
getSEPAMandateOrganizationalUnit3()
Constraints: Not nullable, Maximum length: 35
|
String |
getSEPAMandateOrganizationalUnit4()
Constraints: Not nullable, Maximum length: 35
|
String |
getSEPAMandateReference()
Constraints: Not nullable, Maximum length: 70
|
String |
getSEPAMandateReferenceDesc()
Constraints: Not nullable, Maximum length: 50
|
String |
getSEPAMandateReferenceType()
Constraints: Not nullable, Maximum length: 10
|
String |
getSEPAMandateStatus()
Constraints: Not nullable, Maximum length: 1
|
io.vavr.control.Option<List<SEPAMandateUsage>> |
getSEPAMandateUsageIfPresent()
Retrieval of associated SEPAMandateUsage entities (one to many).
|
List<SEPAMandateUsage> |
getSEPAMandateUsageOrFetch()
Retrieval of associated SEPAMandateUsage entities (one to many).
|
String |
getSEPAPaymentType()
Constraints: Not nullable, Maximum length: 1
|
String |
getSEPASignatureCityName()
Constraints: Not nullable, Maximum length: 40
|
LocalDateTime |
getSEPASignatureDate()
Constraints: Not nullable, Precision: 7
|
Class<SEPAMandate> |
getType() |
LocalDateTime |
getValidityEndDate()
Constraints: Not nullable, Precision: 7
|
LocalDateTime |
getValidityStartDate()
Constraints: Not nullable, Precision: 7
|
String |
getVersion()
Constraints: Not nullable, Maximum length: 4
|
int |
hashCode() |
void |
setAlternativePayee(String alternativePayee)
Constraints: Not nullable, Maximum length: 70
|
void |
setAlternativePayeeName(String alternativePayeeName)
Constraints: Not nullable, Maximum length: 40
|
void |
setAlternativePayer(String alternativePayer)
Constraints: Not nullable, Maximum length: 70
|
void |
setAlternativePayerName(String alternativePayerName)
Constraints: Not nullable, Maximum length: 40
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 7
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCreditor(String creditor)
(Key Field) Constraints: Not nullable, Maximum length: 35
|
void |
setOriginalSEPAMandate(String originalSEPAMandate)
Constraints: Not nullable, Maximum length: 35
|
void |
setRecipient(String recipient)
Constraints: Not nullable, Maximum length: 70
|
void |
setRecipientCityName(String recipientCityName)
Constraints: Not nullable, Maximum length: 40
|
void |
setRecipientCountry(String recipientCountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setRecipientHouseNumber(String recipientHouseNumber)
Constraints: Not nullable, Maximum length: 10
|
void |
setRecipientName1(String recipientName1)
Constraints: Not nullable, Maximum length: 40
|
void |
setRecipientName2(String recipientName2)
Constraints: Not nullable, Maximum length: 40
|
void |
setRecipientPostalCode(String recipientPostalCode)
Constraints: Not nullable, Maximum length: 10
|
void |
setRecipientStreetName(String recipientStreetName)
Constraints: Not nullable, Maximum length: 10
|
void |
setRecipientType(String recipientType)
Constraints: Not nullable, Maximum length: 10
|
void |
setSender(String sender)
Constraints: Not nullable, Maximum length: 70
|
void |
setSenderBankSWIFTCode(String senderBankSWIFTCode)
Constraints: Not nullable, Maximum length: 11
|
void |
setSenderCityName(String senderCityName)
Constraints: Not nullable, Maximum length: 40
|
void |
setSenderCountry(String senderCountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setSenderExternalID(String senderExternalID)
Constraints: Not nullable, Maximum length: 35
|
void |
setSenderFirstName(String senderFirstName)
Constraints: Not nullable, Maximum length: 40
|
void |
setSenderHouseNumber(String senderHouseNumber)
Constraints: Not nullable, Maximum length: 10
|
void |
setSenderIBAN(String senderIBAN)
Constraints: Not nullable, Maximum length: 34
|
void |
setSenderLanguage(String senderLanguage)
Constraints: Not nullable, Maximum length: 2
|
void |
setSenderLastName(String senderLastName)
Constraints: Not nullable, Maximum length: 40
|
void |
setSenderPostalCode(String senderPostalCode)
Constraints: Not nullable, Maximum length: 10
|
void |
setSenderStreetName(String senderStreetName)
Constraints: Not nullable, Maximum length: 60
|
void |
setSenderType(String senderType)
Constraints: Not nullable, Maximum length: 10
|
void |
setSepaCreditorIdOrigin(String sepaCreditorIdOrigin)
Constraints: Not nullable, Maximum length: 35
|
void |
setSEPAMandate(String sEPAMandate)
(Key Field) Constraints: Not nullable, Maximum length: 35
|
void |
setSEPAMandateApplication(String sEPAMandateApplication)
Constraints: Not nullable, Maximum length: 1
|
void |
setSEPAMandateFirstUseDate(LocalDateTime sEPAMandateFirstUseDate)
Constraints: Not nullable, Precision: 7
|
void |
setSEPAMandateFirstUseObjTypeCode(String sEPAMandateFirstUseObjTypeCode)
Constraints: Not nullable, Maximum length: 10
|
void |
setSEPAMandateFirstUsePaymentDoc(String sEPAMandateFirstUsePaymentDoc)
Constraints: Not nullable, Maximum length: 70
|
void |
setSEPAMandateIsB2BMandate(Boolean sEPAMandateIsB2BMandate)
Constraints: Not nullable
|
void |
setSEPAMandateLastUseDate(LocalDateTime sEPAMandateLastUseDate)
Constraints: Not nullable, Precision: 7
|
void |
setSEPAMandateLastUseObjTypeCode(String sEPAMandateLastUseObjTypeCode)
Constraints: Not nullable, Maximum length: 10
|
void |
setSEPAMandateLastUsePaymentDoc(String sEPAMandateLastUsePaymentDoc)
Constraints: Not nullable, Maximum length: 70
|
void |
setSEPAMandateOrganizationalUnit1(String sEPAMandateOrganizationalUnit1)
Constraints: Not nullable, Maximum length: 20
|
void |
setSEPAMandateOrganizationalUnit2(String sEPAMandateOrganizationalUnit2)
Constraints: Not nullable, Maximum length: 20
|
void |
setSEPAMandateOrganizationalUnit3(String sEPAMandateOrganizationalUnit3)
Constraints: Not nullable, Maximum length: 35
|
void |
setSEPAMandateOrganizationalUnit4(String sEPAMandateOrganizationalUnit4)
Constraints: Not nullable, Maximum length: 35
|
void |
setSEPAMandateReference(String sEPAMandateReference)
Constraints: Not nullable, Maximum length: 70
|
void |
setSEPAMandateReferenceDesc(String sEPAMandateReferenceDesc)
Constraints: Not nullable, Maximum length: 50
|
void |
setSEPAMandateReferenceType(String sEPAMandateReferenceType)
Constraints: Not nullable, Maximum length: 10
|
void |
setSEPAMandateStatus(String sEPAMandateStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setSEPAMandateUsage(List<SEPAMandateUsage> value)
Overwrites the list of associated SEPAMandateUsage entities for the loaded navigation property
SEPAMandateUsage.
|
void |
setSEPAPaymentType(String sEPAPaymentType)
Constraints: Not nullable, Maximum length: 1
|
void |
setSEPASignatureCityName(String sEPASignatureCityName)
Constraints: Not nullable, Maximum length: 40
|
void |
setSEPASignatureDate(LocalDateTime sEPASignatureDate)
Constraints: Not nullable, Precision: 7
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setValidityEndDate(LocalDateTime validityEndDate)
Constraints: Not nullable, Precision: 7
|
void |
setValidityStartDate(LocalDateTime validityStartDate)
Constraints: Not nullable, Precision: 7
|
void |
setVersion(String version)
Constraints: Not nullable, Maximum length: 4
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final SEPAMandateSelectable ALL_FIELDS
public static final SEPAMandateField<String> SEPA_MANDATE_APPLICATION
public static final SEPAMandateField<String> CREDITOR
public static final SEPAMandateField<String> SEPA_MANDATE
public static final SEPAMandateField<String> SEPA_PAYMENT_TYPE
public static final SEPAMandateField<String> SENDER_TYPE
public static final SEPAMandateField<String> SENDER
public static final SEPAMandateField<String> SENDER_LAST_NAME
public static final SEPAMandateField<String> SENDER_FIRST_NAME
public static final SEPAMandateField<String> SENDER_STREET_NAME
public static final SEPAMandateField<String> SENDER_HOUSE_NUMBER
public static final SEPAMandateField<String> SENDER_POSTAL_CODE
public static final SEPAMandateField<String> SENDER_CITY_NAME
public static final SEPAMandateField<String> SENDER_COUNTRY
public static final SEPAMandateField<String> SENDER_LANGUAGE
public static final SEPAMandateField<String> SENDER_IBAN
public static final SEPAMandateField<String> SENDER_BANK_SWIFT_CODE
public static final SEPAMandateField<String> ALTERNATIVE_PAYER_NAME
public static final SEPAMandateField<String> RECIPIENT_TYPE
public static final SEPAMandateField<String> RECIPIENT
public static final SEPAMandateField<String> RECIPIENT_NAME1
public static final SEPAMandateField<String> RECIPIENT_NAME2
public static final SEPAMandateField<String> RECIPIENT_STREET_NAME
public static final SEPAMandateField<String> RECIPIENT_HOUSE_NUMBER
public static final SEPAMandateField<String> RECIPIENT_POSTAL_CODE
public static final SEPAMandateField<String> RECIPIENT_CITY_NAME
public static final SEPAMandateField<String> RECIPIENT_COUNTRY
public static final SEPAMandateField<String> SEPA_MANDATE_REFERENCE_TYPE
public static final SEPAMandateField<String> SEPA_MANDATE_REFERENCE
public static final SEPAMandateField<String> SEPA_MANDATE_REFERENCE_DESC
public static final SEPAMandateField<LocalDateTime> VALIDITY_START_DATE
public static final SEPAMandateField<LocalDateTime> VALIDITY_END_DATE
public static final SEPAMandateField<String> SEPA_SIGNATURE_CITY_NAME
public static final SEPAMandateField<LocalDateTime> SEPA_SIGNATURE_DATE
public static final SEPAMandateField<String> SEPA_MANDATE_STATUS
public static final SEPAMandateField<String> ALTERNATIVE_PAYER
public static final SEPAMandateField<String> ALTERNATIVE_PAYEE_NAME
public static final SEPAMandateField<String> ALTERNATIVE_PAYEE
public static final SEPAMandateField<Boolean> SEPA_MANDATE_IS_B2_B_MANDATE
public static final SEPAMandateField<String> SENDER_EXTERNAL_ID
public static final SEPAMandateField<String> SEPA_MANDATE_ORGANIZATIONAL_UNIT1
public static final SEPAMandateField<String> SEPA_MANDATE_ORGANIZATIONAL_UNIT2
public static final SEPAMandateField<String> SEPA_MANDATE_ORGANIZATIONAL_UNIT3
public static final SEPAMandateField<String> SEPA_MANDATE_ORGANIZATIONAL_UNIT4
public static final SEPAMandateField<LocalDateTime> SEPA_MANDATE_FIRST_USE_DATE
public static final SEPAMandateField<String> SEPA_MANDATE_FIRST_USE_OBJ_TYPE_CODE
public static final SEPAMandateField<String> SEPA_MANDATE_FIRST_USE_PAYMENT_DOC
public static final SEPAMandateField<LocalDateTime> SEPA_MANDATE_LAST_USE_DATE
public static final SEPAMandateField<String> SEPA_MANDATE_LAST_USE_OBJ_TYPE_CODE
public static final SEPAMandateField<String> SEPA_MANDATE_LAST_USE_PAYMENT_DOC
public static final SEPAMandateField<String> SEPA_CREDITOR_ID_ORIGIN
public static final SEPAMandateField<String> ORIGINAL_SEPA_MANDATE
public static final SEPAMandateField<String> VERSION
public static final SEPAMandateField<String> CREATED_BY_USER
public static final SEPAMandateField<LocalDateTime> CREATION_DATE
public static final SEPAMandateField<LocalTime> CREATION_TIME
public static final SEPAMandateLink<SEPAMandateUsage> TO_SEPA_MANDATE_USAGE
public SEPAMandate()
public SEPAMandate(@Nullable String sEPAMandateApplication, @Nullable String creditor, @Nullable String sEPAMandate, @Nullable String sEPAPaymentType, @Nullable String senderType, @Nullable String sender, @Nullable String senderLastName, @Nullable String senderFirstName, @Nullable String senderStreetName, @Nullable String senderHouseNumber, @Nullable String senderPostalCode, @Nullable String senderCityName, @Nullable String senderCountry, @Nullable String senderLanguage, @Nullable String senderIBAN, @Nullable String senderBankSWIFTCode, @Nullable String alternativePayerName, @Nullable String recipientType, @Nullable String recipient, @Nullable String recipientName1, @Nullable String recipientName2, @Nullable String recipientStreetName, @Nullable String recipientHouseNumber, @Nullable String recipientPostalCode, @Nullable String recipientCityName, @Nullable String recipientCountry, @Nullable String sEPAMandateReferenceType, @Nullable String sEPAMandateReference, @Nullable String sEPAMandateReferenceDesc, @Nullable LocalDateTime validityStartDate, @Nullable LocalDateTime validityEndDate, @Nullable String sEPASignatureCityName, @Nullable LocalDateTime sEPASignatureDate, @Nullable String sEPAMandateStatus, @Nullable String alternativePayer, @Nullable String alternativePayeeName, @Nullable String alternativePayee, @Nullable Boolean sEPAMandateIsB2BMandate, @Nullable String senderExternalID, @Nullable String sEPAMandateOrganizationalUnit1, @Nullable String sEPAMandateOrganizationalUnit2, @Nullable String sEPAMandateOrganizationalUnit3, @Nullable String sEPAMandateOrganizationalUnit4, @Nullable LocalDateTime sEPAMandateFirstUseDate, @Nullable String sEPAMandateFirstUseObjTypeCode, @Nullable String sEPAMandateFirstUsePaymentDoc, @Nullable LocalDateTime sEPAMandateLastUseDate, @Nullable String sEPAMandateLastUseObjTypeCode, @Nullable String sEPAMandateLastUsePaymentDoc, @Nullable String sepaCreditorIdOrigin, @Nullable String originalSEPAMandate, @Nullable String version, @Nullable String createdByUser, @Nullable LocalDateTime creationDate, @Nullable LocalTime creationTime, List<SEPAMandateUsage> toSEPAMandateUsage)
@Nonnull public Class<SEPAMandate> getType()
getType
in class VdmObject<SEPAMandate>
public void setSEPAMandateApplication(@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.
sEPAMandateApplication
- The application describes which application component (for example, FI-CA, FI-AR, FS-AM) the mandate
is being used in.public void setCreditor(@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
creditor
- Specifies a cross-country unique identification of the creditor of a SEPA direct debit.public void setSEPAMandate(@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.
sEPAMandate
- Identifies, together with the Creditor Identifier, the mandate uniquely.public void setSEPAPaymentType(@Nullable String sEPAPaymentType)
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.
sEPAPaymentType
- Payment typepublic void setSenderType(@Nullable String senderType)
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
senderType
- Internal technical key of a business object in the Business Object Repository (BOR).public void setSender(@Nullable String sender)
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.
sender
- Compound key of an object.public void setSenderLastName(@Nullable String senderLastName)
Original property name from the Odata EDM: SenderLastName
senderLastName
- Last Name of Business Partner (Person)public void setSenderFirstName(@Nullable String senderFirstName)
Original property name from the Odata EDM: SenderFirstName
senderFirstName
- First Name of Business Partner (Person)public void setSenderStreetName(@Nullable String senderStreetName)
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.
senderStreetName
- Street name as part of the address.public void setSenderHouseNumber(@Nullable String senderHouseNumber)
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.
senderHouseNumber
- House number as part of an address.public void setSenderPostalCode(@Nullable String senderPostalCode)
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.
senderPostalCode
- Postal code as part of the addresspublic void setSenderCityName(@Nullable String senderCityName)
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.
senderCityName
- City name as part of the address.public void setSenderCountry(@Nullable String senderCountry)
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.
senderCountry
- The country key contains information which the system uses to check entries such as the length of the
postal code or bank account number.public void setSenderLanguage(@Nullable String senderLanguage)
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.
senderLanguage
- The Language key field contains an alphanumeric code that identifies the language an entry is written
in.public void setSenderIBAN(@Nullable String senderIBAN)
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
senderIBAN
- A standard number standardized in accordance with the ECBS (Europeanpublic void setSenderBankSWIFTCode(@Nullable String senderBankSWIFTCode)
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.
senderBankSWIFTCode
- Uniquely identifies a bank throughout the world.public void setAlternativePayerName(@Nullable String alternativePayerName)
Original property name from the Odata EDM: AlternativePayerName
If the mandate is used for collecting your own invoices, leave the field empty. .
alternativePayerName
- Name of business partner or customer whose invoices are to be collected with this SEPA mandate ('Name
of the Debtor Reference Party').public void setRecipientType(@Nullable String recipientType)
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
recipientType
- Internal technical key of a business object in the Business Object Repository (BOR).public void setRecipient(@Nullable String recipient)
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.
recipient
- Compound key of an object.public void setRecipientName1(@Nullable String recipientName1)
Original property name from the Odata EDM: RecipientName1
recipientName1
- First name field for business partners in the Organization category.public void setRecipientName2(@Nullable String recipientName2)
Original property name from the Odata EDM: RecipientName2
recipientName2
- Second name field for business partners in the Organization category.public void setRecipientStreetName(@Nullable String recipientStreetName)
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.
recipientStreetName
- Street name as part of the address.public void setRecipientHouseNumber(@Nullable String recipientHouseNumber)
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.
recipientHouseNumber
- House number as part of an address.public void setRecipientPostalCode(@Nullable String recipientPostalCode)
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.
recipientPostalCode
- Postal code as part of the addresspublic void setRecipientCityName(@Nullable String recipientCityName)
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.
recipientCityName
- City name as part of the address.public void setRecipientCountry(@Nullable String recipientCountry)
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.
recipientCountry
- The country key contains information which the system uses to check entries such as the length of the
postal code or bank account number.public void setSEPAMandateReferenceType(@Nullable String sEPAMandateReferenceType)
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
sEPAMandateReferenceType
- Internal technical key of a business object in the Business Object Repository (BOR).public void setSEPAMandateReference(@Nullable String sEPAMandateReference)
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.
sEPAMandateReference
- Compound key of an object.public void setSEPAMandateReferenceDesc(@Nullable String sEPAMandateReferenceDesc)
Original property name from the Odata EDM: SEPAMandateReferenceDesc
sEPAMandateReferenceDesc
- Explanatory text fieldpublic void setValidityStartDate(@Nullable LocalDateTime validityStartDate)
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).
validityStartDate
- Date (YYYYMMDD)public void setValidityEndDate(@Nullable LocalDateTime validityEndDate)
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).
validityEndDate
- Date (YYYYMMDD)public void setSEPASignatureCityName(@Nullable String sEPASignatureCityName)
Original property name from the Odata EDM: SEPASignatureCityName
sEPASignatureCityName
- Location (city) of signaturepublic void setSEPASignatureDate(@Nullable LocalDateTime sEPASignatureDate)
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
sEPASignatureDate
- Date of signaturepublic void setSEPAMandateStatus(@Nullable String sEPAMandateStatus)
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.
sEPAMandateStatus
- Specifies the processing status of a mandate.public void setAlternativePayer(@Nullable String alternativePayer)
Original property name from the Odata EDM: AlternativePayer
If the mandate is used for collecting your own invoices, leave the field empty.
alternativePayer
- Identification of business partner or customer whose invoices are to be collected with this SEPA
mandate ('Identification Code of Debtor Reference Party').public void setAlternativePayeeName(@Nullable String alternativePayeeName)
Original property name from the Odata EDM: AlternativePayeeName
alternativePayeeName
- Name of the creditor for whom the collecting payment is made (Name of the Creditor Reference Party).
This field is only filled if the collecting payment is made on behalf of a third party.public void setAlternativePayee(@Nullable String alternativePayee)
Original property name from the Odata EDM: AlternativePayee
alternativePayee
- ID of the creditor for whom the collecting payment is made (Identification Code of the Creditor
Reference Party). This field is only filled if the collecting payment is made on behalf of a third
party.public void setSEPAMandateIsB2BMandate(@Nullable Boolean sEPAMandateIsB2BMandate)
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.
sEPAMandateIsB2BMandate
- Business-to-Business Mandatepublic void setSenderExternalID(@Nullable String senderExternalID)
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.
senderExternalID
- Identification number of the payerpublic void setSEPAMandateOrganizationalUnit1(@Nullable String sEPAMandateOrganizationalUnit1)
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit1
sEPAMandateOrganizationalUnit1
- SEPA Mandate: Internal Organizational Datapublic void setSEPAMandateOrganizationalUnit2(@Nullable String sEPAMandateOrganizationalUnit2)
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit2
sEPAMandateOrganizationalUnit2
- SEPA Mandate: Internal Organizational Datapublic void setSEPAMandateOrganizationalUnit3(@Nullable String sEPAMandateOrganizationalUnit3)
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit3
sEPAMandateOrganizationalUnit3
- SEPA Mandate: Internal Organizational Datapublic void setSEPAMandateOrganizationalUnit4(@Nullable String sEPAMandateOrganizationalUnit4)
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit4
sEPAMandateOrganizationalUnit4
- SEPA Mandate: Internal Organizational Datapublic void setSEPAMandateFirstUseDate(@Nullable LocalDateTime sEPAMandateFirstUseDate)
Original property name from the Odata EDM: SEPAMandateFirstUseDate
Date in the form YYYYMMDD (where Y = year, M = month, D = day)19920301
sEPAMandateFirstUseDate
- Date (YYYYMMDD)public void setSEPAMandateFirstUseObjTypeCode(@Nullable String sEPAMandateFirstUseObjTypeCode)
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
sEPAMandateFirstUseObjTypeCode
- Technical key of a business object in the Business Object Repository (BOR).public void setSEPAMandateFirstUsePaymentDoc(@Nullable String sEPAMandateFirstUsePaymentDoc)
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.
sEPAMandateFirstUsePaymentDoc
- Technical key of a business object in the Business Object Repository (BOR).public void setSEPAMandateLastUseDate(@Nullable LocalDateTime sEPAMandateLastUseDate)
Original property name from the Odata EDM: SEPAMandateLastUseDate
Date in the form YYYYMMDD (where Y = year, M = month, D = day)19920301
sEPAMandateLastUseDate
- Date (YYYYMMDD)public void setSEPAMandateLastUseObjTypeCode(@Nullable String sEPAMandateLastUseObjTypeCode)
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
sEPAMandateLastUseObjTypeCode
- Technical key of a business object in the Business Object Repository (BOR).public void setSEPAMandateLastUsePaymentDoc(@Nullable String sEPAMandateLastUsePaymentDoc)
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.
sEPAMandateLastUsePaymentDoc
- Technical key of a business object in the Business Object Repository (BOR).public void setSepaCreditorIdOrigin(@Nullable String sepaCreditorIdOrigin)
Original property name from the Odata EDM: SepaCreditorIdOrigin
sepaCreditorIdOrigin
- SEPA Mandate: Original Creditor ID of Mandatepublic void setOriginalSEPAMandate(@Nullable String originalSEPAMandate)
Original property name from the Odata EDM: OriginalSEPAMandate
originalSEPAMandate
- SEPA Mandate: Original Mandate of Mandatepublic void setVersion(@Nullable String version)
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)
version
- If you create a new version by changing fields for a SEPA mandate, then the previous (former) status
of 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).public void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser
- User name of program author.public void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on which the object was createdpublic void setCreationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
creationTime
- Time at which the object was createdprotected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<SEPAMandate>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<SEPAMandate>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SEPAMandate>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SEPAMandate>
@Nonnull public static <T> SEPAMandateField<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> SEPAMandateField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<SEPAMandate>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<SEPAMandate>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<SEPAMandate>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntity
getDefaultServicePath
in class VdmEntity<SEPAMandate>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SEPAMandate>
@Nonnull public List<SEPAMandateUsage> fetchSEPAMandateUsage() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SEPAMandateUsage> getSEPAMandateUsageOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property SEPAMandateUsage of a queried SEPAMandate is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SEPAMandateUsage>> getSEPAMandateUsageIfPresent()
If the navigation property for an entity SEPAMandate has not been resolved yet, this method will not
query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setSEPAMandateUsage(@Nonnull List<SEPAMandateUsage> value)
If the navigation property SEPAMandateUsage of a queried SEPAMandate is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of SEPAMandateUsage entities.public void addSEPAMandateUsage(SEPAMandateUsage... entity)
If the navigation property SEPAMandateUsage of a queried SEPAMandate is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of SEPAMandateUsage entities.@Nonnull public static SEPAMandate.SEPAMandateBuilder builder()
@Nullable public String getSEPAMandateApplication()
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.
@Nullable public String getCreditor()
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
@Nullable public String getSEPAMandate()
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.
@Nullable public String getSEPAPaymentType()
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.
@Nullable public String getSenderType()
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
@Nullable public String getSender()
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.
@Nullable public String getSenderLastName()
Original property name from the Odata EDM: SenderLastName
@Nullable public String getSenderFirstName()
Original property name from the Odata EDM: SenderFirstName
@Nullable public String getSenderStreetName()
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.
@Nullable public String getSenderHouseNumber()
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.
@Nullable public String getSenderPostalCode()
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.
@Nullable public String getSenderCityName()
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.
@Nullable public String getSenderCountry()
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.
@Nullable public String getSenderLanguage()
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.
@Nullable public String getSenderIBAN()
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
@Nullable public String getSenderBankSWIFTCode()
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.
@Nullable public String getAlternativePayerName()
Original property name from the Odata EDM: AlternativePayerName
If the mandate is used for collecting your own invoices, leave the field empty. .
@Nullable public String getRecipientType()
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
@Nullable public String getRecipient()
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.
@Nullable public String getRecipientName1()
Original property name from the Odata EDM: RecipientName1
@Nullable public String getRecipientName2()
Original property name from the Odata EDM: RecipientName2
@Nullable public String getRecipientStreetName()
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.
@Nullable public String getRecipientHouseNumber()
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.
@Nullable public String getRecipientPostalCode()
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.
@Nullable public String getRecipientCityName()
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.
@Nullable public String getRecipientCountry()
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.
@Nullable public String getSEPAMandateReferenceType()
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
@Nullable public String getSEPAMandateReference()
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.
@Nullable public String getSEPAMandateReferenceDesc()
Original property name from the Odata EDM: SEPAMandateReferenceDesc
@Nullable public LocalDateTime getValidityStartDate()
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).
@Nullable public LocalDateTime getValidityEndDate()
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).
@Nullable public String getSEPASignatureCityName()
Original property name from the Odata EDM: SEPASignatureCityName
@Nullable public LocalDateTime getSEPASignatureDate()
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
@Nullable public String getSEPAMandateStatus()
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.
@Nullable public String getAlternativePayer()
Original property name from the Odata EDM: AlternativePayer
If the mandate is used for collecting your own invoices, leave the field empty.
@Nullable public String getAlternativePayeeName()
Original property name from the Odata EDM: AlternativePayeeName
@Nullable public String getAlternativePayee()
Original property name from the Odata EDM: AlternativePayee
@Nullable public Boolean getSEPAMandateIsB2BMandate()
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.
@Nullable public String getSenderExternalID()
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.
@Nullable public String getSEPAMandateOrganizationalUnit1()
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit1
@Nullable public String getSEPAMandateOrganizationalUnit2()
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit2
@Nullable public String getSEPAMandateOrganizationalUnit3()
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit3
@Nullable public String getSEPAMandateOrganizationalUnit4()
Original property name from the Odata EDM: SEPAMandateOrganizationalUnit4
@Nullable public LocalDateTime getSEPAMandateFirstUseDate()
Original property name from the Odata EDM: SEPAMandateFirstUseDate
Date in the form YYYYMMDD (where Y = year, M = month, D = day)19920301
@Nullable public String getSEPAMandateFirstUseObjTypeCode()
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
@Nullable public String getSEPAMandateFirstUsePaymentDoc()
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.
@Nullable public LocalDateTime getSEPAMandateLastUseDate()
Original property name from the Odata EDM: SEPAMandateLastUseDate
Date in the form YYYYMMDD (where Y = year, M = month, D = day)19920301
@Nullable public String getSEPAMandateLastUseObjTypeCode()
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
@Nullable public String getSEPAMandateLastUsePaymentDoc()
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.
@Nullable public String getSepaCreditorIdOrigin()
Original property name from the Odata EDM: SepaCreditorIdOrigin
@Nullable public String getOriginalSEPAMandate()
Original property name from the Odata EDM: OriginalSEPAMandate
@Nullable public String getVersion()
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)
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public LocalTime getCreationTime()
Original property name from the Odata EDM: CreationTime
@Nonnull public String toString()
toString
in class VdmObject<SEPAMandate>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<SEPAMandate>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<SEPAMandate>
public int hashCode()
hashCode
in class VdmObject<SEPAMandate>
Copyright © 2021 SAP SE. All rights reserved.