ABAP Unicode issue...

ABAP gurus,
We are in the process of upgrading our SAP from 4.6C to ECC 6.0. I am trying to pass some of the programs from UCCHECK. I got following exceptions:
"XK_HEX00" must be a character-type data object (data type C, N, D, T or STRING)
"XK_HEX09" must be a character-type data object (data type C, N, D, T or STRING)
"XK_HEXLF" must be a character-type data object (data type C, N, D, T or STRING)
We have following statements in the program:
      xk_hex00(1)   type x value '00',      "binaer null
      xk_hex09(1)   type x value '09',      "Steuerzeichen Tabulator
      xk_hexcr(1)   type x value '0D',      "Steuerzeichen CR
      xk_hexlf(1)   type x value '0A',      "Steuerzeichen LF
Please help.
Thanks.
Rajesh.

Please help how to convert hexadecimal values '00', '09', '0D' and '0A' in type C for unicode validation. I know there is a class called CL_ABAP_CHAR_UTILITIES. But I don't know what attribute to use for what ?
Thanks.
Regards,
Rajesh.

Similar Messages

Error in installing SAP Web AS ABAP (Unicode Version)

I have SAP Web AS Java in my machine already, but in order to install XI, I need to install also ABAP unicode. During the installation, I got the following error. I can't interpret it what it is or what I have done wrong. Can anybody give me a hand?
Here is the error message:
ERROR 2005-12-16 01:51:17
MOS-01082 File system node E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE with type NODE does not exist.
ERROR 2005-12-16 01:51:17
MOS-01105 Processing of one or more file system node operations of table   Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='J2E' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF') Row[0]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"   Row[1]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E" NodeType="DIRECTORY" OpMode="CREATE"   Row[2]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"   Row[3]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[4]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"   Row[5]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[6]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[7]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"   Row[8]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"   Row[9]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS" NodeType="DIRECTORY" OpMode="CREATE"   Row[10]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[11]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[12]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[13]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"   Row[14]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"   Row[15]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[16]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[17]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"   Row[18]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"   Row[19]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"   Row[20]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[21]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"   Row[22]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[23]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"   Row[24]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"   Row[25]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"   Row[26]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[27]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"   Row[28]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"   Row[29]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"   Row[30]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[31]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"   Row[32]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[33]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"   Row[34]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY" failed.

Still have the same error message.
When I look at the log, it fails at some step that tried to copy UNINSAP.EXE to my local drive. It is looking at directory IM01_NT_I386/SAPINST/NT/I386/UNISAP.EXE. This is a path in the "Installation Master" DVD. However, during the intsallation, the installation wizard asked me to insert the RDBMS DVD. I don't know exactly what it means. Anyway, following is a stack trace. See the last line:
MOS-01105 Processing of one or more file system node operations of table
Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='ABP' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF')
Row[0]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"
Row[1]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP" NodeType="DIRECTORY" OpMode="CREATE"
Row[2]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"
Row[3]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"
Row[4]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"
Row[5]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"
Row[6]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[7]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"
Row[8]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"
Row[9]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS" NodeType="DIRECTORY" OpMode="CREATE"
Row[10]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"
Row[11]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"
Row[12]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"
Row[13]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"
Row[14]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"
Row[15]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"
Row[16]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"
Row[17]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"
Row[18]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"
Row[19]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"
Row[20]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"
Row[21]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"
Row[22]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"
Row[23]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"
Row[24]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"
Row[25]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"
Row[26]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[27]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"
Row[28]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"
Row[29]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"
Row[30]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"
Row[31]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"
Row[32]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[33]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"
Row[34]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY"
failed.

Unicode issue jdbc receiver adapter

Hi guys,
I'm facing an unicode issue while trying to put some data into a MS database.
The sender system is a SAP ERP 6.0 system.
When we are trying to transfer some text in polish or korean or something else, this textes are not transferred correctly.
I already checked the SAP Note 831162 FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter
and used the url parameter sendStringParametersAsUnicode=true
Furthermore I changed my mapping to get the sql statements, so that I add the attribute hasQuot="no"
and a leading N in front of the data string as described in the Note and in some threads in SDN
Unicode problem in JDBC receiver adapter
JDBC adapter , problem in inserting Korean Charaters in MS SQL
but nothing solved my problem.
any ideas?
Do all the languages have to be installed on the XI system?
Kind regards
Jochen

Hi Sarvesh,
thanks for helping.
Unfortunately I´m not sure what I should exactly do.
If I get you wright I have to test the mapping using the test functionality in message mapping (test tab).
I did this already
The result message looks like this
<?xml version="1.0" encoding="UTF-8"?>
<ns0:IDOC_CDB_IMPORT_insert xmlns:ns0="http://endress.com/xi/sbo/cdb">
 <ns0:StatementName1>
 <ns0:dbTableName action="insert">
 <ns0:table>CFG.DBO.IDOC_CDB_IMPORT</ns0:table>
 <ns0:access>
 <ns0:IDOC>CHRMAS</ns0:IDOC>
 <ns0:SEGMENT>E1CABTM</ns0:SEGMENT>
 <ns0:ATNAM></ns0:ATNAM>
 <ns0:SPRAS>PL</ns0:SPRAS>
 <ns0:ATBEZ hasQuot="no">N'D?ugo?? ca?kowita Tl; L:'</ns0:ATBEZ>
 </ns0:access>
 </ns0:dbTableName>
 </ns0:StatementName1>
</ns0:IDOC_CDB_IMPORT_insert>
How to proceed?
copy this message to notepad or ultra edit and then doing what?
please specify clearly.
this message will be send to the jbdc adapter and this will insert it to database.
<ns0:ATBEZ hasQuot="no">N'D?ugo?? ca?kowita Tl; L:'</ns0:ATBEZ>
will end up in a table entry like D?ugo?? ca?kowita Tl; L:
has anybody an idea how I will get the wright characters in database, when I test my UDF in eclipse, the variable during debugging has the correct text.
When output this variable via system.ou.print(text); the same issue occurs, the special characters are shown as ?.
I appreciate for your help, unfortunately my polish colleagues hustle a little bit.
kind regards
Jochen

ABAP performance issues and improvements

Hi All,
Pl. give me the ABAP performance issue and improvement points.
Regards,
Hema

Performance tuning for Data Selection Statement
For all entries
The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of
entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the
length of the WHERE clause.
The plus
Large amount of data
Mixing processing and reading of data
Fast internal reprocessing of data
Fast
The Minus
Difficult to program/understand
Memory could be critical (use FREE or PACKAGE size)
Some steps that might make FOR ALL ENTRIES more efficient:
Removing duplicates from the the driver table
Sorting the driver table
 If possible, convert the data in the driver table to ranges so a BETWEEN statement is used instead of and OR statement:
 FOR ALL ENTRIES IN i_tab
 WHERE mykey >= i_tab-low and
 mykey <= i_tab-high.
Nested selects
The plus:
Small amount of data
Mixing processing and reading of data
Easy to code - and understand
The minus:
Large amount of data
when mixed processing isnt needed
Performance killer no. 1
Select using JOINS
The plus
Very large amount of data
Similar to Nested selects - when the accesses are planned by the programmer
In some cases the fastest
Not so memory critical
The minus
Very difficult to program/understand
Mixing processing and reading of data not possible
Use the selection criteria
SELECT * FROM SBOOK.
CHECK: SBOOK-CARRID = 'LH' AND
 SBOOK-CONNID = '0400'.
ENDSELECT.
SELECT * FROM SBOOK
WHERE CARRID = 'LH' AND
 CONNID = '0400'.
ENDSELECT.
Use the aggregated functions
C4A = '000'.
SELECT * FROM T100
WHERE SPRSL = 'D' AND
 ARBGB = '00'.
CHECK: T100-MSGNR > C4A.
C4A = T100-MSGNR.
ENDSELECT.
SELECT MAX( MSGNR ) FROM T100 INTO C4A
WHERE SPRSL = 'D' AND
 ARBGB = '00'.
Select with view
SELECT * FROM DD01L
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
SELECT SINGLE * FROM DD01T
 WHERE DOMNAME = DD01L-DOMNAME
 AND AS4LOCAL = 'A'
 AND AS4VERS = DD01L-AS4VERS
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
SELECT * FROM DD01V
WHERE DOMNAME LIKE 'CHAR%'
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
Select with index support
SELECT * FROM T100
WHERE ARBGB = '00'
 AND MSGNR = '999'.
ENDSELECT.
SELECT * FROM T002.
SELECT * FROM T100
 WHERE SPRSL = T002-SPRAS
 AND ARBGB = '00'
 AND MSGNR = '999'.
ENDSELECT.
ENDSELECT.
Select Into table
REFRESH X006.
SELECT * FROM T006 INTO X006.
APPEND X006.
ENDSELECT
SELECT * FROM T006 INTO TABLE X006.
Select with selection list
SELECT * FROM DD01L
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
ENDSELECT
SELECT DOMNAME FROM DD01L
INTO DD01L-DOMNAME
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
ENDSELECT
Key access to multiple lines
LOOP AT TAB.
CHECK TAB-K = KVAL.
ENDLOOP.
LOOP AT TAB WHERE K = KVAL.
ENDLOOP.
Copying internal tables
REFRESH TAB_DEST.
LOOP AT TAB_SRC INTO TAB_DEST.
APPEND TAB_DEST.
ENDLOOP.
TAB_DEST[] = TAB_SRC[].
Modifying a set of lines
LOOP AT TAB.
IF TAB-FLAG IS INITIAL.
 TAB-FLAG = 'X'.
ENDIF.
MODIFY TAB.
ENDLOOP.
TAB-FLAG = 'X'.
MODIFY TAB TRANSPORTING FLAG
 WHERE FLAG IS INITIAL.
Deleting a sequence of lines
DO 101 TIMES.
DELETE TAB_DEST INDEX 450.
ENDDO.
DELETE TAB_DEST FROM 450 TO 550.
Linear search vs. binary
READ TABLE TAB WITH KEY K = 'X'.
READ TABLE TAB WITH KEY K = 'X' BINARY SEARCH.
Comparison of internal tables
DESCRIBE TABLE: TAB1 LINES L1,
 TAB2 LINES L2.
IF L1 <> L2.
TAB_DIFFERENT = 'X'.
ELSE.
TAB_DIFFERENT = SPACE.
LOOP AT TAB1.
 READ TABLE TAB2 INDEX SY-TABIX.
 IF TAB1 <> TAB2.
 TAB_DIFFERENT = 'X'. EXIT.
 ENDIF.
ENDLOOP.
ENDIF.
IF TAB_DIFFERENT = SPACE.
ENDIF.
IF TAB1[] = TAB2[].
ENDIF.
Modify selected components
LOOP AT TAB.
TAB-DATE = SY-DATUM.
MODIFY TAB.
ENDLOOP.
WA-DATE = SY-DATUM.
LOOP AT TAB.
MODIFY TAB FROM WA TRANSPORTING DATE.
ENDLOOP.
Appending two internal tables
LOOP AT TAB_SRC.
APPEND TAB_SRC TO TAB_DEST.
ENDLOOP
APPEND LINES OF TAB_SRC TO TAB_DEST.
Deleting a set of lines
LOOP AT TAB_DEST WHERE K = KVAL.
DELETE TAB_DEST.
ENDLOOP
DELETE TAB_DEST WHERE K = KVAL.
Tools available in SAP to pin-point a performance problem
 The runtime analysis (SE30)
 SQL Trace (ST05)
 Tips and Tricks tool
 The performance database
Optimizing the load of the database
Using table buffering
Using buffered tables improves the performance considerably. Note that in some cases a stament can not be used with a buffered table, so when using these staments the buffer will be bypassed. These staments are:
Select DISTINCT
ORDER BY / GROUP BY / HAVING clause
Any WHERE clasuse that contains a subquery or IS NULL expression
JOIN s
A SELECT... FOR UPDATE
If you wnat to explicitly bypass the bufer, use the BYPASS BUFFER addition to the SELECT clause.
Use the ABAP SORT Clause Instead of ORDER BY
The ORDER BY clause is executed on the database server while the ABAP SORT statement is executed on the application server. The datbase server will usually be the bottleneck, so sometimes it is better to move thje sort from the datsbase server to the application server.
If you are not sorting by the primary key ( E.g. using the ORDER BY PRIMARY key statement) but are sorting by another key, it could be better to use the ABAP SORT stament to sort the data in an internal table. Note however that for very large result sets it might not be a feasible solution and you would want to let the datbase server sort it.
Avoid ther SELECT DISTINCT Statement
As with the ORDER BY clause it could be better to avoid using SELECT DISTINCT, if some of the fields are not part of an index. Instead use ABAP SORT + DELETE ADJACENT DUPLICATES on an internal table, to delete duplciate rows.

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

ABAP related issues in 4.7 to ECC 6.0 Upgrade

Hi All,
We are in the process of upgrade of SAP 4.7 non unicode to ECC 6.0 non unicode system .
Please let me know what are the things we need to check& what are the issues related to ABAP will encounter in this process.
Please provide the touch points which we need to take care.
Regards,
Reddy

Hi
While doing Upgrade You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.
Some function modules may become obsolete, and some screens will change
and some new fields will be added in the new versions etc.
Also take care of SPAU and SPDD tcodes.
You should be able to know about Unicode concept in sap.
check this
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
also chk these 2 notes in service.sap.com
Technical Upgrade is only a version upgrade without any functionality changes.
The objects that are needed to be upgraded are:
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
You can refer to the below links for more information on technical upgrade:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Regards
Anji

Unicode Issue - Corrupted long texts in Plant Maintenance Work Orders

we're having an issue regarding corrupted texts in a Unicode system. here's the scenario:
- long text came from 4.5b wherein, of course, the japanese characters are viewable either in EN or JA logon
- now, this long text when viewed in our acceptance/testing system which is already, take note, already in unicode long text is garbled. both in EN and JA logon long texts are garbled. we are expecting that since the system is already in unicode it can now support code page for japanese.
(here's the tricky part -- the one seen in the field is properly displayed but when trying to view the complete long text, those that are not in the field are garbled.)
- we also have some scenarios that came from 4.5b, when viewed in the testing system while not unicoded - it's garbled in EN. this is normal since it's still non-unicoded. and of course when viewed using JA logon it's not corrupted anymore. we're expecting that this will also be the same with the issue above. but it's not.
please see link for screenshots. [http://img16.imageshack.us/img16/9760/unicodeissuee.jpg|http://img16.imageshack.us/img16/9760/unicodeissuee.jpg]

i know it's weird.
but then i talked to a friend, she's an abaper. she said that those that can be converted or properly viewed are texts elements in database tables and those that are like free texts or comments can not. and there's no possible way for this but to manually retype everything.
makes sense right.

BI Java and BI ABAP -RSPLAN issue

Hi All
We are working with BI system ,using BI 7.0 Java and BI ABAP as separate systems on same host.
Already run the template intaller for BI Java and ABAP integration.
But facing some issue ,when going ot BI ABAP and RSPLAN and clicking the Start Mideller
it is opening a browser as http://host:8000/sap/public/myssocntl?sap-client-XXX
Since this is not correct and it should open BI Java portal instead of ABAP stack page.
Instead this should open a Url like this http://host:5XX00/webdynpro/dispatcher/sap.com/biplanworkbench1/Modeler?
I check on BI ABAP system under SAP Reference IMG -> SAP Customizing Implementation Guide-> SAP NetWeaver _> Business Intelligence-> BI Integrated Planning -> Settings for Starting the Planning Modeler.
There the default Url is BEx Portal Server and the url is
http://host:5XX00/webdynpro/dispatcher/sap.com/biplanworkbench1/Modeler
Can anybody let me know why this is going to ABAP server instead it should go to Java.
Regards
Ajay
Edited by: Ajay Sandal on Mar 10, 2009 2:31 PM

Hi Ajay ..
Good news that ur issue is resolved ..
I have somewhat similar issue .. Hopu u can put some light ..
I have Bi 7.o with Add on java ,
In RSPLAN from ABAP system , modular page is not coming . if i click on start moduler button in RSPLAN ..portal page is coming up and i have to give logging details .
Please suggest .
Thanks

How to Convert a HEX value to CHAR value...Unicode Issue...

Hi,
How can I convert HEX value to CHAR value.
The Code in non Unicode system is:
DATA: t_text LIKE tline OCCURS 0 WITH HEADER LINE.
constants: c_hex_20a5(2) TYPE x VALUE '20A5'.
t_text-tdline = 'seller of the item so listed. A legend of the Seller Code(s) is as'.
 TRANSLATE t_text-tdline USING c_hex_20a5.
The same code give error in Uni-Code system:
error is "c_hex_20a5 must be an character type object (C, N, D, T or String type)."
If anyone know, what is the solution, please let me know.
Thanks!
Puneet.

Hi,
Try declaring the Hex chars using the ABAP char utilities. This is just a sample piece of code on how to declare and use:
CLASS cl_abap_char_utilities DEFINITION LOAD.
DATA: ws_lf TYPE c VALUE cl_abap_char_utilities=>cr_lf.
data: c_newline TYPE x VALUE '0D'. [ it is zero D, for carriage return ]
ws_lf = c_newline.
 CONCATENATE it_tab-maktx
 ws_lf
 ws_template
 INTO it_notificatn-template.
Hope this helps...
Regards
Subramanian

Windows 8.1 Pro Non-Unicode Issue: CS6 Standard

I use WIndows 8.1 Pro English, I installed the CS6 Standard in Spanish, I changed the language for the non-unicode programs to spanish but still cannot use the Illustrator, I am having issue only with the Illustrator, noting that in the installation I was prompt for Spanish(Latin America) or Just Spanish, I clicked on Spanish(Latin America), but in the non-Unicode languages there is no Spanish(non-Unicode) they have Spanish per countries.

I have the same problem did you manage to find the solution? is impossible to contact adobe helpers, they just hide all contact

ABAP Dump issue while accessing Gateway

Hi
We have recently upgraded our Gateway server to SP03. Eversince after service generation while accessing the XML/Metadata from the consumption page we get an HTTP error with Dump. Has anyone faced this problem before.
<?xml version="1.0" encoding="utf-8" ?>
- <error xmlns:xsi="http://www.w3.org/2001/XMLSchema-Instance">
<code>HTTP/500/E/Internal Server Error</code>
<message>Call of service /sap/opu/sdata/sap/Z14335_RFC_BP_1/ terminated because of an error. The following error text was processed in system AC1 : Syntax error in program /IWCOR/CL_REST_HTTP_HANDLER===CP .The error occurred on the application server njsapnet3. The termination type was: RABAX_STATE.If the termination type is RABAX_STATE, you will find more information on the cause of termination in system AC1 in transaction ST22. If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server njsapnet3 in transaction SM21. If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process in transaction ST11 on the application server njsapnet3. You may also need to analyze the trace files of other work processes. If you do not yet have a user ID, contact your system adminmistrator.</message>
</error>

Hi All,
I am also facing the same issue.
When i am executing query/read operation my service it will works properly and getting data also,but when i am trying get X-CSRF token it throws error(ABAP Dump) .Can you please help me out this issue.
Based on the Tx: ST11..getting below log.
A ABAP Program /IWCOR/CL_REST_HTTP_HANDLER===CP .
A Source /IWCOR/CL_REST_HTTP_HANDLER===CCIMP Line 40.
A Error Code ASSERTION_FAILED.
A Module abassert.c.
A Function ab_aabAssertionFailedRabax Line 1880.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
N
N Thu Jan 03 15:00:58 2013
N *** ERROR => System ID and client from ticket are not the same than mine. [ssoxxkrn.c 1065]
N {root-id=0050569E07B31ED295B108EAC1527575}_{conn-id=0050569E07B31ED295B108EABC707575}_1
N *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL (see note 1055856). [ssoxxkrn.c 1071]
N {root-id=0050569E07B31ED295B108EAC1527575}_{conn-id=0050569E07B31ED295B108EABC707575}_1
i am getting based on Tx:ST22
Category
ABAP Programming Error
Runtime Errors
ASSERTION_FAILED
ABAP Program
/IWCOR/CL_REST_HTTP_HANDLER===CP
Application Component OPU-FND-CCL
Note: I am using SAP NW-GW-SP04
Thanks,
Syam

ABAP WP Issue in SAP MMC

Dear Guru's,
After upgrading kernel 133 in our solution manager, we're unable to see anything in ABAP WP Table of SAP MMC. But, we are able to login to SAP and work on it.
Closed and reopened the MMC, still we are facing the issue.
Kindly suggest what could be the reason.
regards,
Guna

>
BasisGuna wrote:
> Dear Guru's,
>
> After upgrading kernel 133 in our solution manager, we're unable to see anything in ABAP WP Table of SAP MMC. But, we are able to login to SAP and work on it.
>
> Closed and reopened the MMC, still we are facing the issue.
>
> Kindly suggest what could be the reason.
>
> regards,
>
> Guna
Hello Guna,
Have you checked if sapmmc. dlls have the same version of disp+work.exe files from your new kernel? pls try to keep them consistent and register them for new versions.
Else please first try to reboot the whole server after updating kernel.
Regards
Amit

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.

ABAP program issue

Dear All,
I have written an ABAP program by which it writes few things on application server (overwrite mode).
I have included this program in the Process Chain but it is giving dump first time when it is running "DATASET_NOT_OPEN" whereas the path and all directories are created on application server.
When i try to repeat the process chain it is running successfully.
Please help on the same.
Regards,
SS

Check these links.
Re: SHORT DUMP! Exception: CX_SY_FILE_OPEN_MODE
CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test
Re: catching an exception 'CX_SY_FILE_OPEN_MODE'
Re: Issue in Uploading file to application server
Thanks.

ABAP coding issues after BW upgrade

Hello Gurus,
We recently did a BW upgrade from version 3.5 to 7.31 and even since have been encountering few strange issues with many of our ABAP coding.
For example, there is an APPEND statement in one of our Update Rules as below:
APPEND <lw_rtab_wa> TO <lt_rtab>.
Before upgrade, this was working as expected and the contents of <lw_rtab_wa> was getting transferred to <lt_rtab> without any issues.
Now after upgrade, we find that the contents of <lw_rtab_wa> is being clubbed together in the 1st few columns of <lt_rtab>.
Both the <lw_rtab_wa> & <lt_rtab> have the same fields, but the length of few fields in <lt_rtab> is bigger than that in <lw_rtab_wa>. For example DOC_NUMBER in <lw_rtab_wa> is of type C(10) while in <lt_rtab> it is C(20). This difference is causing the data of the 2nd field also to be over-writen in the DOC_NUMBER field of <lt_rtab>.
Please let us know if you have encountered similar situations after your BW upgrade. Any possible solutions to this would be very much appreciated as this is causing PROD issues at the moment!
Thanks
Arvind

Hi Arvind,
After Upgrade In BW 7.3 or higher versions All data elements that use the domain RSCHAVL are converted from CHAR60 to SSTRING. thats the reason you are getting that syntax error.
Take help of some ABAP programmer and try to change the syntax as suggested from below link.
Just scroll down and check the same. even though link shows for BW 7.4 issues, its applicable for 7.3 too. Please let me know
http://scn.sap.com/community/data-warehousing/bw/blog/2014/07/28/sap-bw-74-analysis-issues
Thanks
Ajay

ABAP Unicode issue...

Similar Messages

Maybe you are looking for