SAP ABAP Data Element SEPA_REC_TYPE (SEPA Mandate: Recipient Type)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
CA-BK (Application Component) Bank
⤷
BF_SEPA (Package) Single Euro Payments Area (Mandate)
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_REC_TYPE |
| Short Description | SEPA Mandate: Recipient Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OJ_NAME | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | TOJTB |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | OBJ | |
| Default Component name | OBJTYPE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Recip.Type |
| Medium | 15 | Recipient Type |
| Long | 20 | Recipient Type |
| Heading | 20 | Recipient Type |
Documentation
Definition
Internal technical key of a business object in the Business Object Repository (BOR).
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.
Use
Dependencies
Example
Examples:
- BUS2032
- BUS6026
History
| Last changed by/on | SAP | 20080411 |
| SAP Release Created in | 700 |
