Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-I18 (Application Component) Internationalization (I18N)⤷
SCP (Package) SAP Code Pages
Basic Data
| Data Element | RSCPUSEF1 |
| Short Description | Request subfunction: Use F1 memory |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RSTSX_ | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Use F1 |
| Medium | 20 | Use F1 memory |
| Long | 35 | Use F1 memory |
| Heading | 10 | Use F1 |
Documentation
Definition
Function selection for the case where a code page converter encounters a code page pair for which a mapping table also exists in the F1 memory.
This function selection defines right from the start, what the converter must do if such a situation occurs. The following values are possible:
'N' ' '
The CCC converter is used completely as normal. As well as 'N', a blank is also accepted to stay compatible with the old Boolean values. ('not F1')
'T' 'X'
If there is a mapping table in the F1 memory that is suitable, then it is used. If the F1 memory recommends that you copy data unconverted, this takes place. If the F1 memory reports incompatibility for the pair, then the actual CCC converter is used. For code page pairs, which is how they usually occur, this makes the result compatible with what the RFC would have done in versions 3.1 to 4.6. As well as 'T', the value 'X' is also accepted, to remain compatible with the old Boolean values. ('try')
'O'
If the F1 memory has a conversion table that is partially suitable, then it is used. If the F1 memory recommends that you copy the data unconverted, then this takes place. However, if the F1 memory reports an unresolvable incompatibility, or if it cannot process the pair at all, then the request is rejected and no converter object is generated. ('only')
'E'
If the F1 memory has a conversion table that is partially suitable, then it is used. If the F1 memory recommends that you copy the data unconverted, then this takes place. However, if the F1 memory reports an unresolvable incompatibility, or if it cannot process the pair at all, then the actual CCC converter is used. This selection corresponds to what RFC and TRANSLATE CODE PAGE did in Releases 3.1 to 4.6. ('enforce')
'C'
This selection is dependent on system settings and can correspond to 'T', 'N' or 'E'. ('customizable')
Use
Dependencies
Example
Some transactions in Release 4.5 and 4.6 relied on RFC allowing the Euro character 156, although it was not included in the ISO code pages. With this switch, you can use the new ABAP features to write programs that are compatible with the old behavior. (z.B. GUI_DOWNLOAD)
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in | 50A |
