Error in unicode export...

Hi,
We are doing an inplace conversion of an ERP2005SR2 system. We have just upgraded the system from 4.6C yesterday and are now performing an unicode conversion.
Unfortunately we have an error in the unicode export... See below:
From the SAPINST_DEV.LOG file:
ERROR      2007-08-25 17:08:03 [iaxxbdbld.cpp:1001]
           CR3ldStep::startR3ldProcesses lib=iamodload module=CR3ldStep
MSC-01015 Process finished with error(s), check log file G:\usr\sap\SAPinst\CPC\EXP/SAPSDIC.log
From the SAPSDIC.LOG file:
/sapmnt/BNP/exe/R3load: START OF LOG: 20070825202939
/sapmnt/BNP/exe/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
/sapmnt/BNP/exe/R3load: version R7.00/V1.4
Compiled Aug 8 2007 00:22:00
/sapmnt/BNP/exe/R3load -datacodepage 4102 -e /usr/sap/SAPinst/CPC/EXP/SAPSDIC.cmd -l /usr/sap/SAPinst/CPC/EXP/SAPSDIC.log -inplace
DbSl Trace: CPFB755 occured. Refer to job log.
(DB) INFO: connected to DB
(EXP) INFO: check NameTab widths: Result=0.
(RC) WARNING: unexpected "ext:" entry at line 6 in file /usr/sap/SAPinst/CPC/EXP/SAPSDIC.cmd,
            entry will be ignored
(RSCP) WARN: UMGCOMCHAR read check, skip: no data found; probably old SPUMG.
(RSCP) INFO: "/usr/sap/SAPinst/CPC/EXP/SAPSDIC004.xml" created.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1100
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(GSI) INFO: dbname   = "BNPSAP001                                                                                "
(GSI) INFO: vname    = "DB400                           "
(GSI) INFO: hostname = "SAP001                                                          "
(GSI) INFO: sysname = "OS400"
(GSI) INFO: nodename = "SAP001"
(GSI) INFO: release = "3"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "006500039C6C"
(GSI) INFO: instno   = "0020141614"
(EXP) INFO: starting NameTab check. Allow 999999999 misses in DDNTT, 10000 misses in DDNTT_CONV_UC, 0 outdated alternate NameTab entries according to CRTIMESTMP.
(EXP) INFO: /SSF/DHEAD                        missing in DDNTT_CONV_UC
(EXP) INFO: /SSF/DTAB                         missing in DDNTT_CONV_UC
(EXP) INFO: /SSF/PTAB                         missing in DDNTT_CONV_UC
(EXP) INFO: TIBAN_ACTIVE                      missing in DDNTT_CONV_UC
(EXP) ERROR: entry for COPABBSEG                         in DDNTT is newer than in DDNTT_CONV_UC: 20070825073714 > 20070825073318
(EXP) ERROR: entry for COPABBSEG_GLX                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073756 > 20070825073318
(EXP) ERROR: entry for COPACRIT                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073801 > 20070825073318
(EXP) ERROR: entry for COPAOBJ                           in DDNTT is newer than in DDNTT_CONV_UC: 20070825073804 > 20070825073318
(EXP) ERROR: entry for EE72_COPAKEY                      in DDNTT is newer than in DDNTT_CONV_UC: 20070825073756 > 20070825072528
(EXP) ERROR: entry for JBDCHARDERI                       in DDNTT is newer than in DDNTT_CONV_UC: 20070825073804 > 20070825071134
(EXP) ERROR: entry for JBDCHARPAFO                       in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825071134
(EXP) ERROR: entry for JBD_STR_FO_PA_CHAROBJ             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825071127
(EXP) ERROR: entry for JHF11_KOMP_STR                    in DDNTT is newer than in DDNTT_CONV_UC: 20070825073820 > 20070825071037
(EXP) ERROR: entry for JVKOMP                            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073822 > 20070825070937
(EXP) ERROR: entry for KOMG                              in DDNTT is newer than in DDNTT_CONV_UC: 20070825073808 > 20070825070802
(EXP) ERROR: entry for KOMGF                             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073823 > 20070825070802
(EXP) ERROR: entry for KOMGFNEW                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073836 > 20070825070802
(EXP) ERROR: entry for KOMGFOLD                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073838 > 20070825070802
(EXP) ERROR: entry for KOMP                              in DDNTT is newer than in DDNTT_CONV_UC: 20070825073814 > 20070825070755
(EXP) ERROR: entry for KOMPAKE                           in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825070755
(EXP) ERROR: entry for OICIL                             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073825 > 20070825070219
(EXP) ERROR: entry for OIRCPMITEM                        in DDNTT is newer than in DDNTT_CONV_UC: 20070825073826 > 20070825070148
(EXP) ERROR: entry for STR_KOMG                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073828 > 20070825063750
(EXP) ERROR: entry for SVVSC_COPA                        in DDNTT is newer than in DDNTT_CONV_UC: 20070825073757 > 20070825063738
(EXP) ERROR: entry for TRCON_CONTRACT_DATA               in DDNTT is newer than in DDNTT_CONV_UC: 20070825073846 > 20070825053905
(EXP) ERROR: entry for TRCON_CONTRACT_DATA_MM            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073847 > 20070825053905
(EXP) ERROR: entry for TRCON_CONTRACT_DATA_SD            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for TRCON_IT_KOMP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073830 > 20070825062450
(EXP) ERROR: entry for TRCON_OUTP_DBDATA                 in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for WB2_EKOMP                         in DDNTT is newer than in DDNTT_CONV_UC: 20070825073831 > 20070825060540
(EXP) ERROR: entry for WCB_COND_DATA                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for WCB_COND_DISP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073839 > 20070825053905
(EXP) ERROR: entry for WCB_KEY_CHANGE                    in DDNTT is newer than in DDNTT_CONV_UC: 20070825073843 > 20070825053905
(EXP) ERROR: entry for WCB_KOMG                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073832 > 20070825053905
(EXP) ERROR: entry for WCB_KOMG_HELP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073834 > 20070825060526
(EXP) ERROR: entry for WRF_POHF_KOMP_STY                 in DDNTT is newer than in DDNTT_CONV_UC: 20070825073844 > 20070825060357
(EXP) INFO: NameTab check finished. Result=2 #20070825203013
(EXP) INFO: check for inactive NameTab entries: Result=0.
(DB) INFO: disconnected from DB
/sapmnt/BNP/exe/R3load: job finished with 1 error(s)
/sapmnt/BNP/exe/R3load: END OF LOG: 20070825203013
I have an OSS message on "very-high" on this error, but they are not helping very much! SAP has proposed note 738858 were we set two environment variables. We have done this and that did not help.
We have upgraded and unicode converted two test systems and one development system in the last 2 months without this error.
Do you have any ideas?
Best regards
Henrik Hviid

Hello!!:
I'm doing a CU&UC (as say the CU&UC Guide), and now i'm in the phase of upgrade from 46C MDMP to ECC6.0 no unicode (later in other phase i've to change to unicode). I've generated all the SCAN's, and launch the SAPup (Upgrade Process). The phase UPGRADE/SHADOW: START OF PHASE RUN_RADCUCNT_ALL of the SAPup has created the job RADCUCNTUPG, and has been running during 20 hours. It's possible to do this phase quickly??.
Otherwise, in the chapter 3.2.2 Phase RUN_RAD_CUCNT_NEW is going to regenerated the DDIC Objects. So in the Additional Preparation Steps in SAP NW7.0 nonUC (chapter 4.1. of the guide) will be neccesary to launch again the program RADCUCNT with the variant UNICODE-02??? or we've only to do the seven steps that appears in the Guide???.
I've seen the Note 932779, 837173, about this, but i don't see the solution. In the page 7 and 8 of the Note OSS 932779, say that:
- during CU&UC nametab is touched twice, once for upgrade and once for unicode conversion (in phase RADCUCNT_ALL and in phase RADCUCNT_NEW).
- later appears that during unicode conversion preparation (SPUM4/SPUMG) RADCUCNT runs again twice.
So in the chapter 4.1 about additional preparation steps in NW7.0 non UC there is not this step (only appears7 steps). It's really neccesary in the CU&UC in this moment?
Thanks!.
Alfredo.

Similar Messages

ORA-00942 Error during unicode export of BI 7.0

Hello Everyone,
I am doing an export of a non-unicode BI 7.0 system to convert and import it into a Unicode database. All the jobs have passed except one and I see the following error in the log file (SAPAPPL0_3.log)
/usr/sap/ABD/SYS/exe/run/R3load: START OF LOG: 20080302124247
/usr/sap/ABD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
/usr/sap/ABD/SYS/exe/run/R3load: version R7.00/V1.4
Compiled Jun 9 2007 09:20:06
/usr/sap/ABD/SYS/exe/run/R3load -e SAPAPPL0_3.cmd -datacodepage 4102 -l SAPAPPL0_3.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) WARN: UMGCONTAINER has 1 problems.
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1100
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(GSI) INFO: dbname   = "ABD20070922100908
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "ussbbdd5                                                        "
(GSI) INFO: sysname = "HP-UX"
(GSI) INFO: nodename = "ussbbdd5"
(GSI) INFO: release = "B.11.23"
(GSI) INFO: version = "U"
(GSI) INFO: machine = "ia64"
(GSI) INFO: instno   = "INITIAL   "
(EXP) ERROR: DbSlExeRead failed
rc = 103, table "/BIC/SZTERR_CD"
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(DB) INFO: disconnected from DB
/usr/sap/ABD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/ABD/SYS/exe/run/R3load: END OF LOG: 20080302124251
When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.
SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';
I did finish all the unicode preconversion steps and also ran the SMIGR_CREATE_DDL program. I had exported recently from the same system but I never got this error during that run.
Another question is about the order in which the steps need to be performed. I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?
Thanks again for your help!

Hello Stacy,
> When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.
> SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';
If the object does not exists on the source target database, please check if the ddic of sap still contains the table definition. (SE11 or SE14)
If yes you can set the status of the table /BIC/SZTERR_CD to "ok" in the corresponding task file.
You can not fix this problem in other way after you have started the conversion, because of the export files are already generated (with the information of the sap ddic)...
> I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?
That was the right way.
Regards
Stefan

Error in Phase EXPORT of CU&UC Migration 46C to ECC60: ORA-00942

Hi,
We are making a 46C to ECC 6.0 upgrade EHP4 Stack 8.
We have migrated to the system ECC6.0 not Unicode. Now we're in the
process of Export to Unicode and we got the following errors:
(EXP) ERROR: failed DbSlExeRead rc = 103, table "/ BI0/PTCTUSERNM"
(SQL error 942) error message returned by DbSl: ORA-00942: table or
view does not exist
(DB) INFO: disconnected from DB
(EXP) ERROR: failed DbSlExeRead rc = 103, table "DFKKCOLFILE_P_W (SQL
error 942) error message returned by DbSl: ORA-00942: table or view
does not exist
(DB) INFO: disconnected from DB
We found that the 2 tables do not exist in previous 46C release but
exist in other systems with ECC6.0 release.
We found that, at least, DFKKCOLFILE_P_W table did not exist in our
system migrated not unicode.
We have reviewed the OSS Note 1156968 (Add. info. EHP on upgrading to 4
for ERP SAP ABAP 6.0) and we did not find a solution to our errors.
Is there a process or mechanism to put these tables in the system if
the migration process has not created them? or is it possible to ignore
these errors in the export and go on with the migration and fix the
tables when we are done with the migration? If we ignore these errors
will we encounter problems because of that?
Can you help us?
Thank you in advance.

Hello, we have solved the problem.
To help someone with the same error, what we have done is:
1.- wait until all the processes has finished and the export is stopped.
2.- startup SAP
3.- SE14 and look up the tables. Crete the tables in the database.
4.- stop SAP
5.- Retry the export (if you did all the steps with sapinst running but the dialogue window in the screen) or begin the sapinst again with the option: "continue with the old options".
Regards to all.

Unicode Export - unable to retrieve nametab info for logic table BSEG

Hi
We are performing a unicode export (CUUC from 4.6C upgrade to ECC 6.0) and we have incurred this error.
        Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
Our OS is HPUX11.31 & Database is 10.2.0.2
myCluster (63.21.Exp): 1610: inconsistent settings for table position validity detected.
myCluster (63.21.Exp): 1611: nametab says table positions are valid.
myCluster (63.21.Exp): 1614: alternate nametab says table positions are not valid.
myCluster (63.21.Exp): 1617: for field 310 of nametab displacement is 1877, yet dbtabpos shows 1885.
myCluster (63.21.Exp): 1621: character length is 1 (in) resp. 2 (out).
myCluster (63.21.Exp): 1257: unable to retrieve nametab info for logic table BSEG      .
myCluster (63.21.Exp): 8358: unable to acquire nametab info for logic table BSEG      .
myCluster (63.21.Exp): 2949: failed to convert cluster data of cluster item.
myCluster: RFBLG      *400**AT10**0000100000**2004*
myCluster (63.21.Exp): 322: error during conversion of cluster item.
myCluster (63.21.Exp): 323: affected physical table is RFBLG.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/SBX/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SBX/SYS/exe/run/R3load: END OF LOG: 20081102104452
We checked the note 913783 as per the CUUC guide but the correction only for package SAPKB70004 to 6. but we are in package SAPKB70011.
We had found two notes:
1. Note 1238351 - Hom./Het.System Copy SAP NW 7.0 incl. Enhancement Package 1
:Solution:
There are two possible workarounds:
1. Modify DDL<dbs>.TPL (<dbs> = ADA, DB2, DB4, DB6, IND, MSS, ORA) BEFORE the R3load TSK files are generated;
              search for the keyword "negdat:" and add "CLU4" and "VER_CLUSTR" to thisline.
2. Modify the TSK file (most probably SAPCLUST.TSK) BEFORE R3load import is(re-)started.
              search for the lines starting with "D CLU4 I" and "D VER_CLUSTR I" and change the status (i.e. "err" or "xeq") to "ign" or remove the lines. "
I tried the above solution by editing the file DDL*.TPL but it is skipping the table and marks it as completed but its not the good solution as we will be miss the data from the table RFBLG.
2. Note 991401 - SYSCOPY EXPORT FAILS:SAPCLUST:ERROR: Code page conversion:
Solution
Activate the table.
Then call the RADCUCNT report. Do not change the selected parameters, but ensure that 'Overwrite Entries' is selected. Set the 'Unicode Length' to 2 and fill the last two fields 'Type' and 'Name' with TABL and TACOPAB respectively. Then select 'No Log' or specify a log name.
Execute the RADCUCNT report and restart the export.
We have not tried this solution, bcos SAP is still down and CDCLS job is still running.
We would like to know whether you have faced any issues like the above one and what is your suggested approach and solution.
Is it safe to start SAP now (when the CDCLS job runs) and then try to activate the table RFBLG?
Regards
Senthil
Edited by: J. Senthil Murugan on Nov 3, 2008 1:41 AM
Edited by: J. Senthil Murugan on Nov 3, 2008 3:36 AM

Hi Senthil,
If you have done your pre-conversion steps before upgrade and after upgrade successfully then you should not see the below errors. However changes to SPDD tables may some times also have some impact during conversion and throws nametab errors occurs. Program RADCUCNT runs in the end of upgrade to update nametab tables if any new changes happned during upgrade.
You can do any no of exports to complete jobs successfully.yeah When export running you shouldnt bring SAP up.
The tables you have mentioned all are cluster tables and CDCLS being the biggest table it will take hrs to complete depending on your size of the database.
Do not pay around with the .TSK file until if you are sure you want to re-execute it.Your first possiblility is skipped because there may be multiple same .TSK files present locally(where u r running distribution.monitor (or) sapinst ) and on the common directory. You may also look at the .TSK.bkp files because it get information and creates a new .TSK. This is not complicated but tricky.
secound possibility is to update the changed tables(eg: RFBLG...) to conversion tables.Follow the Note but make sure no R3load processes are running before you start SAP. If you dont want to wait long and sure to restart other processes which are running you can kill it and start SAP. Specify your error tables only and follow instructions given in the note.Once done bring down SAP app. and restart the export process using ur sapinst or distribution monitor.
Regards,
Vamshi.

Frequently faced errors in Unicode while SAP Upgrade

Hi Gusy,
I am going work on Unicode upgarde project, can any one share Frequently faced errors in Unicode while SAP Upgrade.
Thanks,
Gourisankar.

Hi
MESSAGEG@3
Replace variable declaration of type X with appropriate value from method cl_abap_char_utilities
i.e.      CONSTANTS:      con_tab TYPE x VALUE '09',
               con_cret TYPE x VALUE '0D'.
would be replaced with
     CONSTANTS:      con_tab TYPE c value cl_abap_char_utilities=>HORIZONTAL_TAB,
               con_cret TYPE c value cl_abap_char_utilities=>CR_LF.
*UPLO      *
Upload/ws_upload and download/ws_download are obsolete, since they are not Unicode enabled. Replace
with appropriate methods from cl_gui_frontend_services. Please also note that the data types of the various
parameters will also probably also need changing for the new method calls but the code below demonstrates
how to do this. I_TABLE is the original table and IT_UCTABLE is the converted table.
i.e. Function module u2018WS_DOWNLOADu2019
CALL FUNCTION 'WS_DOWNLOAD'
      EXPORTING
           FILENAME                = p_file
           FILETYPE                = 'ASC'
         MODE                    = ' '
       TABLES
            DATA_TAB                = i_table
      EXCEPTIONS
would be replaced with
data: gd_file type string.
types: t_uctable like line of i_table.
data: it_uctable type standard table of t_uctable.
gd_file = p_file.
it_uctable[] = i_table[].
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
    filename = gd_file
    filetype = 'ASC' " DAT,WK1
    Append   = ' '   "if mode = A then this would be X
CHANGING
    data_tab = it_uctable
EXCEPTIONS
    OTHERS   = 1.
Function module u2018DOWNLOADu2019
      CALL FUNCTION 'DOWNLOAD'
        EXPORTING
          filename = p_file
          filetype = 'WK1'
        TABLES
          data_tab = i_table.
would be replaced with
data: gd_file type string.
DATA: ld_filename TYPE string,
      ld_path TYPE string,
      ld_fullpath TYPE string,
      ld_result TYPE i.
types: t_uctable like line of i_table.
data: it_uctable type standard table of t_uctable.
gd_file = p_file.
shift gd_file RIGHT DELETING TRAILING '\'.
shift gd_file RIGHT DELETING TRAILING '/'.
shift gd_file left DELETING LEADING space.
CALL METHOD cl_gui_frontend_services=>file_save_dialog
    EXPORTING
      DEFAULT_EXTENSION = 'WK1'
      default_file_name = gd_file
      INITIAL_DIRECTORY = gd_file
    CHANGING
      filename          = ld_filename
      path              = ld_path
      fullpath          = ld_fullpath
      user_action       = ld_result.
check ld_result eq 0.
gd_file = ld_fullpath.
gd_file = p_file.
it_uctable[] = i_table[].
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
    filename = gd_file
    filetype = 'ASC' " DAT,WK1
    Append   = ' '   "if mode = A then this would be X
CHANGING
    data_tab = it_uctable
EXCEPTIONS
    OTHERS   = 1.
Or in circumstances where you need to add field texts to the first line of the file you could use the
GUI_DOWNLOAD function module:
DATA: BEGIN OF fields_tab OCCURS 0,
        f1(50),
      END   OF fields_tab.
fields_tab-f1 = 'field1 text'.
APPEND fields_tab.
fields_tab-f1 = 'field2 text'.
APPEND fields_tab.
fields_tab-f1 = 'field3 text'.
APPEND fields_tab.
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      filename                = i_filename
      filetype                = 'DAT'
    IMPORTING
      filelength              = filelen
    TABLES
      data_tab                = itab
      fieldnames              = fields_tab
    EXCEPTIONS
Note: u2018ws_uploadu2019 and u2018uploadu2019 would be the same as above but would use the
cl_gui_frontend_services=>gui_upload method call instead:
CALL METHOD cl_gui_frontend_services=>gui_upload
EXPORTING
    filename = gd_file
    filetype = 'ASC' " DAT,WK1
    Append   = ' '
CHANGING
    data_tab = it_uctable
EXCEPTIONS
    OTHERS   = 1.
OPEN 004
Add u2018ENCODINGu2019 addition to statement
i.e.      OPEN DATASET G_DATAFILE for OUTPUT IN TEXT MODE.
would be replaced with
     OPEN DATASET G_DATAFILE for OUTPUT IN TEXT MODE ENCODING NON-UNICODE.
OPEN 002
IN..Mode is expected within open dataset command.
i.e.      OPEN DATASET wfilepath FOR OUTPUT.
would be replaced with
     OPEN DATASET wfilepath FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE.
Or      OPEN DATASET wfilepath FOR OUTPUT IN BINARY MODE.
OPEN 001
FOR INPUT, FOR OUTPUT, FOR APPENDING or FOR UPDATE expected!
i.e.      OPEN DATASET wfilepath FOR OUTPUT.
would be replaced with
     OPEN FOR OUTPUT DATASET wfilepath FOR OUTPUT IN TEXT MODE.
DESCIBE002
THE DESCRIBE LENGTH can only be used with the IN BYTE or IN CHARACTER MODE
i.e.      describe field e_text length line_length.
would be replaced with
     describe field e_text length line_length IN CHARACTER MODE.
ASSIGN 019
The statement u2018ASSIGN PATH+PATHLENGTH TO
.u2019 Returns the following error message:
"You cannot use ASSIGN f+offset. Always use an explicit length (or '*')".
i.e.      ASSIGN PATH+PATHLENGTH TO
would be replaced with
     ASSIGN PATH+PATHLENGTH(2) TO
. u201Creplace 2 with the length of the field
MESSAGEG!2
Itab/structure and u201C u201C are not mutually convertible in a Unicode program
i.e.      G_SHOW_LIST = SPACE.
would be replaced with
     Clear: G_SHOW_LIST.
Or      G_SHOW_LIST-field1 = space.
     G_SHOW_LIST-field2 = space.
                         u2026etc
*MESSAGEG!3      *
var and var are not comparable in a Unicode program
Example      Data: VAR like tabix.
was replaced with
          Data: VAR type sy-tabix.

Error in Pre- Export methods for a request

Hi All,
I am getting an error while releasing a request, its giving
"Error in Pre- Export methods for a request DM0k.....". Could you please tell me why and how can I rectify that?
Thanks.
NA

Please go through as per the link
[SAP Transport Request |http://www.sap-basis-abap.com/sapbs008.htm]
thanks
G. Lakshmipathi

Error in pre-export methods for request

hi...
while releasing the TR we are facing this error msg..." Error in pre-export methods for request" it is showing lock in fornt of the TR.neither be able to delete the TR ....
do reply as soon as possible..

Hi,
I had the same error PU238.
What I did was:
Execute SE03 to unlock the object.
Then execute the program 'RS_STREE_OBJECTS_TO_REQ_GET', not sure what it does.
Afterwards, it worked perfectly.
Hope that information helps you.
Regards,

Error Detected by export DLL for pdf

Post Author: netonomous
CA Forum: Exporting
We have a Win 2000 box with this feature working with no problem.
I am getting an error exporting to .PDF when using .NET 2 Business Objects. Quite the opposite of your situation. Any ideas? My temp folder is under C:\Windows\Temp and the error I receive is
Error in File C:\WINDOWS\TEMP\TSRDetail {F7EAB0D7-408F-4787-A1FE-5086F7199CB9}.rpt: Error detected by export DLL: This is on a Win 2003 box Service Pack 1 with IIS 6.0 with ASP.NET Framework for Crystal using an Oracle Database. Excel exports work ok.
Thanks much in advance.

Post Author: netonomous
CA Forum: Exporting
We have a Win 2000 box with this feature working with no problem.
I am getting an error exporting to .PDF when using .NET 2 Business Objects. Quite the opposite of your situation. Any ideas? My temp folder is under C:\Windows\Temp and the error I receive is
Error in File C:\WINDOWS\TEMP\TSRDetail {F7EAB0D7-408F-4787-A1FE-5086F7199CB9}.rpt: Error detected by export DLL: This is on a Win 2003 box Service Pack 1 with IIS 6.0 with ASP.NET Framework for Crystal using an Oracle Database. Excel exports work ok.
Thanks much in advance.

Releasing transport request has an error during the 'export' step.

Hello Everyone,
My environment is ERP 6.0 EHP6, AIX 6.3, Oracle 11g.
We have a transport request that was created in our development system by deleting some obsolete roles. When we try to release the transport request to our q/a system it terminates with errors in the export step.
The errors are.
   End of export R3TRTABUUSR10
   no E071K or E071K_STR entries found for R3TRTABUUSR11
   Start export R3TRTABUUSR12 ...
   no E071K or E071K_STR entries found for R3TRTABUUSR13
Of course we cannot create a new transport request because the roles were deleted.
Can someone please explain to me what could have cause this type of error and possibly how to resolve it?
Regards,
Ron

Hi Ron,
As per your log, no E071K or E071K_STR entries found forR3TRTABUUSR11
no E071K or E071K_STR entries found for R3TRTABUUSR1
Looks like there is no entry found for E071K or E071K_STR in table USR11 and USR13.
Please check those table and make sure the above entries are there, if not that could be the issues.
Also, please check if these tables (USR10, USR11, USR12 USR13) are active in SE14.
Thanks
Adil

I got error when I export database ORACLE 9i from solaris 9.

I want to export full database ORACLE 9i from SOLARIS 9 to import full database on ORACLE 9i on windows.
I set oracle environment and NSL_LANG with command:
bash-3.00$ export ORACLE_SID=TIS
bash-3.00$ export NLS_LANG=AMERICAN_AMERICA.TH8TISASCII
and then run command to export:
bash-3.00$ exp system/manager@TIS full=y file= /u03/dmp/TISfull.dmp log=/u03/dmp/exp_TIS.log
I got error message as:
Export: Release 9.2.0.1.0 - Production on Thu Oct 8 17:57:32 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Export done in TH8TISASCII character set and UTF8 NCHAR character set
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
EXP-00008: ORACLE error 25153 encountered
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_AW", line 42
ORA-06512: at "SYS.DBMS_AW", line 105
ORA-06512: at "SYS.DBMS_AW", line 221
ORA-06512: at "SYS.DBMS_AW_EXP", line 264
ORA-06512: at line 1
EXP-00083: The previous problem occurred when calling SYS.DBMS_AW_EXP.schema_info_exp
. exporting cluster definitions
EXP-00056: ORACLE error 25153 encountered
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_LOB", line 424
ORA-06512: at "SYS.DBMS_METADATA", line 1140
ORA-06512: at line 1
EXP-00056: ORACLE error 25153 encountered
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_LOB", line 424
ORA-06512: at "SYS.DBMS_METADATA", line 1140
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
How can I solve this problem?
Any suggestion?

#### HOW to solve it.
## To check the default temporary tablespace of the database:
SQL> select property_name, property_value from database_properties;
## check DEFAULT_TEMP_TABLESPACE, if it use wrong temporary tablespace, run:
SQL> alter database default temporary tablespace temp;
## check user with temporary tablespace, run command:
SQL> select username, temporary_tablespace, account_status from dba_users;
## change temporary tablespace:
SQL> create temporary tablespace temp1 tempfile '/data/u01/app/oracle/oradata/TIS/temp_b.dbf' size 100m;
SQL> alter database default temporary tablespace temp1;
SQL> drop tablespace temp including contents and datafiles;
SQL> create temporary tablespace temp tempfile '/data/u01/app/oracle/oradata/TIS/temp01.dbf' size 100m autoextend off extent management local uniform size 1m;
SQL> alter database default temporary tablespace temp;
SQL> drop tablespace temp1 including contents and datafiles;
Thanks

Error message when exporting

keep getting error message when exporting 12 min project from premier pro ,
never had this problem.
Adobe tech used remote access to assist me with something and changed settings etc.

WHAT error message?
More information needed for someone to help... please click below and provide the requested information
-PPro Information FAQ http://forums.adobe.com/message/4200840

Error synchronizing with Windows 7 Contacts: "CRADSDatabase ERROR (5211): There is an error converting Unicode string to or from code page string"

CRADSDatabase ERROR (5211): There is an error converting Unicode string to or from code page string
Device Blackberry Z10
Sw release 10.2.1.2977
OS Version 10.2.1.3247
The problem is known by Blackberry but they didn't make a little effort to solve this problem and they wonder why nobody buy Blackberry. I come from Android platform and I regret buying Blackberry: call problems(I sent it to service because the people that I was talking with couldn't hear me), jack problems (the headphones does not work; I will send it again to service). This synchronisation problem is "the drop that fills the glass". Please don't buy Blackberry any more.
http://btsc.webapps.blackberry.com/btsc/viewdocument.do?noCount=true&externalId=KB33098&sliceId=2&di...

This is a Windows registry issue, if you search the Web using these keywords:
"how to fix craddatabase error 5211" you will find a registry editor that syas it can fix this issue.

Error 541 when exporting to PDF

Post Author: BCLin
CA Forum: Other
Hi,Our application is using Crystal Report VCL (version 9) component for exporting reports.I have a customer reported that he got an error message "Not enough memory for operation" when exporting the report to PDF. I opened the .rpt file sent in by the customer in XI, and tried to export the report in XI to PDF, failed due to "memory full". By deleting something in the report header and reset the database location, it now can be exported within XI, but it is still failed to be exported to PDF through my application, the error message is changed to "Error: 541 Error detected by export DLL...", but it is no problem to export other .rpt files through my application. It seems there are differences between those .rpt files cause above problems, but what are they? Can somebody here tell me what do I need to check to find out the differences? Thanks in advance.

turn down the little triangle next to the 'red' error message--you sholud then see what the (2) problems are

Content generation error. [Error: Failed to Export the PDF file.]

Hi;
Everytime i try to update an article within a folio in DPS folio builder i get this error :
Content generation error.
[Error: Failed to Export the PDF file.]
My colleague next to me is running exactly the same set up and doesnt get the error. in fact his update anf sideloading is fast as lightning.
the ONLY difference is that im running v28 tools and he is on v27, however wehave another colleague running v28 and his updates work perfectly.
Any ideas lovely community?
Scott

Hi Bob;
Have tried that one. And again on your suggestion....no luck.
Scott

An error occurred while exporting principals

Hi All,
When i am exporting users (not roles and groups) i am getting the error "An error occurred while exporting principals; contact your System Administrator". I don't able to understand the cause of the error.
And in default trace i get the same description of the error. Please guide.
Regards,
Bharat Mistry.

Hi Robert,
Thanks for the reply.
Find the default trace details
An error occurred while exporting principals
[EXCEPTION]
com.sap.security.core.wd.exception.UmeUiException: com.sap.security.api.UMException
at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.handleThrowable(UmeUiFactoryCompInterface.java:2872)
at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.batchExport(UmeUiFactoryCompInterface.java:433)
at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.batchExport(InternalUmeUiFactoryCompInterface.java:510)
at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.batchExport(InternalUmeUiFactoryCompInterface.java:887)
at com.sap.security.core.wd.batchexport.BatchExportComp.exportPrincipals(BatchExportComp.java:233)
at com.sap.security.core.wd.batchexport.wdp.InternalBatchExportComp.exportPrincipals(InternalBatchExportComp.java:157)
at com.sap.security.core.wd.batchexport.BatchExportCompInterfaceView.onPlugExportPrincipalsIn(BatchExportCompInterfaceView.java:102)
at com.sap.security.core.wd.batchexport.wdp.InternalBatchExportCompInterfaceView.wdInvokeEventHandler(InternalBatchExportCompInterfaceView.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.Exception: classname:[com.sap.security.api.UMException]message:[TP Adani Energy Limited not found]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.sap.security.core.jmx.impl.JmxServer.handleThrowable(JmxServer.java:717)
at com.sap.security.core.jmx.impl.JmxServer.batchExport(JmxServer.java:307)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at javax.management.StandardMBean.invoke(StandardMBean.java:286)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.security.core.jmx._gen.IJmxServer$Impl.batchExport(IJmxServer.java:1428)
at com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.batchExport(JmxModelCompInterface.java:319)
at com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.batchExport(InternalJmxModelCompInterface.java:427)
at com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface$External.batchExport(InternalJmxModelCompInterface.java:730)
at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.batchExport(UmeUiFactoryCompInterface.java:431)
... 52 more
Caused by: com.sap.security.api.UMException: TP Adani Energy Limited not found
at com.sap.security.core.jmx.impl.JmxBatch.batchExport(JmxBatch.java:68)
at com.sap.security.core.jmx.impl.JmxServer.batchExport(JmxServer.java:300)
... 73 more
Regards,
Bharat Mistry.

Error in unicode export...

Similar Messages

Maybe you are looking for