sap note dmee

3
02.01.2013 Page 1 of 3 SAP Note 970892 - Unicode: Specifying the codepage in RFFO* programs Note Language: English Version: 5 Validity: Valid Since 09.01.2007 Summary Symptom You create payment mediums with a RFFO* report in a Unicode system and you want to control the codepage of the file on the application server during the generation. By implementing this note, you have 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 that you do not have to perform another conversion. The used codepage depends on the logon language. If this codepage does not correspond to the requirements, enter the codepage directly with the P_CODEP report 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 externally or 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 the values using the TVARVC table. In the report variant for the payment medium report, enter a table variant 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 medium report and choose 'Attributes'. In Release 4.7 or higher releases: On the next screen, expand the display (shift+F4) to display the selection 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 table variants 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 the variable 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 X P_CODEP RFFO_CODEPAGE Example 2: You want to create a file in codepage 1401

Upload: gayet-bir

Post on 16-Apr-2015

148 views

Category:

Documents


16 download

TRANSCRIPT

Page 1: SAP Note DMEE

02.01.2013 Page 1 of 3

SAP Note 970892 - Unicode: Specifying the codepage inRFFO* programs

Note Language: English Version: 5 Validity: Valid Since 09.01.2007

Summary

SymptomYou create payment mediums with a RFFO* report in a Unicode system and youwant to control the codepage of the file on the application server duringthe generation. By implementing this note, you have the option to controlthis 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 anon-Unicode codepage so that you do not have to perform another conversion.The used codepage depends on the logon language. If this codepage does notcorrespond to the requirements, enter the codepage directly with theP_CODEP report parameter (the attachment contains a list of the non-Unicodecodepages).If you want to create the file in the Unicode codepage (codepage 4102 or4103), set the P_UNICO parameter to 'X'. However, you must then convert thefile to a non-Unicode page, either externally or 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 the values using the TVARVC table. In the report variantfor the payment medium report, enter a table variant from the TVARVC tablefor the parameters.To do so, proceed as follows:1. Call transaction STVARV, create one or two new parameters with relevantnames (for example, RFFO_CODEPAGE, RFFO_UNICODE) and assign thecorresponding values.

2. Use transaction SE38 to access the variant maintenance in change modefor the payment medium report and choose 'Attributes'.In Release 4.7 or higher releases: On the next screen, expand the display(shift+F4) to display the selection criteria that you cannot see. For theparameters P_CODEP and P_UNICO, select the 'Selection Variable' column andchoose 'Selection Variables'. Assign the corresponding table variants fromthe TVARVC table to the variables P_CODEP or P_UNICO.In Release 4.7 or higher releases: In the rows of the parameters P_UNICOand P_CODEP, select the 'T' category (table variable from TVARVC) in the'Selection Variable' column and select the name of the variable from theTVARVC table in the 'Variable Name' column.

Save the variant. During the runtime of the program, the correspondingvalues from the TVARVC table ('X' for P_UNICO or, for example, '1100' forP_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 1401

Page 2: SAP Note DMEE

02.01.2013 Page 2 of 3

SAP Note 970892 - Unicode: Specifying the codepage inRFFO* programs

The 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 logonlanguage is written in the codepage (see attachment).

Download using transaction FDTAIf you want to download a file that you already created in the correcttarget code page with this note using transaction FDTA, note that the DCPuser parameter must have the value NONE, so that there is no furtherconversion. 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

Reason and PrerequisitesUnicode is active in the system and you do not use the Payment MediumWorkbench.The file is not saved in the temporary sequential file but on theapplication server.

SolutionImplement the source code corrections as described above.

Header Data

Release Status: Released for CustomerReleased on: 10.01.2007 08:08:39Master Language: GermanPriority: Correction with medium priorityCategory: Program errorPrimary Component: FI-BL-PT-FO payment forms

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 470 470 470

SAP_APPL 500 500 500

SAP_APPL 600 600 600

Support Packages

Page 3: SAP Note DMEE

02.01.2013 Page 3 of 3

SAP Note 970892 - Unicode: Specifying the codepage inRFFO* programs

Support Packages Release Package Name

SAP_APPL 470 SAPKH47028

SAP_APPL 500 SAPKH50016

SAP_APPL 600 SAPKH60008

Related Notes

Number Short Text

1319517 Unicode Collection Note

Attachments

FileType

File Name Language Size

PPT codepage_list.PPT E 155 KB

Correction Instructions

CorrectionInstructions

Validfrom

Validto

SoftwareComponent

Type*)

ReferenceCorrection

LastChanged

817939 470 600 SAP_APPL C P6BK233837 09.08.200609:51:21

817946 470 600 SAP_APPL C P6BK233837 09.08.200609:54:31

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work