Hierarchy
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSDS (Package) Apollo DataSource
Basic Data
Data Element | RSDSWSFIXOBJNM |
Short Description | Fixed Service Name |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 15 | |
Decimal Places | 0 | |
Output Length | 15 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Fxd Name |
Medium | 15 | Fixed Serv.Name |
Long | 20 | Fixed Service Name |
Heading | 30 | Fixed Service Name |
Documentation
Definition
In this field, you enter a fixed service name. The fixed service name is used to generate the following objects:
- Function group
- Function module
- Web service
- Virtual interface
The whole name is preceded by a generation prefix and is determined as follows:
- Generation namespace that corresponds to DataSource name (example: DataSource name ABC_TEST, generation namespace '/BIC/')
- Subprefix 'CF'
- User-defined fixed service name: Minimum length of 5 characters; maximum length of 15 characters
This name is retained when the DataSource is transported to the target system.
If you do not specify a fixed service name, the system uses an object name that is determined generically. This name may change in the target system because object names are also determined generically in the target system.
Use
If you need to predefine the name that is used for a function module or Web service in the target system of the transport, enter a fixed service name.
This is useful, for example, if names are used in the programming in an application.
Note that the system generates a generation prefix that precedes the fixed service name. This is dependent on the generation namespace for the name of the DataSource and cannot be changed in the target system of the transport.
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 710 |