Mutually incovertible issue in unicode

hi
i am workin on a unicode project.In a certain set of programs i am gettin an error as mutually inconvertible.
eg. error
"XVBRK" and "ARC_BUFFER-SEGMENT" are not mutually convertible in a Unicode program.
here xvbrk is like vbrk and contains more than 100 fields and i hve 15 errors to deal of same kind.
so anyone can help me with any technique to do this.

at what line of code does this error occur. Are "XVBRK" and "ARC_BUFFER-SEGMENT" of the same type.

Similar Messages

Error -not mutually convertible in a Unicode program

Hi all,
          I have declare my internal table and workarea as below ...
TYPES: BEGIN OF t_mara,
        matnr type mara-matnr,
       END OF t_mara.
DATA : it_mara TYPE t_mara OCCURS 0 WITH HEADER LINE.
DATA :wa_mara like mara-matnr.
when iam loopimg my internal table into work area(like loop at it_mara into wa_mara ......) .. iam getting below error
A line of "IT_mara" and "wa_mara" are not mutually convertible in a Unicode program. Unicode program.
Can any one let me know what is the exact problem ?..
Thanks
MAHA

Hi Maha,
pls see the declaration as below..it is working..
TYPES: BEGIN OF t_mara,
matnr type mara-matnr,
END OF t_mara.
DATA : it_mara TYPE t_mara OCCURS 0 WITH HEADER LINE.
DATA :wa_mara like line of it_mara.
Keerthi.

ABAP program issues..Unicode program "ITAB" must have the same structure?

Dear Expert,
I coded below code in se38, but system give below error message, could please kindly advie issue reason? Thanks!!
Error message: A line of "ITAB" and "LINE" are not mutually convertible. In a Unicode program "ITAB" must have the same structure layout as "LINE" independent of the length of a . Unicode character. Unicode character.
REPORT ZTEST_HIHIHI.
Data: begin of line,
num type i,
sqr type i,
end of line,
itab type standard table of line with key table_line.
Do 5 times.
line-num = sy-index.
line-sqr = sy-index ** 2.
append line to itab.
enddo.
loop at itab into line.
write: / line-num, line-sqr.
endloop.
clear itab.

Hello Hoo Laa,
This is because the way you have defined LINE, it is a structure & not a data type. Hence you are facing the issue
You have to change the data declaration to:
itab LIKE STANDARD TABLE OF line WITH KEY table_line.
BR,
Suhas

Nametab issue during unicode conversion

There are some tables inconsistent durning Unicode conversion, is it possible to delete them?
Moderator message: not directly related to ABAP development, please have a look in the Netweaver forums, alway search for information before asking.
Edited by: Thomas Zloch on Dec 23, 2010 1:32 PM

Hi,
Reposting the question again, as earlier one was incomplete.
We are doing Unicode Conversion activity in one of our system. After running through UCCHECK transaction, we got around 80 programs in which most of them were resolved manually. When we are trying to edit one object, the error"Namespace /OSJ8C/' does not exists is displayd. Any help to resolve this issue will be highly appreciated .

Any known issues with Unicode apps in System 9 Analytic Services ?

We have installed System 9.2.0.2 Analytic Services on an AIX server. It was installed as a non-Unicode server. I am exploring enabling the server for Unicode, and then setting non-ASO apps to Unicode enabled. We don't need multi-lingual features, but we would like to be able to have calc scripts, report scripts, and load rules with names more than 8 characters long. Apparently, during the planning for upgrading to System 9, a consultant advised against setting Unicode on. But no specifics were given on why he advised against it. Is anyone aware of any downsides to Unicode enabled ? I know that ASO apps can't use it, but the server is supposed to support having some apps running in Unicode mode and others not. It's understood that if you have a Unicode app, and it needs to switch to ASO, that any long names would require name changes. The thing I'm wondering is why that consultant said that, so I wonder if anyone knows of issues. If no issues are known, than can anyone who is running Unicode mode in System 9.2 speak up and tell me that they are doing fine with no issues ?

We have installed System 9.2.0.2 Analytic Services on an AIX server. It was installed as a non-Unicode server. I am exploring enabling the server for Unicode, and then setting non-ASO apps to Unicode enabled. We don't need multi-lingual features, but we would like to be able to have calc scripts, report scripts, and load rules with names more than 8 characters long. Apparently, during the planning for upgrading to System 9, a consultant advised against setting Unicode on. But no specifics were given on why he advised against it. Is anyone aware of any downsides to Unicode enabled ? I know that ASO apps can't use it, but the server is supposed to support having some apps running in Unicode mode and others not. It's understood that if you have a Unicode app, and it needs to switch to ASO, that any long names would require name changes. The thing I'm wondering is why that consultant said that, so I wonder if anyone knows of issues. If no issues are known, than can anyone who is running Unicode mode in System 9.2 speak up and tell me that they are doing fine with no issues ?

Are not mutually convertible in a Unicode program

Hi guys,
I'm getting error: "LS_EDIDD-SDATA and LS_STRUCTURE are not mutually convertible in Unicode Program"
I have PRKST which is Amount field in LS_STRUCTURE, which causes this problem.
But if I change type of PRKST to CHAR15, then it doesn't give error.
But i want to use this field with type PRKST( CURR 11, decimal places 2).
Please help. Its urgent.
Thanks,
Mehul Lad
Moderator message - "Urgency" is not allowed in the forums. Read the RoE.
Message was edited by: Suhas Saha

Hi,
LCHR field is not a standalone field. It is always preceded by a field of type INT2 which has the length of the data stored in LCHR field.
So, in structure LS_EDIDD there should be a INT2 type field just before the field SDATA which tells the length of the actual value in SDATA. Suppose the field name is LEN.
So,
assign the value like this :
LS_STRUCTURE = LS_EDIDD-SDATA(LS_EDIDD-LEN).
Regards,
Ashish

Issue in Unicode Conversion

Hi,
We are doing Unicode Conversion activity in one of our system. After running through UCCHECK transaction, we got around 80 programs in which most of them were resolved manually.
kindly find the below screenshot when we are trying to edit one object, we are facing the issue. Any help will be highly appreciated .
Thanks,
Grace

Hi,
Reposting the question again, as earlier one was incomplete.
We are doing Unicode Conversion activity in one of our system. After running through UCCHECK transaction, we got around 80 programs in which most of them were resolved manually. When we are trying to edit one object, the error"Namespace /OSJ8C/' does not exists is displayd. Any help to resolve this issue will be highly appreciated .

Do varying issue in unicode programs(ECC6.0)

Hi,
I am facing the error "Could not specify the range automatically. This means you need a RANGE addition." for the following code.
DATA : W_STRAT_LANC1 LIKE T16FD-FRGCT, "stratégie de lancement 1 +DJA
         W_STRAT_LANC2 LIKE T16FD-FRGCT
DO 3 TIMES
     VARYING T16FS-FRGCX   FROM T16FS-FRGC1   NEXT T16FS-FRGC2 RANGE T16FS
     VARYING W_STRAT_LANCX FROM W_STRAT_LANC1 NEXT W_STRAT_LANC2.
Please send me a possible solution.
I have gone through many posts but this is a new issue.

Hi,
This is not a correct way of using the varying addition. Your fields should belong to the same structure...
something like:
TYPES: BEGIN OF ts_lanc,
         lanc1 TYPE frgct,
         lanc2 TYPE frgct,
        END OF ts_lanc.
DATA: w_strat_lancx TYPE t16fd-frgct,
      w_t16fs-frgcx TYPE t16fs-frgsx.
DATA: ws_t16fs TYPE t16fs,
      ws_lanc TYPE ts_lanc.
DO 3 TIMES
   VARYING w_t16fs-frgcx FROM ws_t16fs-frgc1 NEXT ws_t16fs-frgc2 RANGE ws_t16fs
   VARYING w_strat_lancx FROM ws_lanc-lanc1 NEXT ws_lanc-lanc2 RANGE ws_lanc.
ENDDO.
Kr,
Manu.

Help on error - not mutually convertible in a unicode program

I am trying to implement a badi - badi_matmas_ale_cr. I want to take contents of sdata to i_marc but getting this error ...any workaround for this. I thought of defining structure of marc with all char fields but that is almost 218 fields so thought if there is anyother way of doing this.
DATA : wa TYPE LINE OF edidd_tt,
         i_marc type line of MARC_UEB_TT .
LOOP AT t_idoc_data INTO wa.
    CASE wa-segnam.
      WHEN 'E1MARCM'.
        MOVE wa-sdata TO i_marc.
        IF i_marc-compl+0(1) NE '9'.
          DELETE t_idoc_data INDEX sy-tabix.
        ENDIF.
      ENDLOOP.

try this
call method cl_abap_container_utilities=>read_container_c
exporting
im_ container = wa-sdata
importing
ex_ value = imarc
exceptions
illegal_parameter_type = 1
others = 2.
Check Re: Table maintenance - change field contents of the already existing entri for reference.

Java JCo SAP XI RFC SAP R/3 6.C ... Unicode issue

Hello,
My scenario is very simple. I'd like to connect a Java program to a SAP R/3 (MDMP) for RFC calls (in both direction), using SAP XI (some of the RFC calls will redirected to some other systems). I use SAP JCo v2.1.8 and tried with Java 1.4.2_09 and Java 6.0.
It works well when the Java program is calling a function module, but when SAP R/3 is doing it, the returned texts looks like: S#A#P# #J#C#o# #v#2#.#1#.#8# #(#2#0#0#6#-#1#2#-#1#1#)# (the text should be SAP JCo v2.1.8).
It looks like an issue with Unicode. Although I didn't check the Unicode checkbox in the RFC sender adapter (the RFC receiver one doesn't offer the possibility to specify unicode or not).
Do anyone have a solution ? Is it a code in the Java program or something to set in SAP XI / SAP R/3 ?
Thanks in advance for your help.

This is a workaround solution. In the case of this prototype it is ok, but the final plan is to migrate a web based application. It was directly connected to one SAP R/3, but now we would like to connect it to SAP XI because a few RFC calls will be re-directed to some other systems, but the majority of them will we'll still be sent to the SAP R/3. We don't want to make development on this part for cost reason (and time). Plus on some text there are the "#" character that is legitimate.

Mutually convertible Unicode

When I change the next code (Adaptation unicode):
IF t004-sakln > 0.
*{ REPLACE &$&$&$&$ 1
* DESCRIBE FIELD ska1-bilkt LENGTH sy-fdpos.
 DESCRIBE FIELD ska1-bilkt LENGTH sy-fdpos IN CHARACTER MODE.
I obtain the next error sintaxis:
Can you help me, please?
"SKC1A-GSBER" and "X_FF_GSBER" are not mutually convertible in a Unicode program . . . . .
IF NOT ( repwaers IS INITIAL ).
 ctyp_waers = repwaers.
ELSE.
 ctyp_waers = skc1a-hwaer.
ENDIF.
IF fi_lc_ex = '2'.
* Extrakt an FI_LC, Geschäftsbereich austauschen
 SELECT SINGLE * FROM tgsb WHERE gsber = skc1a-gsber.
* IF SY-SUBRC = 0 AND TGSB-GSBER_KONS <> SPACE. "vhs134295
 IF sy-subrc = 0. "vhs134295
 skc1a-gsber = tgsb-gsber_kons.
 ELSE.
 IF NOT skc1a-gsber IS INITIAL. "vhs134295
* Fehler, Gsber auf HexFF setzen
 skc1a-gsber = x_ff_gsber.
 ENDIF. "vhs134295
 ENDIF.
ENDIF.
Cordial greetings.

Hi,
under Unicode you can't easely assign values from one variable to another with different datatype.
skc1a-gsber is char4 and x_ff_gsber seams to be type x?
Under Unicode there are strict rules. Instead of x = y you can use field-symbols.
This coding may help you:
DATA: z_gsber TYPE skc1a-gsber,
 x_ff_gsber TYPE x.
FIELD-SYMBOLS: <f_gsber> TYPE skc1a-gsber,
 <f_ff_gsber> TYPE x.
ASSIGN z_gsber TO <f_gsber>.
ASSIGN x_ff_gsber TO <f_ff_gsber>.
<f_gsber> = <f_ff_gsber>.
The variable z_gsber has now the same value as x_ff_gsber.

File constructor and unicode filename issue

I have issues with unicode filename.
I need to create a File object from unicode file name "Юга.mp3" in order to use it in the code.
File in=new File("Юга.mp3")
AudioFile f = AudioFileIO.read(in);
Tag tag = f.getTag();
Anybody knows how to deal with a file or directory that is named using Unicode characters?

1) Have you tried just reading the file as a file using a FileInputStream?
2) What operating system?
3) What Java version?
4) What are the \uxxxx values of some of the problem characters?
Edit: I have just run        String filename = System.getProperty("user.home") + "/\u1070\u1075\u1072.mp3";
       File file = new File(filename);
       OutputStream os = new FileOutputStream(file);
       os.write("Hello World".getBytes("utf-8"));
       os.close();
       DataInputStream dis = new DataInputStream(new FileInputStream(file));
       byte[] buffer = new byte[(int)file.length()];
       dis.readFully(buffer);
       dis.close();
       System.out.println(new String(buffer,"utf-8"));on Unbuntu 7.10 using JRE/JDK1.6.0_3
without any problems other than not being able to see the \u1070\u1075\u1072 in my console because I don't have fonts installed for displaying them.
Edited by: sabre150 on Dec 28, 2007 8:52 AM
Further edit: It also runs on Windows XP using 1.6.0_03 .
Edited by: sabre150 on Dec 28, 2007 9:00 AM
I don't think the file is located where you think it is!
Edited by: sabre150 on Dec 28, 2007 9:02 AM

Looping issue in Smartform

Hi All..
I am working on a smartform.
While activating the form, i came across a error called "A line of I_ITEMS and WA_ITEMS is not mutually convertible. In Unicode program, I_ITEMS must have same structure layout".
But in program, i have defined both objects as follows..
Data: i_items TYPE STANDARD TABLE of ty_items.
Data: wa_items TYPE ty_items.
What to do now..???
How to resolve this issue..????
Please Help me out....
Regards
Pavan

Thanks to everyone here...
Special Thanks to Jayanthi...
I have changed the I_ITEMS's structure in Form Interfaces of the form.
Now its working fine...
Regards
Pavan

How to assign string to structure in unicode system R/3 4.7 ?

Hi All,
We are upgrading system from non-unicode to unicode.
While passing a string to a structure ( MOVE RECEIVERS-RECEIVER TO RECEIVER_OBJECT, where
RECEIVERS_RECEIVER = string
RECEIVER_OBJECT = structure )
following error is thrown :
"RECEIVER_OBJECT" and "RECEIVERS-RECEIVER" are not mutually convertible in a unicode program.
To resolve this error, i hv used :
CALL METHOD CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
EXPORTING
IM_VALUE = RECEIVERS-RECEIVER
IMPORTING
EX_CONTAINER = RECEIVER_OBJECT
EXCEPTIONS
ILLEGAL_PARAMETER_TYPE = 1
others = 2
While activating the code, following error message is thrown :
"RECEIVER_OBJECT" is not type-compatible with formal parameter "EX_CONTAINER".
Please help me out to solve this issue ..
I need to know what I am missing here to make my code correct.
Thanks in advance.
Priya

Hi All,
My issue is resolved by using following class and method : CL_ABAP_CONTAINER_UTILITIES=> READ_CONTAINER_C and passing 'string' in export parameter and structure in 'import' parameter.
Cheers !!
Priya

Could you pls give the details about the Unicode conversion during Upgrade

Hi,
Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
Waiting for quick response
Best Regards,
Padhy

Hi,
These are the few points i gathered during my upgradation project.
Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
So it is advised to keep a back-up of the existing system.
Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
Version Upgrade involves the following Steps.
Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
First copy the entire E4B system into the E1B System which is created for Version 4.7.
Apply the Version 4.7 CD provided by SAP over the E1B System.
Now check whether all the functionalities that was in E4B system works fine with E1B system also.
Thus the Version Upgrade involves two steps.
1. SAP Upgradation with the help of the CD
2. Manual Upgradation.
1. SAP Upgradation with the help of the CD
This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
2. Manual Upgradation.
This Manual Upgradation involves
2.1 Upgradation of Standard Objects
2.1.1 SPAU Objects
2.1.2 SPDD Objects
2.2 Upgradation of Custom Objects.
Upgradation of Custom Objects can be placed under the following three categories.
Unicode Compliance
Retrofit
Upgrade
Please Find below some of the common Unicode Errors and their solutions
1. Error:
In case of Translate Error; Dangerous use of Translate in Multilingual system.
Correction:
To correct the Error occurring on TRANSLATE statement use this additional statement before the Translate statement.
SET LOCALE LANGUAGE sy-langu.
This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is sy-langu, i.e. the log on language of the user.
2. Error:
In case of Open Dataset Error; Encoding Addition must be included.
Correction:
This Error occurs only when the MODE is TEXT.
To correct the Error occurring on OPEN DATASET statement use this statement instead.
OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
Where: dataset_name NAME OF THE DATASET.
Access INPUT or OUTPUT or APPENDING or UPDATE.
DEFAULT - Corresponds to UTF-8 in UNICODE systems &
NON_UNICODE in NON-UNICODE systems.
3. Error:
In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; Function module UPLOAD is flagged as obsolete.
Correction:
The FM GUI_DOWNLOAD/UPLOAD is used.
The variations to be made in the parameters of the FM:
1. Filename It must be of STRING type.
2. Filetype DAT is not used any longer, instead ASC is used.
3. Field Separator The default value SPACE is used, incase for a TAB separated file X can be used.
4. Error:
In case of CURRENCY/UNIT Addition Error; Use addition CURRENCY/UNIT when outputting.
Correction:
The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
To correct this error follow the following method:
WRITE: /3 'TOTAL',' ', TOTAL.
WRITE: /3 TOTAL, , TOTAL CURRENCY 2. --- Where 2is the Currency Key for Getting 2 decimal places.
5. Error:
In case of TYPE X Error; Variable must be of C, N, D, T or STRING type.
Correction:
We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
So the method to be followed is:-
1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
2. Declare the variable as Type C, and use the method UCCP(XXXX) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute HORIZONTAL_TAB of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
E.g.:
i) *DATA: TAB TYPE X VALUE 09, Tab character
CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
ii) * DATA: CHAR TYPE X VALUE 160.
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA CHAR TYPE C.
CHAR = CL_ABAP_CONV_IN_CE=>UCCP(00AO).
(Here 00A0 is the Hexadecimal equivalent of the decimal 160).
3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
E.g.:
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA : LF(2) TYPE X VALUE 'F5CD'.
DATA : BEGIN OF LF,
A1 TYPE C,
A2 TYPE C,
END OF LF.
LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
6. Error:
In case of the Character -Error; The Character -cant appear in names in Unicode Programs.
Correction:
The Character -(Hyphen) appearing in Variable names is replaced by the character _ (Under Score) for Unicode/Upgrade Compliance.
E.g.:
*wk-belnr LIKE bkpf-belnr,
*wk-xblnr LIKE bkpf-xblnr,
*wk-date LIKE sy-datum,
*wk-wrbtr LIKE bseg-wrbtr,
*wk-name1 LIKE lfa1-name1,
*wk-voucher(8) TYPE c.
wk_belnr LIKE bkpf-belnr,
wk_xblnr LIKE bkpf-xblnr,
wk_date LIKE sy-datum,
wk_wrbtr LIKE bseg-wrbtr,
wk_name1 LIKE lfa1-name1,
wk_voucher(8) TYPE c.
7. Error:
In case of The SUBMIT-TO-SAP-SPOOL Error; you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition.
Correction:
1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
2. Call the FM GET_PRINT_PARAMETERS:
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
3. Use the SUBMIT-TO-SAP-SPOOL statement.
E.g.:
 submit zrppt500
 using selection-set 'AUTO3'
 with res_no eq lo_rsnum
 with sreserv in preserv
 to sap-spool destination p_dest
 immediately 'X'. "print immediate
DATA: print_parameters type pri_params,
archive_parameters type arc_params,
valid_flag(1) type c.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
Submit zrppt500
Using selection-set 'AUTO3'
With res_no eq lo_rsnum
with sreserv in preserv
to sap-spool
SPOOL PARAMETERS PRINT_PARAMETERS
ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
WITHOUT SPOOL DYNPRO.
8. Error:
In case of Message Error; Number of WITH fields and number of Place Holders are not same .
Correction:
Split the statement after WITH into the same number as the place holder for that Message ID.
E.g.:
1. * MESSAGE E045.
MESSAGE E045 WITH '' ''.
2. in program ZIPI0801
 Start of change for ECC6
 message e398(00) with 'Could not find access sequence'
 'for condition type:'
 p_ptype.
message e398(00) with 'Could not find '
'access sequence'
'for condition type:'
p_ptype.
 End of change made for ECC6
9. Error:
In case of Move between 2 different Structures; The structures are not mutually convertible in a Unicode program.
Correction:
Make both the Data Types compatible and then assign the contents.
E.g.:
The statement move retainage_text to temp_text. Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
10. Error:
In case of no description found; add a GUI title.
Correction:
In this type of error gui title is generally missing so add a GUI title to the module pool.
11. Error:
In case of writing internal or transparent table
Correction:
Write individual fields.
E.g.:
WRITE: / EXT. --> EXT should be a character type field
WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
12. Error:
In case of combination reference table/field S541-UMMENGE does not exist
Correction:
Was due to error in reference table S541. TABLE S541 has errors
1)Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)
2)Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)
Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
And that of ZMKCODE (from ZACCODE to ATTR8)
13. Error:
In case of KEY does not exist
Correction:
The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
14. Error:
Incase of WRITE statement, Literals that take more than one line is not permitted in Unicode systems.
Correction: To correct this error, we need to align the spaces accordingly so that the statement doesnt go beyond the line.
15. Error:
Incase of Data statement, The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect..
Correction: To correct this error, instead of like in the Data statement, use type.
16. Error:
Incase of DESCRIBE statement, DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.
Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
CHARACTER MODE is added when the data object is of flat/ character type.
BYTE MODE is added when the data object is a deep structure.
Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
LENGTH clen IN CHARACTER MODE.
Where blen and clen must be of type I.
17. Error:
Incase of DO-LOOP Error, In Do loop range addition needed
Correction:
An internal tables is declared and the two fields (VARYING field and NEXT field) were
Included inside the internal table
E.g.: In program SAPMZP02
DO 11 TIMES
 VARYING STATION_STATE FROM STATION1 NEXT STATION2. ECC6
CASE SYST-INDEX.
WHEN 1
STATION_STATE = STATION1.
WHEN 2
STATION_STATE = STATION2.
WHEN 3
STATION_STATE = STATION3.
WHEN 4
STATION_STATE = STATION4.
WHEN 5
STATION_STATE = STATION5.
WHEN 6
STATION_STATE = STATION6.
WHEN 7
STATION_STATE = STATION7.
WHEN 8
STATION_STATE = STATION8.
WHEN 9
STATION_STATE = STATION9.
WHEN 10
STATION_STATE = STATION10.
WHEN 11
STATION_STATE = STATION11.
18. Error:
Incase of the parameter QUEUE-ID Error, QUEUE-ID is neither a parameter nor a select option in program rsbdcbtc.
Correction:
The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
E.g.: In program Z_CARRIER_EDI_INTERFACE
 submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
 The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
19. Error:
Incase of EPC Error, Field symbol <TOT_FLD> is not assigned to a field .
Correction:
This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
The OS Note - 1036943 needs to be applied.
Error:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
Correct:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Error:
Constants : c_tab type x value '09' .
Correct:
Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
Error:
Data : begin of output_options occurs 0 . Include structure ssfcompop.
Data : end of output_options .
Correct:
Data : output_options type standard table of ssfcompop with header line .
Error:
PARAMETERS : NAST TYPE NAST .
Correct:
PARAMETERS : NAST TYPE NAST NO-DISPLAY .
Replace WS_DOWNLOAD and WS_UPLOAD by
GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
Issue:
Moving data from one structure to another structure if those two structures are not compatible
Solution:
we should use move-corresponding or field by filed we need to move it.
If database structures are different in 4.6c and ECC6.0,
Then we should go with append structure concept.
While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
Also Check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
Reward points if helpful.
Regards,
Ramya

Mutually incovertible issue in unicode

Similar Messages

Maybe you are looking for