SAP ABAP Data Element ISM_RFCDEST_POST (IS-M: RFC Destination for Client Containing Postal Data)
Hierarchy
☛
IS-M (Software Component) SAP MEDIA
⤷ IS-M (Application Component) SAP Media
⤷ JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
⤷ IS-M (Application Component) SAP Media
⤷ JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
Basic Data
Data Element | ISM_RFCDEST_POST |
Short Description | IS-M: RFC Destination for Client Containing Postal Data |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RFCDEST | |
Data Type | CHAR | Character String |
Length | 32 | |
Decimal Places | 0 | |
Output Length | 32 | |
Value Table | RFCDES |
Further Characteristics
Search Help: Name | F4_RFCDES3 | |
Search Help: Parameters | RFCDEST | |
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 | PostDest |
Medium | 16 | Dest. for Post |
Long | 21 | Dest. for Postal Data |
Heading | 32 | Destination for Postal Data |
Documentation
Definition
RFC destination for postal client
Use
The postal data is indexed for the search engine service (for example TREX) within the postal client. An RFC destination is required for the postal client so that these indexes can be accessed for search purposes (for example, in the F4 help).
If the postal data is in the current month, a destination is not required.
Dependencies
You can only search the postal data using a search engine when the indexes are accessible from the client in which the search is accessed.
History
Last changed by/on | SAP | 20060208 |
SAP Release Created in | 600 |