LSMW - Unicode

Hello Experts!
I have issue.
I need to upload customer master record. Of 30 fields, three needs to be uploaded in Chinese language. I have installed Unicode for notepad and I can see the Chineese characters in my source file. But when I read data from lsmw, it comes ?????? where ever chinese characters are there.
Could any of you have work around for this.
Regards,
Aravind

Hi Lakshmipati,
Thanks for the response.
I did till the end for one record. All 27 fields are uploaded except those three fields which comes as ?????. I tried alternatives like changing the logon pad to chinese, reading ANSI file, reading Unicode file, all these throws new problems.
There should be a way to upload Unicode file to SAP, else I need to catch hold of ABAPer and Basis guys to help me out which is tough to do.
Looking forward for any solution.
Regards,
Aravind

Similar Messages

Error in uploading master through LSMW

Hi,
We are uploading customer master through LSMW with flat file in 10 th step (Display Read Data) we are getting error
that - "Data record too long to be imported (0 or >5000)"
we checked length of file also everything is perfect.
So How to resolve this?
Regards,
Akshay

Hello Akshay
Not specialist in this area but want to help you.
1) Review OSS notes:
1066952 - Working with legacy data files in LSMW (Unicode, BOM, FTP)
795072 - LSMW: Error in the display of the READ or CONV file
2) Debug program /SAPDMC/SAP_LSMW_VIEW_READDATA - with breakpoint @ Line # 185. I guess something is going wrong during length to Integer conversion whatever it means.
Error Message: /SAPDMC/LSMW 108.
Good luck.

LSMW: Codepage conversion error with a Unicode data file

Hi all,
I am currently developing a LSMW upload program which has to use a Unicode data file. The underlying system/target system is NOT a Unicode system. The data file also contains non-Latin2 characters.
In the step "Specify Files", I have specified my Unicode data file and specified the codepage type "4110 - Unicode UTF-8".
In the step "Read Data", then I get the runtime error "CONVT_CODEPAGE", exception "CX_SY_CONVERSION_CODEPAGE".
I would expect that all non-Unicode characters are automatically transformed to "#", but the conversion progam breaks. The character transformation to "#" would be fine.
I am really wondering why, at first, I am able to specify the Unicode codepage type, but then, the file cannot be converted correctly.
What do I make wrong, what can I do to avoid the error?
Thanks a lot in advance for helping me out...
Regards,
Klaus

Hello,
You need convert the file with the format UTF-8. In notepad you can choose this option.
Regards,
Oscar.

Unicode error in LSMW IDOC method

Hi Experts,
Iam using IDOC method to create material master. I am uploading the material master views seperately. When I convert the file and process it in LSMW, system gives me the message, the converted file can not be processed. The reason system display for the same is the idoc table passes the value EDI_DC40U instead of EDI_DC40.
But this is happening only for a single file and this is not a uni code file. I checked the port also. No where its flagged as uni code system.
Please help me
Regards
Prathib

Hi Sushanth
To use IDOC method.
You should create Partner profile.
Pls create the same using WE20 transaction.
After creating the same, you need to assign them in LSMW
You can assign the same using LSMW->SETTINGS->IDOC INBOUND PROCESSING
Pls let me know, if you need further help on the same
Regards
Madhan Doraikannan

Non English characters conversion issue in LSMW BAPI Inbound IDOCs

Hi Experts,
We have some fields in customer master LSMW data load program which can
contain non-English characters. We are facing issues in LSMW BAPI
method with non-English characters Conversion. LMSW steps read and
conversion are showing the non-English characters properly with out any
issue. While creating inbound IDOCs most of the non-English characters
replaced with '#' and its causing issues in creating customer master data in
system. In our scenario customer data with non-English characters in
the first name, last name and address details. Any specific setting
needs to be done from our side? Please suggest me to resolve this issue.
Thanks
Rajesh Yadla

If your language is a unicode tehn you need to change the options like IN SAP you need to change it to unicode in the initial screen Customize local layout(ALT F12) options 118 --> Encoding ....

LSMW - Upgrade Technical 4.7 to ECC 6.0

Hi All,
I am studying / researching ways to optimize the migration process of master data in the case of scenario of SAP version.
Anybody have any experience to share about the use of a scenario of LSMW upgrade of version? Or, hints to optimize the scenario.
Thanks
Regard
Rafael Aires

There is no impact, the projects can still be used if you don't migrate to Unicode at the same time.
Markus

Urgent: Error in magrating assets by LSMW

When I use LSMW - convert data, the system end up a ABAP dump. What does it mean?
Runtime Errors         UC_OBJECTS_NOT_CONVERTIBLE
Date and Time          2008.05.23 10:28:56
Short text
     Data objects in Unicode programs cannot be converted.
发生了什么?
     Error in the ABAP Application Program
     The current ABAP program "/1CADMC/SAP_LSMW_CONV_00000012" had to be terminated
      because it has
     come across a statement that unfortunately cannot be executed.
错误分析
     The statement
        "MOVE src TO dst"
     requires that the operands "dst" and "src" are convertible.
     Since this statement is in a Unicode program, the special conversion
     rules for Unicode programs apply.
     In this case, these rules were violated.
Trigger Location of Runtime Error:
     Program Name                            /1CADMC/SAP_LSMW_CONV_00000012
     Include                                 /SAPDMC/SAP_LSMW_CONV_FORMS
     Row                                     1,080
     Module type                             (FORM)
     Module Name                             TRANSFER_RECORD
CLEAR:
    g_cnt_idocs_package,
    gt_pack_edi_dc40[],
    gt_pack_edi_dd40[].
ENDFORM.                    "TRANSFER_IDOCS
      FORM TRANSFER_RECORD
FORM transfer_record.
FIELD-SYMBOLS:
    <l_record>,
    <l_prev_record>.
DATA:
    l_prev_record TYPE tumls_segment.
DATA:
    l_len_trgstr TYPE i.
IF g_skip_record = no AND
     g_skip_transaction = no.
    ASSIGN (g_record) TO <l_record>.
    CASE g_objecttype.
      WHEN '01' OR '02'.
        gt_buffer-record = g_record.
        gt_buffer-data = <l_record>.
        APPEND gt_buffer.
      WHEN '03' OR '04'.
        IF g_record = 'EDI_DC40'.
          IF p_trfcpt = yes.
            gt_curr_edi_dc40 = <l_record>.
            APPEND gt_curr_edi_dc40.
          ELSE.
            gt_buffer-record = g_record.
            gt_buffer-data = <l_record>.
            APPEND gt_buffer.
          ENDIF.
        ELSE.
          CLEAR edi_dd40.
          edi_dd40-segnam = g_edidd_segnam.
          edi_dd40-mandt = edi_dc40-mandt.
          edi_dd40-docnum = edi_dc40-docnum.
          ADD 1 TO g_segnum.
          edi_dd40-segnum = g_segnum.
          edi_dd40-hlevel = g_edidd_hlevel.

hi..
I too faced the problem..
as its regarding the date and time.. my mistake was...
while declaring the fields I have declared the length of the field for date as length 8( as given in the table) but when I am uploading the flat file the length was 10( including the separator . or / or - what ever it might be) so it was throwing the dump. So I have declared the date as char and length as 10 ( else u can change the format for that date field by removing the seperators in the flat file). Similar might be the case for u also.
reward if found helpful

LSMW upload of Thai characters uploaded incorrectly as '#####'

Hello,
Im using LSMW to upload data in Thai language. However the Thai characters are uploaded as ####.
I uploaded using LSMW to upload customer master as follows
-     file uploaded is a tab delimitted (.txt) unicode file
-     SAP gui character set is set to Thai TIS620
-     I logon in language EN using codepage 1100
-     SAP release is 620 for SAP ABAP & BASIS and release 470 for SAP APPL
Logging onto SAP using codepage 8600(Thai codepage) did not make any difference.
Doing all of the above with SAP gui character set Simplified Chinese GB2312, I was able to upload chinese characters into SAP succesfully
Just wondering if any special Thai codepage, character set, technical settings is required as part of Thai installation(I'm not a Basis expert).
Has anyone sucessfully uploaded Thai characters into your SAP system?
Thanks for any tips and informations.
Best regards, Yong Yong

Hi Yong,
I need some help in upload some data using LSMW. I am uploading some customer data which is mainatined in Spanish. Could you please tell me about the settings that i have to take care off before the upload?
my email address is [email protected]

LSMW error message during "Start Idoc generation"

Hi ,
I am getting error message "'/tmp/YS.lsmw.conv' File Has Not Been Accepted for Processing"
during the step "Start Idoc generation" in transaction LSMW.
Please help to solve this issue.
Thanks & regards,
Yogita

Hi,
I already have set port and partner function.
As per the details of the error message, it says "
System Response
Clarify if the inbound file is a Unicode file.
Procedure
If it is not a Unicode file, change the port definition and then start inbound processing again.
If it is a Unicode file, then the file must be generated with the 'EDI_DC40_U' indicator. This must be clarified with the creator of the file.
I have added the check Unicode fomat while defining the port.
Can you please help?
Regards,
Yogita

LSMW short dump

Hi Experts,
We developed a LSMW using Idoc method for Material master. I need to make changes to this LSMW to fix a short dump in step 5 [Read data]. The dump is because of a unicode error. i Know how to fix the dump.
My question is how to make the changes to the program. i knnow the program where the error is. But i need to do it from the LSMW tool. When i open the program directly and make changes, it is not asking for a transport request.
Any suggestions on how to open the code from LSMW?
Please advice.

usually the code will be maintained at mapping level in Step "Maintain Field Mapping and Conversion Rules". Else you can do one thing . Call a perform in the above step and handle the code for the same in the step "Maintain Fixed Values, Translations, User-Defined Routines"
Find below example:
In the step "Maintain Field Mapping and Conversion Rules"
For the below processing here iam calling a perform:
__END_OF_PROCESSING__          After Data Processing Finishes
                               Code:    * __END_OF_PROCESSING__
                                        perform call_commit.
In the step "Maintain Fixed Values, Translations, User-Defined Routines"
Under user defined routines I called above created routine.
User-Defined Routines
    CALL_COMMIT                 call_commit
Check the code below that has been handled in the above routine.
Eigene Routine
form CALL_COMMIT.
endform.

LSMW - BUS1001001 - EDIDC40 Message

I'm trying to set up LSMW to update characteristics on materials using object BUS1001001 and IDOC ARTMAS. When I try and generate the IDOC's I get an error message as below. Anyone know what is causing the problem? It is not a Unicode file.
Message no. EA042
Diagnosis
The file 'ZCOLOURS_ZCOLOURS_ZCOLOURS.lsmw.conv' is not processed.
When starting IDoc inbound processing, the port 'LSMW' was transferred. This port is defined so that the file is not expected in Unicode format.
The 'EDI_DC40' indicator was therefore expected in the control record, but instead 'EDI_DC40_U' is there.
System response
Ensure that the inbound file really is not a Unicode file.
Procedure
If it is a Unicode file, change the port definition and then start inbound processing again.
If it is not a Unicode file, then the file must be generated with the indicator 'EDI_DC40'.
The creator of the file must agree to this.

I was wrong - the partner did have the Unicode flag set wrongly in the environment I was working in.

Help: Error in LSMW migrating assets

When I use LSMW - convert data, the system end up a ABAP dump. What does it mean?
Runtime Errors         UC_OBJECTS_NOT_CONVERTIBLE
Date and Time          2008.05.23 10:28:56
Short text
     Data objects in Unicode programs cannot be converted.
发生了什么?
     Error in the ABAP Application Program
     The current ABAP program "/1CADMC/SAP_LSMW_CONV_00000012" had to be terminated
      because it has
     come across a statement that unfortunately cannot be executed.
错误分析
     The statement
        "MOVE src TO dst"
     requires that the operands "dst" and "src" are convertible.
     Since this statement is in a Unicode program, the special conversion
     rules for Unicode programs apply.
     In this case, these rules were violated.
Trigger Location of Runtime Error:
     Program Name                            /1CADMC/SAP_LSMW_CONV_00000012
     Include                                 /SAPDMC/SAP_LSMW_CONV_FORMS
     Row                                     1,080
     Module type                             (FORM)
     Module Name                             TRANSFER_RECORD
CLEAR:
    g_cnt_idocs_package,
    gt_pack_edi_dc40[],
    gt_pack_edi_dd40[].
ENDFORM.                    "TRANSFER_IDOCS
      FORM TRANSFER_RECORD
FORM transfer_record.
FIELD-SYMBOLS:
    <l_record>,
    <l_prev_record>.
DATA:
    l_prev_record TYPE tumls_segment.
DATA:
    l_len_trgstr TYPE i.
IF g_skip_record = no AND
     g_skip_transaction = no.
    ASSIGN (g_record) TO <l_record>.
    CASE g_objecttype.
      WHEN '01' OR '02'.
        gt_buffer-record = g_record.
        gt_buffer-data = <l_record>.
        APPEND gt_buffer.
      WHEN '03' OR '04'.
        IF g_record = 'EDI_DC40'.
          IF p_trfcpt = yes.
            gt_curr_edi_dc40 = <l_record>.
            APPEND gt_curr_edi_dc40.
          ELSE.
            gt_buffer-record = g_record.
            gt_buffer-data = <l_record>.
            APPEND gt_buffer.
          ENDIF.
        ELSE.
          CLEAR edi_dd40.
          edi_dd40-segnam = g_edidd_segnam.
          edi_dd40-mandt = edi_dc40-mandt.
          edi_dd40-docnum = edi_dc40-docnum.
          ADD 1 TO g_segnum.
          edi_dd40-segnum = g_segnum.
          edi_dd40-hlevel = g_edidd_hlevel.

can anyone read?

Problem in task list uploading through lsmw

Hi,
Can someone please tell me how to upload a task list through lsmw wherein my description for the task list has been maintained
in English but the operation description is maintained in Thai language.Due to description being maintained in Thai language I am not
able to upload my data.

Hi
Whats the error you are getting when you upload?
Please save the operation text file(note pad) as "unicode" in the encoding-.and try to upload.
Regards
Seenu

Loading Language translations for Catalogs using LSMW

I have hundreds of codes entered for a Catalog in English and I need to be able to load all the French translations for those codes. Doing a translation by hand is simple by just clicking on the Translation selection in the Menu. However, when I try to do that using LSMW recordings, it doesn't record a field that I can attach my source data to for the translation. So, basically, I can't get it to work. Is this even possible? Is there another way to load translations?

Hi,
1. Data has been captured as per the template
2. Instead of capturing catalog codes in English, keep those details in the Required language (in your case, its French).
3. Save the Excel file as Unicode Text instead of Tab delimited or other recommended formats.
4. Login into SAP as normal. Nothing specifically required from SAP side.
5. Do the normal LSMW technique to upload the data.
Material Description in Chineese language
http://www.sap-img.com/general/lsmw-and-ftp-upload-chinese-or-non-english-characters.htm
Regards,
Maheswaran.
Edited by: Maheswaran.K on Apr 12, 2011 8:56 AM

LSMW Custom program for updating picked quantity in outbound delivery

I have been tasked with creating an LSMW that will update the picked quantity in an outbound delivery. I originally thought of using a recording on transaction vl02n, but I need the LSMW to work with variable amount of item lines.
Through some research I figured out that FM WS_DELIVERY_UPDATE_2 can update the picked quantity. I have successfully created a custom program that calls this FM.
I have created what I believe to be the correct entries in the SXDA0, SXDA1, SXDA2, and SXDA3 tables to make my custom program work with LSMW. I am able to find my program in the "Maintain Object Attributes." I am also able to "Maintain Structure Relations Step" (screen shot attached) I am currently using VBKOK and VBPOK for the header and line item structures respectively.
My difficulty is converting the data. I have tried everything from having no conversion rules to mapping many fields and I always receive the following error (screen shot also provided).
Error analysis
The statement
     "Move src TO dst"
requires that the operands "dst" and "src" are convertible.
Since this statement is in a Unicode program, the special conversion
rules for Unicode programs apply.
In this case, these rules were violated.
Program /SAPDMC/SAP_LSMW_CONV_FORMS
Include /SAPDMC/SAP_LSMW_CONV_FORMS
Row 1,080
Module type (FORM)
Module Name TRANSFER_RECORD
Since I have run the conversion with no conversion rules I am very confused as to why I am still receiving this error. Any insight would be greatly appreciated.

For anyone I have uncovered some interesting things about my issue. I started going through the conversion code piece by piece trying to figure out what data element the system was choking on.
After digging though the program and using the debugger I found out that the issue was in FORM transfer_record.
ASSIGN (g_record) TO <l_record>.
     CASE g_objecttype.
       WHEN '01' OR '02'.
         gt_buffer-record = g_record.
         gt_buffer-data = <l_record>.
         APPEND gt_buffer.
If this LSMW was working
g_record = 'VBKOK'
<l_record> = 'VBKOK'
But what is actually happening
g_record = 'VBKOK'
<l_record> = "Structure of some sort
I do not know why this is happening since the field symbol is being assigned right before this piece of code. Any suggestions are greatly appreciated.

LSMW - Unicode

Similar Messages

Maybe you are looking for