7/21/2019 0000970892

http://slidepdf.com/reader/full/0000970892 1/2

SAP Note 

Header Data

Symptom 

You create payment mediums with a RFFO* report in a Unicode system and you want to control thecodepage of the file on the application server during the generation. By implementing this note, youhave the option to control this using the parameters P_CODEP (codepage number) and P_UNICO(indicator: X or empty).If the parameters are not filled by default, the file is created in a non-Unicode codepage so thatyou do not have to perform another conversion. The used codepage depends on the logon language. Ifthis codepage does not correspond to the requirements, enter the codepage directly with the P_CODEPreport parameter (the attachment contains a list of the non-Unicode codepages).If you want to create the file in the Unicode codepage (codepage 4102 or 4103), set the P_UNICO

parameter to 'X'. However, you must then convert the file to a non-Unicode page, either externallyor by using transaction FDTA.

Maintaining the parameters P_CODEP and P_UNICO:The parameters P_CODEP and P_UNICO are not directly visible on the report, you can determine thevalues using the TVARVC table. In the report variant for the payment medium report, enter a tablevariant from the TVARVC table for the parameters.To do so, proceed as follows:1. Call transaction STVARV, create one or two new parameters with relevant names (for example,RFFO_CODEPAGE, RFFO_UNICODE) and assign the corresponding values.

2. Use transaction SE38 to access the variant maintenance in change mode for the payment mediumreport and choose 'Attributes'.In Release 4.7 or higher releases: On the next screen, expand the display (shift+F4) to display theselection criteria that you cannot see. For the parameters P_CODEP and P_UNICO, select the'Selection Variable' column and choose 'Selection Variables'. Assign the corresponding tablevariants from the TVARVC table to the variables P_CODEP or P_UNICO.

In Release 4.7 or higher releases: In the rows of the parameters P_UNICO and P_CODEP, select the 'T'category (table variable from TVARVC) in the 'Selection Variable' column and select the name of thevariable from the TVARVC table in the 'Variable Name' column.

Save the variant. During the runtime of the program, the corresponding values from the TVARVC table('X' for P_UNICO or, for example, '1100' for P_CODEP) are used in the program.

Two examples:Example 1: You want to create a file in Unicode codepage (4102/4103)The P_UNICO parameter is set, the codepage is left empty:

Report parameter Table variable Value in TVARVC-------------------------------------------------------------P_UNICO RFFO_UNICODE XP_CODEP RFFO_CODEPAGE

Example 2: You want to create a file in codepage 1401The code page is set, P_UNICO is left empty:

Report parameter Table variable Value in TVARVC--------------------------------------------------------------P_UNICO RFFO_UNICODEP_CODEP RFFO_CODEPAGE 1401

If neither parameter is assigned, the file that corresponds to the logon language is written in thecodepage (see attachment).

Download using transaction FDTAIf you want to download a file that you already created in the correct target code page with thisnote using transaction FDTA, note that the DCP user parameter must have the value NONE, so thatthere is no further conversion. If the parameter is not set, the file is converted to code page1100. (For more information about the DCP parameter, see Note 716454).

Other Terms 

Unicode is active in the system and you do not use the Payment Medium Workbench.The file is not saved in the temporary sequential file but on the application server.

Solution 

970892 - Unicode: Specifying the codepage in RFFO* programs 

Version  5 Validity: 09.01.2007 - active Language  English

Released On  10.01.2007 08:08:39

Release Status Released for Customer

Component  FI-BL-PT-FO payment forms

Priority  Correction with medium priorityCategory  Program error

7/21/2019 0000970892

http://slidepdf.com/reader/full/0000970892 2/2

 

Implement the source code corrections as described above.

Validity

Correction Instructions

Support Packages & Patches

References

This document refers to:

SAP Notes 

This document is referenced by:

SAP Notes (2) 

Attachments

Software Component From Rel. To Rel. And Subsequent

SAP_APPL  470  470  

500  500  

600  600  

Correction Instructions

Software Component Valid from Valid to Number

SAP_APPL  470  600  817939

 SAP_APPL  470  600  817946

Support Packages

Software Component Release Support Package

SAP_APPL  470  SAPKH47028

 500  SAPKH50016

 600  SAPKH60008

1319517 Unicode Collection Note 

1319517 Unicode Collection Note 

1365764 Codepage of DME file 

File Name File Size (KB) Mime Type

codepage_list.PPT  155  application/vnd.ms-powerpoint