Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-BK (Application Component) Bank⤷
BF_SEPA (Package) Single Euro Payments Area (Mandate)
Basic Data
| Data Element | SEPA_MVERS |
| Short Description | SEPA Mandate: Version of Mandate (0 = Current Version) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM04 | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | SEPA_MANDATE_VERSION | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Version |
| Medium | 15 | Mandate Version |
| Long | 20 | Mandate Version |
| Heading | 30 | Mandate Version |
Documentation
Definition
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).
Use
Dependencies
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.
Example
Mandate is created with version 0 and location = 'A'. If you make a change so the location = 'B, then:
Version Location
0 B (current version)
1 A (first version)
If you make a further change of location of 'B' to location = 'C', then:
Version Location
0 C (current version)
1 A (first version)
2 B (second version)
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
