Exec sqlplus process error in character conversion

Hello,
Having problems loading data using sqlplus_exec_template.sql. I'm trying to load data by executing PROCESS
REPO RT USER = Rtm_access
repo rt OWNER = RTM
locatie wf = WFM_RTM
PROCESS = INI
PROCESS FLOW PACKAGE = MIRO0
this is the command from the dos prompt
sqlplus rtm_access/rtm_access@miro @c:\owbdeploy\sqlplus_exec_template.sql RTM WFM_RTM PROCESS INI MIRO0 ","
In a spool script I'll get the next output
Session altered.
Role set.
ERROR:
ORA-24365: error in character conversion
I also tried the command with system_params = ",". Then I
got the same output error.
Can you help me ?
My best regards
Aad van der Kooij

Mark,
I also tried the command without the process flow package,
sqlplus rtm_access/rtm_access@miro @c:\owbdeploy\sqlplus_exec_template.sql RTM WFM_RTM PROCESS INI "," ","
The problem also exists when I want to execute a mapping in sqlplus:
sqlplus rtm_access/rtm_access@miro @c:\owbdeploy\sqlplus_exec_template.sql RTM STG_TRG_LOC PLSQL SMA_REF_LAND "," ","
I forget to tell you the versions of OWB (9.2.0.2.8) en
SQLPLUS (8.0). Could this be the reason of the error.
My best regards,
Aad van der Kooij

Similar Messages

Error occurred during character conversion in SXMB_MONI

Hello Experts,
Good Day!
I would like to seek your help here. When i used tcode SXMB_MONI to search for messages i get this error : Error occurred during character conversion.
So far no problem with the program. Its work for all other dates. Just for one particular day and specific time period, im geting this error.
Does anyone know what is this error means? Please reply..
Thanks for your help.
Looking forward for ur replies..

Hi Presheela,
Basically this problem occurs when ur payload contains any special characters like '&' ,'>'...etc .So you have to take care of how to deal with these characters in XI.
Refer the following documentation:
How to Work with Character Encodings in Process Integration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Regards,
Vinod.

Character conversion error: "Unconvertible UTF-8 character beginning with 0

Hi All,
I developed an Adapter Module and added to Adapter Framework.
package sample;
import java.io.InputStream;
import java.text.SimpleDateFormat;
import java.util.Date;
import javax.ejb.CreateException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NodeList;
import com.sap.aii.af.mp.module.Module;
import com.sap.aii.af.mp.module.ModuleContext;
import com.sap.aii.af.mp.module.ModuleData;
import com.sap.aii.af.mp.module.ModuleException;
import com.sap.aii.af.ra.ms.api.Message;
import com.sap.aii.af.ra.ms.api.XMLPayload;
@ejbHome <{com.sap.aii.af.mp.module.ModuleHome}>
@ejbLocal <{com.sap.aii.af.mp.module.ModuleLocal}>
@ejbLocalHome <{com.sap.aii.af.mp.module.ModuleLocalHome}>
@ejbRemote <{com.sap.aii.af.mp.module.ModuleRemote}>
@stateless
public class SetAttachmentName implements SessionBean, Module {
     private SessionContext myContext;
     private String mailFileName = "UStN";
     public void ejbRemove() {
     public void ejbActivate() {
     public void ejbPassivate() {
     public void setSessionContext(SessionContext context) {
          myContext = context;
     public void ejbCreate() throws CreateException {
     public ModuleData process(
          ModuleContext moduleContext,
          ModuleData inputModuleData)
          throws ModuleException {
          // create a second attachment for the receiver mail adapter
          try {
               //                  get the XI message from the environment
               Message msg = (Message) inputModuleData.getPrincipalData();
               //               creating parsable XML document
               InputStream XIStreamData = null;
               XMLPayload xmlpayload = msg.getDocument();
               XIStreamData = xmlpayload.getInputStream();
               DocumentBuilderFactory docBuilderFactory =
                    DocumentBuilderFactory.newInstance();
               DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
               Document doc = docBuilder.parse(XIStreamData);
               //            finding the tag's name from the Modules tab in the Directory that will hold the attachment's name
               String absenderIDTag = null;
               absenderIDTag = moduleContext.getContextData("<RCVPRN>");
               //            finding the content of the tag that will be used as the attachment's name (assuming it's the only tag with this name)
               Element element = doc.getDocumentElement();
               NodeList list = doc.getElementsByTagName(absenderIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().toString();
               String anIDTag = null;
               anIDTag = moduleContext.getContextData("<CREDAT>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(anIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().toString();
               Date date = new Date(System.currentTimeMillis());
               //            Add date to the Message
               SimpleDateFormat dateFormat = new SimpleDateFormat("yyyyMMdd");
               mailFileName += "_" + dateFormat.format(date);
               String belegNummerTag = null;
               belegNummerTag = moduleContext.getContextData("<BULK_REF>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(belegNummerTag);
               mailFileName += "_" + list.item(0).getFirstChild().toString();
               //               creating the attachment
               byte by[] = xmlpayload.getText().getBytes();
               XMLPayload attachmentPDF = msg.createXMLPayload();
               attachmentPDF.setName(mailFileName);
               attachmentPDF.setContentType("application/pdf");
               attachmentPDF.setContent(by);
               //adding the message to the attachment
               msg.addAttachment(attachmentPDF);
               //                  provide the XI message for returning
               inputModuleData.setPrincipalData(msg);
          } catch (Exception e) {
               //                  raise exception, when an error occurred
               ModuleException me = new ModuleException(e);
               throw me;
          //                  return XI message
          return inputModuleData;
I get the following error
Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
Any tips, pointers ?
Thanks in Advance
Mukhtar

Hi Henrique,
I am using .getNodeValue()
import java.io.InputStream;
import java.text.SimpleDateFormat;
import java.util.Date;
import javax.ejb.CreateException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NodeList;
import com.sap.aii.af.mp.module.*;
import com.sap.aii.af.ra.ms.api.*;
@ejbHome <{com.sap.aii.af.mp.module.ModuleHome}>
@ejbLocal <{com.sap.aii.af.mp.module.ModuleLocal}>
@ejbLocalHome <{com.sap.aii.af.mp.module.ModuleLocalHome}>
@ejbRemote <{com.sap.aii.af.mp.module.ModuleRemote}>
@stateless
public class UStNAttachmentName3 implements SessionBean, Module {
     private SessionContext myContext;
     private String mailFileName = "UStN";
     public void ejbRemove() {
     public void ejbActivate() {
     public void ejbPassivate() {
     public void setSessionContext(SessionContext context) {
          myContext = context;
     public void ejbCreate() throws CreateException {
     public ModuleData process(
          ModuleContext moduleContext,
          ModuleData inputModuleData)
          throws ModuleException {
          // create a second attachment for the receiver mail adapter
          try {
               // get the XI message from the environment
               Message msg = (Message) inputModuleData.getPrincipalData();
               // creating parsable XML document
               InputStream XIStreamData = null;
               XMLPayload xmlpayload = msg.getDocument();
               XIStreamData = xmlpayload.getInputStream();
               DocumentBuilderFactory docBuilderFactory =
                    DocumentBuilderFactory.newInstance();
               DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
               Document doc = docBuilder.parse(XIStreamData);
               // finding the tag's name from the Modules tab in the Directory that will hold the attachment's name
               String absenderIDTag = null;
               absenderIDTag = moduleContext.getContextData("<RCVPRN>");
               // finding the content of the tag that will be used as the attachment's name (assuming it's the only tag with this name)
               Element element = doc.getDocumentElement();
               NodeList list = doc.getElementsByTagName(absenderIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
               String anIDTag = null;
               anIDTag = moduleContext.getContextData("<CREDAT>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(anIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
               Date date = new Date(System.currentTimeMillis());
               // Add date to the Message
               SimpleDateFormat dateFormat = new SimpleDateFormat("yyyyMMdd");
               mailFileName += "_" + dateFormat.format(date);
               String belegNummerTag = null;
               belegNummerTag = moduleContext.getContextData("<BULK_REF>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(belegNummerTag);
               mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
               // creating the attachment
               byte by[] = xmlpayload.getText().getBytes();
               XMLPayload attachmentPDF = msg.createXMLPayload();
               attachmentPDF.setName(mailFileName);
               attachmentPDF.setContentType("application/pdf");
               attachmentPDF.setContent(by);
               //adding the message to the attachment
               msg.addAttachment(attachmentPDF);
               // provide the XI message for returning
               inputModuleData.setPrincipalData(msg);
          } catch (Exception e) {
               // raise exception, when an error occurred
               ModuleException me = new ModuleException(e);
               throw me;
          // return XI message
          return inputModuleData;
Still I get the same error.
org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
Adapter-Framework: Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
Regards,
Mukhtar

SMQ2 (Inbound Queue) : Error occurred during character conversion

Hi,
In SMQ2 an Inbound Queue has failed with status text "Error occurred during character conversion". The XML message inside this queue is in waiting status with status text " Scheduled for Outbound Processing" .
Even after cancelling this message from SXMB_MONI, and reposting the PO, still again the queue and the XML message inside the queue are in same status.
As this is in XI production system, requesting to provide some suggestion ASAP.
Thanks,
Mateen.

The queue status is still sysfail. There is only 1 message waiting in the queue.
I think that the queue might be locked for some reason and after unlocking the queue and restarting the message, the message will get processed successfully.
But before working on this I want to make sure that the queue is locked.
Do you or anyone else know how and from where can I check whether the queue is locked or unlocked?
Regards,
Mateen.

Character conversion error when installing Java Portlet Container Preview

I'm trying to tets out JSR 168 portlets on our Oracle 10g server. I'm following the instructions at http://portalstandards.oracle.com/
I download and try to install the "Java Portlet Container Preview Release 2", and I get the following error:
[oracle@jupiter home]$ java -jar ~/wsrp-install.jar ~/jwsdp-1.3
File "/home/oracle/jupiter_mid/j2ee/home/config/global-web-application.xml" modified successfully
oracle.webdb.utils.PortalExceptionImpl: Error transforming file "config/server.xml"
at oracle.portal.PortalException.<init>(PortalException.java:66)
at oracle.webdb.wsrp.server.install.InstallException.<init>(InstallException.java:31)
at oracle.webdb.wsrp.server.install.Main.applyTransformation(Main.java:387)
at oracle.webdb.wsrp.server.install.Main.install(Main.java:122)
at oracle.webdb.wsrp.server.install.Main.main(Main.java:98)
Caused by: javax.xml.transform.TransformerException: Character conversion error: "Unconvertible UTF-8 character beginning with 0x92" (line number may be too low).
at org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:739)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:715)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1129)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1107)
at oracle.webdb.wsrp.server.install.Main.applyTransformation(Main.java:371)
... 2 more
caused by: ; SystemID: http://xmlns.oracle.com/ias/dtds/application-server-9_04.dtd; Line#: 1; Column#: -1
javax.xml.transform.TransformerException: Character conversion error: "Unconvertible UTF-8 character beginning with 0x92" (line number may be too low).
at org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:739)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:715)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1129)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1107)
at oracle.webdb.wsrp.server.install.Main.applyTransformation(Main.java:371)
at oracle.webdb.wsrp.server.install.Main.install(Main.java:122)
at oracle.webdb.wsrp.server.install.Main.main(Main.java:98)
[oracle@jupiter home]$
This is what the server.xml looks like:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!DOCTYPE application-server PUBLIC "-//Oracle//DTD OC4J Application-server 9.04//EN" "http://xmlns.oracle.com/ias/dtds/application-server-9_04.dtd">
<application-server localhostIsAdmin="true"
application-directory="../applications"
deployment-directory="../application-deployments"
connector-directory="../connectors">
<rmi-config path="./rmi.xml" />
<sep-config path="./internal-settings.xml" />
<jms-config path="./jms.xml" />
<javacache-config path="../../../javacache/admin/javacache.xml" />
<log>
<file path="../log/server.log" />
</log>
<transaction-config timeout="30000" />
<java-compiler name="javac" in-process="false" extdirs="/home/oracle/jupiter_mid/jdk/jre/lib/ext" />
<global-application name="default" path="application.xml" />
<application name="BC4J" path="../applications/BC4J.ear" auto-start="true" />
<application name="BC4JManager" path="../applications/BC4JManager.ear" auto-start="true" />
<application name="IsWebCacheWorking" path="../applications/IsWebCacheWorking.ear" auto-start="true" />
<application name="jdev_test2" path="../applications/jdev_test2.ear" auto-start="true" />
<global-web-app-config path="global-web-application.xml" />
<web-site default="true" path="./default-web-site.xml" />
<cluster id="1214162165" />
</application-server>
server.xml looks ok, and I've tried tweaking it to no avail. Anyone know what could cause this?

Could you make sure you don't have any extra Apache libraries hanging around in your global classpath, i.e. ensure there is nothing extra in <J2SE Home>/jre/lib/extThere's a xercesImp.jar under mid/j2ee/OC4J_Portal/applications/jpdk/jpdk/WEB-INF/lib/xercesImpl.jar, but there's also one under jwsdp-1.2/jaxp/lib/endorsed/xercesImpl.jar. Is that supposed to be in there?
Neither of these are getting loaded, though; running java -verbose shows that all of org.apache.xalan.* is being loaded from mid/jdk/jre/lib/rt.jar
FWIW, ../../lib/xmlparserv2.jar does exist, but doesn't look like it's being loaded. :-\

Character conversion error

Hi all,
We are getting the following error when trying to parse an xml string resource - Character conversion error: "Illegal ASCII character, 0xc2" (line number may
be too low)-. We have not been able to get around this. We have tried creating the InputSource two different ways:
reader = new StringReader(stringSource);
src = new InputSource( reader );
and
src = new InputSource(new InputStreamReader(new ByteArrayInputStream(stringSource.getBytes())));
The problem does appear to go away if we treat the DTD we are validating against as a file. If we set it has a uri, we get the above problem.
Is anyone else experiencing this problem?
Any help would be greatly appreciated.
Thanks in advance,
Greg

Hi,
2 possible solutions:
1) try using the xerces parser instead of sun's parser
2) look at the posting at the following url and see wether the posted solution solves your problem: http://forums.java.sun.com/thread.jsp?forum=34&thread=67558
Hope this helps,
Kurt.

"character conversion error" while parsing xml files

Hello,
I'm trying to parse MusicXML (Recordare) files, but I'm getting an exception.
I'm using the SAX parser (javax.xml.parsers.SAXParser).
Here is the code I use to instantiate it:
final javax.xml.parsers.SAXParserFactory saxParserFactory = javax.xml.parsers.SAXParserFactory.newInstance();
final javax.xml.parsers.SAXParser saxParser = saxParserFactory.newSAXParser();
final org.xml.sax.XMLReader parser = saxParser.getXMLReader();
I'm using my own handler, but I get the same exception even if I use org.xml.sax.helpers.DefaultHandler.
The error I get is:
Character conversion error: "Illegal ASCII character, 0xc2" (line number may be too low).
The first few lines of my xml files look like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE score-partwise
PUBLIC "-//Recordare//DTD MusicXML 0.6 Partwise//EN"
"http://www.musicxml.org/dtds/partwise.dtd">
<score-partwise>
[...etc...]
If I delete the <!DOCTYPE ...> line, then I don't get the exception anymore. But the MusicXML files I get (from some other program) always contain this line, and it would be quite some work to delete them from every file manually.
So does anyone know if there is a way to avoid deleting that line in every file, while still being able to parse the xml files without exceptions?
Or maybe does anyone know what the exact cause of the exception is? (because I don't know what exactly causes it)
Thank you in advance.
Greetz,
Jipo

So does anyone know if there is a way to avoid
deleting that line in every file, while still being
able to parse the xml files without exceptions?ok this is side-stepping the real problem but I've used this code to filterout DTD references for other reasons   public static InputStream filterOutDTDRef(InputStream in) throws IOException {
      BufferedReader iniReader = new BufferedReader(new InputStreamReader(in));
      StringBuffer newXML = new StringBuffer();
      for(String line = iniReader.readLine(); line!=null; line = iniReader.readLine())
         newXML.append(line+"\n");
      in.close();
      int s = newXML.indexOf("<!DOCTYPE ");
      if(s!=-1)
         newXML.replace(s,newXML.indexOf(">",s)+1,"");
      return new ByteArrayInputStream(newXML.toString().getBytes());
   }and it actually speeds up the parsing phase too (since the DTD ref.s were on the web and the XML standard mandates that there is a fetch for each xml file parsed..)
you can feed the above into the InputSource constructor that takes an InputStream argument.
Now for the real problem... 0xc2 is "LATIN CAPITAL LETTER A WITH CIRCUMFLEX" according to a unicode chart - which is not an ASCII character (as the error message correctly reports). I'm not sure why the file is being parsed as ASCII though? You could try parsing in a FileReader to the inputsource and hope it picks up the default character encoding of your system, and that that character encoding matches the file. Or you could try passing in a FileReader constructed with a explicit character encoding (eg "UTF8") and see if that does the trick?
asjf

Character conversion error: Unconvertible UTF-8 character beginning..

Hello,
I'm using TrAX for XSLT transformations, and having a following
problem
Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
        at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
        at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
        at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
        at org.apache.crimson.parser.Parser2.maybeTextDecl(Parser2.java:2795)
        at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.java:2880)
        at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1167)
        at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:489)
        at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
        at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
        at mlts.converter.XMLImport.outputESGML(XMLImport.java:311)
        at mlts.converter.Converter.processFile(Converter.java:312)
        at mlts.converter.Converter.Convert(Converter.java:229)
        at test.main(test.java:7)Following the source code, I've found that the exception is thrown
when it reads DTD. I tried to read DTD using InputSource
in ascii, in latin-1 and my program reads it without any problem.
I really appreciate any help,
Thanks

http://forum.java.sun.com/thread.jsp?forum=34&thread=254927

SAXParseException: character conversion error: Illegal character 0x9A...

This is my problem:
I use JDom to parse remote XML document with DTD linked to it. But I get that error. Request is:
SAXBuilder builder = new SAXBuilder();
Document doc = builder.build(new URL(url));
This works fine when I use these XML and DTD docs locally, which means that I give xml file name as a parameter from console. Then everything goes well. But when I move my program to server and try to run it there, SAXParseException is thrown. Why???
Error is:
error on line 1 of document "http://server.net/doc.dtd" Character conversion error: Illegal ASCII character 0x9A (line number may be too low)
What this means? And why this just happens when I run program in server? Help, please
tia J_J

Exactly that's the problem.
String class :
* This class is implemented to map an ordinary java.lang.String
* into an xml compliant String
public class String2Xml
     private final String invalidChars [] = {"�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "`",
                                                       "�",
                                                       "<",
                                                       ">",
     private final String replaceChars [] = {"��",
                                                       "ß",
                                                       "ä",
                                                       "ö",
                                                       "ü",
                                                       "Ä",
                                                       "Ö",
                                                       "Ü",
                                                       "§",
                                                       "",
                                                       "`",
                                                       "´",
                                                       "<",
                                                       ">",
                                                       "'"};
     * Constructor
     public String2Xml();
     * This operation is implemented to check if the given String
     * matches one of the invalidChars. If an invalid char is found
     * it'll be replaced.
     * @return String - the correct xml String
     public String checkString(String check)
          for (int i = 0; i < invalidChars.length; i++)
               check = check.replaceAll(invalidChars, replaceChars[i]);
          System.out.println("Check : " + check);
          return check;

Printing ZPL (Zebra) data to printer spooler without character conversion

Hi all,
We are printing shipping labels from UPS, with a process where we recive the ZPL label code directly from UPS, and we just need to pass the data to the printer to get the labels. We have already implemented this with Fedex and some custom labels, and it works perfectly. The problem with the UPS label data is that it contains non-printable characters (in the MaxiCode data field). When passed to the SAP printer spooler (see code example below), the data gets corrupted because SAP interprets these non-printable characters as printer control codes.
I have verified this by saving the ZPL data to a local file, before printing it through the SAP spooler. I then print this raw data and compare the output with the labels printed from the spooler. The MaxiCode (the big 2D barcode) is different in these labels. UPS has also tested the labels, and rejected them because of incorrect data in the barcode.
For printing, we are using printers defined as type "PLAIN", but I also tried using the "LZEB2" device type with the same result. The error we see in the spooler entry is this:
Print ctrl S_0D_ is not defined for this printer. Page 1, line 2, col. 2201
Print output may not be as intended
The printer ctrl code differs, depending om the label. I have examined the spooler data in "raw" mode, and there is always an ASCII character 28 (hex 1C) in front of the characters that SAP think are control codes, and this is why I think these non-printable characters are the reason for the problems.
This is the function module I use to print the ZPL data (and as stated above, this works fine for Fedex and custom labels). The ZPL data is converted to binary format before passed to the function module, but I also tried to send the data in text format with another FM, but the result is the same. I have experimented with the "codepage" parameter, and this one gives the least amount of errors, and some labels actually get through without errors. But still at least 50% of the labels gets corrupted, with log entries like above.
CALL FUNCTION 'RSPO_SR_WRITE_BINARY'
      EXPORTING
        handle           = lv_spool_handle
        data             = lv_label_line_bin
        length           = lv_len
        codepage         = '2010'
      EXCEPTIONS
        handle_not_valid = 1
        operation_failed = 2
        OTHERS           = 3.
Does anyone know if there is a way to send data to the spooler without character conversion or interpretation of printer control codes? Or is there any other smart way to get around this problem?
/Leif

I do a more direct output to the spooler, to avoid any issues with the WRITE statement and SAP's report output processing. At the same time, I insert line breaks so that the output is easy to debug in the spooler if needed. Also included is the code to to detect the escape code (ASCII #28) and to insert a control code ZZUPS in its place (you can skip this for Fedex). Here's a simplified example, but please note this is for a Unicode system, some minor changes is required in a non-Unicode system.
CONSTANTS: lc_spcode TYPE c LENGTH 5 VALUE 'ZZUPS',
           lc_xlen TYPE i VALUE 5.
   DATA: lv_print_params TYPE pri_params,
         lv_spool_handle TYPE sy-tabix,
         lv_name TYPE tsp01-rq0name,
         lv_spool_id TYPE rspoid,
         lv_crlf(2) TYPE c,
         lv_lf TYPE c,
         lstr_label_data TYPE zship_label_data_s,
         lv_label_line TYPE char512,
         lv_label_line_bin TYPE x LENGTH 1024,
         lv_len TYPE i,
         ltab_label_data_255 TYPE TABLE OF char512,
         ltab_label_data TYPE TABLE OF x,
         lv_c1 TYPE i,
         lv_c2 TYPE i,
         lv_cnt1 TYPE i,
         lv_cnt2 TYPE i,
         lv_x(2) TYPE x.
   FIELD-SYMBOLS: <n> TYPE x.
   lv_crlf = cl_abap_char_utilities=>cr_lf.
   lv_lf = lv_crlf+1(1).
   lv_name = 'ZPLLBL'.
CALL FUNCTION 'RSPO_SR_OPEN'
     EXPORTING
       dest                   = i_dest
       name                   = lv_name
       prio                   = '5'
       immediate_print        = 'X'
       titleline              = i_title
       receiver               = sy-uname
*      lifetime               = '0'
       doctype                = ''
     IMPORTING
       handle                 = lv_spool_handle
       spoolid                = lv_spool_id
     EXCEPTIONS
       device_missing         = 1
       name_twice             = 2
       no_such_device         = 3
       operation_failed       = 4
       OTHERS                 = 5.
   IF sy-subrc <> 0.
     RAISE spool_open_failed.
   ENDIF.
LOOP AT i_label_data INTO lstr_label_data.
     CLEAR ltab_label_data_255.
     SPLIT lstr_label_data-label_data AT lv_lf INTO TABLE ltab_label_data_255.
     LOOP AT ltab_label_data_255 INTO lv_label_line.
       IF lv_label_line NE ''.
         lv_len = STRLEN( lv_label_line ).
*       Convert character to hex type
         lv_c1 = 0.
         lv_c2 = 0.
         DO lv_len TIMES.
           ASSIGN lv_label_line+lv_c1(1) TO <n> CASTING.
           MOVE <n> TO lv_x.
           IF lv_x = 28.
             lv_cnt1 = 0.
             lv_label_line_bin+lv_c2(1) = lv_x.
             lv_c2 = lv_c2 + 1.
             DO lc_xlen TIMES.
               ASSIGN lc_spcode+lv_cnt1(1) TO <n> CASTING.
               MOVE <n> TO lv_x.
               lv_cnt2 = lv_c2 + lv_cnt1.
               lv_label_line_bin+lv_c2(2) = lv_x.
               lv_c2 = lv_c2 + 2.
               lv_cnt1 = lv_cnt1 + 1.
               lv_len = lv_len + 1.
             ENDDO.
           ELSE.
             lv_label_line_bin+lv_c2(2) = lv_x.
             lv_c2 = lv_c2 + 2.
           ENDIF.
           lv_c1 = lv_c1 + 1.
         ENDDO.
*       Print binary data to spool
         lv_len = lv_len * 2. "Unicode is 2 bytes per character
         CALL FUNCTION 'RSPO_SR_WRITE_BINARY'
           EXPORTING
             handle                 = lv_spool_handle
             data                   = lv_label_line_bin
             LENGTH                 = lv_len
           EXCEPTIONS
             handle_not_valid       = 1
             operation_failed       = 2
             OTHERS                 = 3.
         IF sy-subrc <> 0.
           RAISE spool_write_failed.
         ENDIF.
       ENDIF.
     ENDLOOP.
   ENDLOOP.
   CALL FUNCTION 'RSPO_SR_CLOSE'
     EXPORTING
       handle = lv_spool_handle.
   IF sy-subrc <> 0.
     RAISE spool_close_failed.
   ENDIF.

Property List error: Unexpected character b at line 1 / JSON error: JSON text did not start with array or object and option to allow fragments not set.

Hi,
I have a MBP 13' Late 2011 and Yosemite 10.10.2 (14C1514).
Until yesterday, I was using Garmin ConnectIQ SDK and all was working fine.
Yesterday, I've updated my system with latest security updates and Xcode updates too (Version 6.2 (6C131e)).
Since, I can't launch the ConnectIQ simulator app, I have this message in console :
8/04/2015 15:19:04,103 mds[38]: There was an error parsing the Info.plist for the bundle at URL Info.plist -- file:///Volumes/Leto/connectiq-sdk-mac-1.1.0_2/ios/ConnectIQ.bundle/
The data couldn’t be read because it isn’t in the correct format.
<CFBasicHash 0x7fa64f44e9a0 [0x7fff7dfc7cf0]>{type = immutable dict, count = 2,
entries =>
0 : <CFString 0x7fff7df92580 [0x7fff7dfc7cf0]>{contents = "NSDebugDescription"} = <CFString 0x7fa64f44f0a0 [0x7fff7dfc7cf0]>{contents = "Unexpected character b at line 1"}
1 : <CFString 0x7fff7df9f5e0 [0x7fff7dfc7cf0]>{contents = "kCFPropertyListOldStyleParsingError"} = Error Domain=NSCocoaErrorDomain Code=3840 "The data couldn’t be read because it isn’t in the correct format." (Conversion of string failed.) UserInfo=0x7fa64f44eda0 {NSDebugDescription=Conversion of string failed.}
I have looked at this file and it looks like a binary plist
bplist00ß^P^V^A^B^C^D^E^F^G^H
^K^L^M^N^O^P^Q^R^S^T^U^V^W^X^Y^Z^[^\^]^^^_ !"$%&'()'+,^[\CFBundleNameWDTXcodeYDTSDKName_^P^XNSHumanReadableCopyrightZDTSDKBuild_^P^YCFBundleDevelopmentRegion_^P^OCFBundleVersi on_^P^SBuildMachineOSBuild^DTPlatformName_^P^SCFBundlePackageType_^P^ZCFBundleShortVersionString_^P^ZCFBundleSupportedPlatforms_^P^]CFBundleInfoDictionaryVersion_^P^RCFBundleE xecutableZDTCompiler_^P^PMinimumOSVersion_^P^RCFBundleIdentifier^UIDeviceFamily_^P^QDTPlatformVersion\DTXcodeBuild_^P^QCFBundleSignature_^P^ODTPlatformBuildYConnectIQT0611[iph oneos8.1o^P-^@C^@o^@p^@y^@r^@i^@g^@h^@t^@ ^@©^@ ^@2^@0^@1^@5^@ ^@G^@a^@r^@m^@i^@n^@.^@ ^@A^@l^@l^@ ^@r^@i^@g^@h^@t^@s^@ ^@r^@e^@s^@e^@r^@v^@e^@d^@.V12B411RenQ1V14C109Xiphoneos TBNDLS1.0¡#XiPhoneOSS6.0YConnectIQ_^P"com.apple.compilers.llvm.clang.1_0S8.1_^P^Tcom.garmin.ConnectIQ¡*^P^AW6A2008aT????^@^H^@7^@D^@L^@V^@q^@|^@<98>^@ª^@À^@Ï^@å^A^B^A^_^A?^AT^ A_^Ar^A<87>^A<96>^Aª^A·^AË^AÝ^Aç^Aì^Aø^BU^B\^B_^Ba^Bh^Bq^Bv^Bz^B|^B<85>^B<89>^B<93>^B¸^B¼^BÓ^BÕ^B×^Bß^@^@^@^@^@^@^B^A^@^@^@^@^@^@^@-^@^@^@^@^@^@^@^@^@^@^@^@^@^@^Bä
I guess it is a normal format but my system seems to be unable to read binary plist ?
I tried some stuff with plutil
plutil -lint Info.plist
Info.plist: Unexpected character b at line 1
Same for convert
plutil -convert xml1 Info.plist
Info.plist: Property List error: Unexpected character b at line 1 / JSON error: JSON text did not start with array or object and option to allow fragments not set.
I also try to download a fresh version of the connectIQ SDK and no changes.
Any idea ?
Thanks

Step by step, how did you arrive at seeing this agreement?

Character conversion problems when calling FM via RFC from Unicode ECC 6.0?

Hi all,
I faced a Cyrillic character convertion problem while calling an RFC function from R/3 ECC 6.0 (initialized as Unicode system - c.p. 4103). My target system is R/3 4.6C with default c.p. 1500.
The parameter I used in my FM interface in target system is of type CHAR10 (single-byte, obviously).
I have defined rfc-connection (SM59) as an ABAP connection and further client/logon language/user/password are supplied.
The problem I faced is, that Cyrillic symbols are transferred as '#' in the target system ('#' is set as default symbol in RFC-destination definition in case character convertion error is met).
Checking convertions between c.p. 4103 and target c.p. 1500 in my source system using tools of transaction i18n shows no errors - means conversion passed O.K. It seems default character conversion executed by source system whithin the scope of RFC-destination definition is doing something wrong.
Further, I played with MDMP & Unicode settings whithin the RFC-destination definition with no successful result - perhaps due to lack of documentation for how to set and manage these parameters.
The question is: have someone any experience with any conversion between Unicode and non-Unicide systems via RFC-call (non-English target obligatory !!!), or can anyone share valuable information regarding this issue - what should be managed in the RFC-destination in order to get character conversion working? Is it acceptable to use any character parameter in the target function module interface at all?
Many thanks in advance.
Regards,
Ivaylo Mutafchiev
Senior SAP ABAP Consultant

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

I recently subscribed to Adobe ExportPDF and tried to convert a PDF file to MS Word. So far, after many tries, I get soe type of error and the conversion fails. Please advise?

I recently subscribed to Adobe ExportPDF and tried to convert a PDF file to MS Word. So far, after many tries, I get soe type of error and the conversion fails. Please advise?

Hi there,
It sounds like there may be an issue with the quality of the PDF. Not all PDFs are created equal, and especially those created from scanned documents can be problematic if the scan quality isn't the best. Is there a dark background on the PDF, or stray marks or smudges?
You can try converting with OCR disabled at outlined in this document: How to disable Optical Character Recognition (O... | Adobe Community. But, while that's a good test to find out where the problem lies, you'll end up with a Word document that isn't editable, so it's not an optimal solution.
Please let us know how it goes.
Best,
Sara

Ldap Synch Error in attribute conversion operation Issue in OIM 11g R2 PS1

Hi All,
We have enabled LDAP Synch in OIM11g R2 PS1 environment. We have requirement of users getting created through Web Services. When we create a user through Webservices, and provide all the attributes required to create user then we are getting LDAP Error in attribute conversion operation:
2014-01-03T02:31:52.249-05:00] [oim_server1] [WARNING] [] [oracle.adf.controller.faces.lifecycle.Utils] [tid: [ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 1353004b0df87234:-67081615:143517a89d1:-8000-0000000000002807,0] [APP: oracle.iam.console.identity.self-service.ear#V2.0] ADF: Adding the following JSF error message: IAM-2050243 : Orchestration process with id 9864, failed with error message IAM-3010201 : LDAP create event failed : 00000057: LdapErr: DSID-0C090C3E, comment: Error in attribute conversion operation, data 0, v1db1.[[
oracle.iam.ui.platform.exception.OIMRuntimeException: IAM-2050243 : Orchestration process with id 9864, failed with error message IAM-3010201 : LDAP create event failed : 00000057: LdapErr: DSID-0C090C3E, comment: Error in attribute conversion operation, data 0, v1db1.
at oracle.iam.ui.platform.exception.OIMErrorHandler.reportServiceException(OIMErrorHandler.java:170)
at oracle.iam.ui.platform.exception.OIMErrorHandler.reportException(OIMErrorHandler.java:65)
at oracle.adf.model.binding.DCDataControl.reportException(DCDataControl.java:411)
at oracle.adf.model.binding.DCBindingContainer.reportException(DCBindingContainer.java:416)
at oracle.adf.model.binding.DCBindingContainer.reportException(DCBindingContainer.java:471)
at oracle.adf.model.binding.DCControlBinding.reportException(DCControlBinding.java:201)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.reportException(JUCtrlActionBinding.java:2016)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1660)
at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2150)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:740)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:402)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:210)
at oracle.iam.ui.platform.utils.FacesUtils.executeOperationBinding(FacesUtils.java:165)
at oracle.iam.ui.platform.utils.FacesUtils.executeOperationBindingFromActionListener(FacesUtils.java:112)
at oracle.iam.ui.catalog.view.backing.CartReqBean.submitActionListener(CartReqBean.java:848)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.sun.el.parser.AstValue.invoke(AstValue.java:187)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297)
at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256)
at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:1018)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:386)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.view.page.editor.webapp.WebCenterComposerFilter.doFilter(WebCenterComposerFilter.java:117)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.ui.platform.servletfilter.IdentityContextFilter.doFilter(IdentityContextFilter.java:50)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.platform.servletfilter.PwdMgmtNavigationFilter.doFilter(PwdMgmtNavigationFilter.java:164)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.doFilter(WorkflowFilter.java:248)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.bpel.services.workflow.client.worklist.util.DisableUrlSessionFilter.doFilter(DisableUrlSessionFilter.java:70)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:179)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
In this case user is getting created in OIM but LDAP Synch is not happening we are getting the error as mentioned above.
When we create user in OIM not through Web Serives but through Identity Self Service and provide any date attribute for example Start Date,Provisoning Date, Deprovisoning Date or any other date attribute, then also we are geeting the same error of Error in attribute conversion operation Issue, in this case user is not getting created in OIM and LDAP Synch is not happening.
And when we create a user in OIM not through Web Serives but through Identity Self Service and did not give any of the date attribute then user is getting created and LDAP synch is also happening successfully.
We need to create users through Web Services and we need to resolve this issue asap, request you all to provide any helpful pointer on this.
Thanks
Varsha

This can happen due to OIM-LDAP wrong attribute mapping/value getting passed.
Can you please first try with OOTB attributes and see how it behaves?
J

Error during Unicode Conversion at DDNTF table

Hello
We are doing a Unicode Conversion for our CRT systems. This system now
is a SAP CRM 7.0 SR1 ABAP.
We have performed preparatory steps (SPUMG, checks, updating R3load,
R3ldctl, R3szchk, dboralib, ...),
but when we start Import process we get an error in SAPSDIC package.
The error looks like:
*************************+
(RTF) ########## WARNING ###########
Without ORDER BY PRIMARY KEY the exported data may be unusable
for some databases
(EXP) INFO: table DDNTF will be exported with sorting
(RSCP) ERROR: 'DDNTF' in UMGCCTL: Guess has illegal value.
(RSCP) WARN: DDNTF: Missing in UMGSTAT,
ERROR in nametab conversion
conversion of nametab table 'DDNTF ':
rscpMCStartTab: rc = 128
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/CRT/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/CRT/SYS/exe/run/R3load: END OF LOG: 20091229193651
Any idea??
Thanks in advance
Regards

Yes I executed this Report using Menu Tool Bar.
The first execution gave me some errors regarding some tables existing at database level but not in DDIC. We ignored this errrors because those tables are not important.
But the last try, we decided solve this inconsistencies deleteting those tables at database level, repeting report RADUCNT (in this case no errors appeared) and repeting the export with the same error..
Now, we have seen in Tabscript STATUS of SPUMG there are some errors regarding DDNTF inconsistency found at table control. Reason 4. But this reason means that faillback codepage missing at table control for this table. But as far I know, I can't fill failbak field for this kind of table...
So know I'm reseting SPUMG, and reestarting again..
But I don't understand what is the problem
In a few minutes I will you inform about results
Meanwhile is anybody have any suggestion or idea... please let me know
Thanks!

Exec sqlplus process error in character conversion

Similar Messages

Maybe you are looking for