Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules⤷
SFDT_CORE (Package) BRFplus: Core
Basic Data
| Data Element | FDT_APPLICATION_NAME |
| Short Description | BRFplus Application name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FDT_NAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table |
Further Characteristics
| Search Help: Name | FDT_SHLP_APPLICATION_NAME | |
| Search Help: Parameters | APPLICATION_NAME | |
| Parameter ID | FDT_AP_NAME | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | BRF+ Appl |
| Medium | 20 | BRFplus Application |
| Long | 30 | BRFplus Application Name |
| Heading | 30 | BRFplus Application Name |
Documentation
Definition
Technical name of a BRFplus application.
Use
You use this field to define the name of a BRFplus application from a technical perspective. You may want to use parts of that name as a common prefix for other objects in this application to indicate that all these objects belong to the same domain and serve a common purpose. Application names must be uniqe for a client in a customer system. In a non-customer system, they must be unique system-wide.
This field is not meant for a descriptive text in natural language. BRFplus offers dedicated fields for maintaining descriptive texts.
Note: Although the application name is technical in nature, it is not relevant for identifying an application from a technical perspective. To identify an application, use its ID property.
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 720 |
