Cure Your Errors

Fix Windows Errors & Optimize Your System

Windows/Mac OS/Linux
Support Guide

Home

Problem in XML file download

types: begin of type_s_data,
         record(65000) type c,
       end of type_s_data.
data: w_xml_out type string.
data: t_xml_tab type table of type_s_data with header line,
Source code
      t_code    type table of type_s_data with header line,
After populating t_code table,
convert internal table data into XML document
  call transformation id
       source code = t_code[]
       result xml w_xml_out.
append XML docu to internal table
  append w_xml_out to t_xml_tab.
Download to XML file
  call function 'GUI_DOWNLOAD'
    exporting
  BIN_FILESIZE                    =
     filename                        = filename
     filetype                        = 'BIN'
    append                        =
  write_field_separator           = sep
  HEADER                          = '00'
  TRUNC_TRAILING_BLANKS           = ' '
  WRITE_LF                        = 'X'
  COL_SELECT                      = ' '
  COL_SELECT_MASK                 = ' '
  DAT_MODE                        = ' '
  CONFIRM_OVERWRITE               = ' '
  NO_AUTH_CHECK                   = ' '
  CODEPAGE                        = ' '
  IGNORE_CERR                     = ABAP_TRUE
  REPLACEMENT                     = '#'
  WRITE_BOM                       = ' '
  TRUNC_TRAILING_BLANKS_EOL       = 'X'
  WK1_N_FORMAT                    = ' '
  WK1_N_SIZE                      = ' '
  WK1_T_FORMAT                    = ' '
  WK1_T_SIZE                      = ' '
  WRITE_LF_AFTER_LAST_LINE        = ABAP_TRUE
  SHOW_TRANSFER_STATUS            = ABAP_TRUE
IMPORTING
  FILELENGTH                      =
    tables
     data_tab                        = t_xml_tab
  FIELDNAMES                      =
    exceptions
     file_write_error                = 1
     no_batch                        = 2
     gui_refuse_filetransfer         = 3
     invalid_type                    = 4
     no_authority                    = 5
     unknown_error                   = 6
     header_not_allowed              = 7
     separator_not_allowed           = 8
     filesize_not_allowed            = 9
     header_too_long                 = 10
     dp_error_create                 = 11
     dp_error_send                   = 12
     dp_error_write                  = 13
     unknown_dp_error                = 14
     access_denied                   = 15
     dp_out_of_memory                = 16
     disk_full                       = 17
     dp_timeout                      = 18
     file_not_found                  = 19
     dataprovider_exception          = 20
     control_flush_error             = 21
     others                          = 22.
  if sy-subrc <> 0.
    message e016 with 'Error during file download'(002).
  endif.
Problem here is when intrernal table data/size is large, only part of the data is getting displayed in the file and at the bottom of the file showing an error message
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
End element was missing the character '>'. Error processing resource 'file:///C:/Documents and Settings/sowjanya.suggula/De...
RECORD
^
>RECORD>
  </item>
wehn i change data  declaration as
data: t_xml_tab type table of string with header line.
when i execute the program, giving me a short dump.please suggest me a soluion for this.
Regards,
Sowjanya

Hi Sowjanya,
Kindly go through this link below:
It Uploads XML to internal table and vice versa :
Upload XML to internal table and vice versa in SAP 4.6C
Hope it helps
Regrds
Mansi

Solution

1. Download & Run DLLEscort - Download Now

2. Click 'Start Scan' to analyze your System.

3. Click 'Fix Errors' and you're done!

 

Related Content

Pyzor Not Running Question


Python script to parse 'iwlist scan' into a table


Pythagorean triples complex squares


PYTHAGORAS THEOREM __ URGENT HELP  NEEDED


PYTHAGORAS THEOREM ) HELP NEEDED


Pytagwrite - easily write ID3 tags to your songs


PY-IN:: Note 1507799 - Sec 80CCD


PY-IN: Payroll Bank Transfer is not working


PY error message - EE's salary group could not be determined for Plan Life


PXI-8532 DNET card is not detected in MAX


PXI-5122 External Sample Clock


PXI R Series PWM Behavior


PXI not showing up properly in MAX


PXI first use, unable to configure/boot safe mode or RT


PXI External Graphic Card


PXI 6733 smallest voltage for external reference?


PXI 6070E, Unable to capture waveform on ACH0 while generating a wavefrm on DAC0


PXI 5620 Initialize Error


PXE T01 file not found PXE E3B TFTP Error file not found error


PXE problem - \boot\BCD 0x0000098 does not contain a valid OS entry


I can't capture screen images with PrtSc button on Lenovo T430. I tried every combination like using Alt+PrtSc, Ctrl+PrtSc and Fn+PrtSc.
Somebody suggested to use windows Snipping Tool to capture images but I dont want it as its very slow and need lots of keystrokes +mouse clicks to capture screen image.
Please help.

Hi All,
We are running EP 7.0 NWO4s on Windows 2003. When the user log on to the portal with the valid qualified URL geting an " 500 Internal Server error with  java.lang.null pointer exception message" Before the restart of the server every user able to access the portal properly. But after the restart of the server we are facing this problem. Few months back also we faced the same problem but it is fixed automitically in our next restart of our server. But this time even though how many times we are restarting of the server still the problem exists.
1. The Server is up and running
2. All the J2EE process are running properly
3. Oracle database is up and running
On the Defaulttrace file we noticed few exceptions
com.sap.portal.prt.sapj2ee.api.clustercommunication.exceptions.PRTMessageListenerException: The listener does not exist !
com.sap.engine.services.servlets_jsp.server.exceptions.WebUnavailableException: Servlet prt is currently unavailable.
Timeout Service Synchronous Internal Thread: javax.management.InstanceNotFoundException
Processing HTTP request to servlet gateway finished with error.The error is: java.lang.NullPointerException: null
Caused by: javax.servlet.UnavailableException: Initialization of Dispatcher failed
Defaulttrace file Information:
#1.5#00188B874AFD002100000505000023E80004474C5F840A13#1204293252562#
com.sap.engine.services.monitor.common.Template##com.sap.engine.services.monitor.common.Template######
a68a3f70e4d411dcc2e100188b874afd#Timeout Service Synchronous Internal Thread##0#0#Warning##Plain###
javax.management.InstanceNotFoundException: com.sap.default:name=ComponentRuntimeMBean,
SAP_J2EEApplicationPerNode=sap.com/com.sap.netweaver.bc.rf.moni,j2eeType=SAP_ApplicationResourcePerNode,
SAP_J2EEClusterNode=18025994,SAP_J2EECluster=ANV not in repository
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1291)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.monitor.mbeans.Template.pollDynamicData(Template.java:891)
at com.sap.engine.services.monitor.mbeans.Template.handleNotification(Template.java:847)
at com.sap.engine.services.jmx.server.AscynchronousProxyListener.handleNotification(AscynchronousProxyListener.java:51)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:94)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:61)
at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification(Timer.java:432)
at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)
at com.sap.engine.services.timeout.TimeoutNode.synchronousRun(TimeoutNode.java:72)
at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun(TimeoutManagerImpl.java:632)
at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:18)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#00188B874AFD00610000000A000023E80004474C946ED4C0#1204294140410#com.sap.engine.services.prtbridge##
com.sap.engine.services.prtbridge######b8f36600e65511dc9d3000188b874afd#SAPEngine_System_Threadimpl:5
_105##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
EXCEPTION
#1#
com.sap.portal.prt.sapj2ee.api.clustercommunication.exceptions.PRTMessageListenerException: The listener does not exist !
(NotificationSAPJ2EE630)
at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.distributeMessage(MessageContextWrapper.java:373)
at com.sap.portal.prt.sapj2ee.bridge.PRTBridgeAccessor.distributeMessage(PRTBridgeAccessor.java:228)
at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.receive(PRTBridgeCommunicationManager.java:568)
at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:126)
at com.sap.engine.core.cluster.impl6.ms.MSMessageQueue.process(MSMessageQueue.java:77)
at com.sap.engine.core.cluster.impl6.ms.MSMessageThread.run(MSMessageThread.java:37)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#00188B874AFD003500000030000023E8000447700BC25D6F#1204446466108#
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
sap.com/irj#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
Guest#2####8920f6c0e83211dc960400188b874afd#SAPEngine_Application_Threadimpl:3_4
##0#0#Error#1#/System/Server/WebRequests#Plain###
Processing HTTP request to servlet gateway finished with error.
The error is: java.lang.NullPointerException: null
Exception id: 00188B874AFD00350000002E000023E8000447700BC25C4C#
#1.5#00188B874AFD00560000003E000023E8000447700C764EBA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain###com.sapportals.portal.prt.dispatcher.DispatcherException: Previous dispatcher initialization failed. Check logs for details.#
#1.5#00188B874AFD00560000003F000023E8000447700C76505A#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:257)#
#1.5#00188B874AFD005600000040000023E8000447700C76509D#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:213)#
#1.5#00188B874AFD005600000041000023E8000447700C7650DA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.access$300(Dispatcher.java:42)#
#1.5#00188B874AFD005600000042000023E8000447700C765116#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:437)#
#1.5#00188B874AFD005600000043000023E8000447700C765151#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#00188B874AFD005600000044000023E8000447700C765192#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
#1.5#00188B874AFD005600000045000023E8000447700C7651CE#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#00188B874AFD005600000046000023E8000447700C765209#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
#1.5#00188B874AFD005600000047000023E8000447700C765247#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#00188B874AFD005600000048000023E8000447700C765282#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
#1.5#00188B874AFD005600000049000023E8000447700C7652BF#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
#1.5#00188B874AFD00560000004A000023E8000447700C7652FB#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
#1.5#00188B874AFD00560000004B000023E8000447700C765338#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
#1.5#00188B874AFD00560000004C000023E8000447700C765374#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
#1.5#00188B874AFD00560000004D000023E8000447700C7653B6#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
#1.5#00188B874AFD00560000004E000023E8000447700C7653F3#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
#1.5#00188B874AFD00560000004F000023E8000447700C76542E#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
#1.5#00188B874AFD005600000050000023E8000447700C76546A#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.5#00188B874AFD005600000051000023E8000447700C7654AA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
#1.5#00188B874AFD005600000052000023E8000447700C7654E8#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5#00188B874AFD005600000053000023E8000447700C765522#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#00188B874AFD005600000054000023E8000447700C76555C#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
#1.5#00188B874AFD005600000055000023E8000447700C765598#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
#1.5#00188B874AFD005600000056000023E8000447700C765C20#1204446477905#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/irj#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2####90290b10e83211dccc4800188b874afd#
SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain###
Processing HTTP request to servlet invoker finished with error.
The error is:
com.sap.engine.services.servlets_jsp.server.exceptions.WebUnavailableException: Servlet prt is currently unavailable.
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:174)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: javax.servlet.UnavailableException: Initialization of Dispatcher failed
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:371)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:213)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$300(Dispatcher.java:42)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:437)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
Please help us to resolve this issue. Its a bit urgent for us. Your suggestions and views would be highly appreciable.
Thanks
Ravi

Whenever I open My PRS600 from complete shutdown it takes too much time to load all the files which are present in Memory card. Is anyone else facing same issue?

Hi,
I tried to update the firmware, but failed when updating to version 1.0.07.05070. Tried to 2 times. The first time it failed I simply tried again. The second time, it took a lot longer to reach the failed to update message, but it did cause the ereader to reboot.
Now, it's stuck in an infinite reboot loop on the "Opening book" page. The progress bar on that page stays completely empty, lasts for about 30 seconds, and reboots again. This will go one until the battery is dead or indefinitely if plugged in. 
I have tried pressing the Home + Menu buttons, but they seem to have no effect.
Please advise if there is anything I can try to revive it?
Thanks in advanced.
David
Solved!
Go to Solution.

Hi
prs-t1 is not properly rendering indic unicode fonts (Hindi, Telugu etc).  Same epub works fine in prs-t2 and it renders the fonts properly.
Solved!
Go to Solution.

I am facing the same problem with my new PRS-T1. It freezes within 20-30 sec of start. It does not freeze when connected to USB or music is played in background. I guess there is some bug in the power management module of the software which puts the CPU in sleep quickly in such a way that it never wakes up other than hard reset.
The problem remained the same even after upgrading to latest FW (v1.0.04.12210). Very poor user experience. never expected this from Sony. They must fix this issue in their next FW release.

Good afternoon.
I recently (about a month ago) bougth two PRS-T1 readers (one as a gift) and I was very happy. I wanted a reader since I first knew of them and a T1 since it came out. I got a job as an intern engineer for the summer and saved to finally buy my gadget of dreams. I actually wanted to wait a little to see if a promotion came up because I lost the "free Harry Potter book combo", but I wanted to use the Reader for my school books and when the "almost free cover" promotion came up I inmediately ordered it.
Fast-forward a few weeks and I'm more than satisfied with my reader. Tablets are very common now, but everyone that sees the e-Ink screen working is thrown back in amazement. I carry it with me at all times (I hold it under my arm because I know keeping it in a bag has the risk of braking the screen) and my reading rate has improved vastly.
I've had the chance to find some areas of improvement on the Reader in the few weeks that I've had it with me and some of those were: being able to post in Facebook my reading status and maybe cite a phrase; and a native Evernote app, because while using the mobile site with the browser to view notes is actually neat, navigation and finding notes isn't, and neither is creating new notes. I supposed these were just remote dreams, knowing that just because you hope for, it doesn't mean a company will implement those features.
Well, imagine my surprise. New reader (it looks very similar to the T2 so no regrets there) with specifically the two functions I spent a month thinking would be great to have. Maybe they were so obvious it was inevitable, but still. Additionally, it seems too soon to drop support of the T1 after less than a year into its lifecycle.
So this is my request to Sony from a true fanboy: Please release a firmware update for the PRS-T1 to add the Facebook and Evernote features. I'd also suggest to remove the Google Books button and change it for one of the above or even a Wikipedia dedicated button, since I discovered that using the Reader is the best device for hours-long Wiki reading sessions.
Please consider my humble request. Maybe it turns out to be very easy to get done. Maybe not. Either way I'll keep enjoying the best e-reading experience with the best e-reader in the market and for that I'm very thankful.

Hi all,
we have schedualiing agreemet in place for some of our consingment stock but we are fadng issue that every day system generates PR for some of those materials for no reason.Ithese materials are MRP relevant.
any suggestion.
thanks

Hi to all -
Our customer desires to see all postings to the general ledger accounts broken down by cost center.  For warranty projects, the settlement rule for WBS elements will be to a Warranty Accrual Account (liability account) and Warranty Expense Account (expense account).  These postings need to be by cost center.
In the WBS element, the coster center field (PRPS-KOSTL) is only available if the WBS element is checked as a statistical WBS.  I would like to use either Responsbile Cost Center, Requesting Cost Center or even a user field as an input field and then substitute this value to the PRPS-KOSTL.  When this is tested, we get the following message:
"Field WBS_CCTR_POSTED_ACTUAL/CCtr posted actual: Changing the contents of the field is not permitted
Message no. CJ727
Diagnosis
Contents of field WBS_CCTR_POSTED_ACTUAL/CCtr posted actual are to be modified, either by substitution or batch input.
Because the system noted that a field was not ready for input no chnage was allowed.
System Response
Processing stopped.
Procedure
Check the field attributes or the action."
My question is if there is a way to use PRPS-KOSTL with out defining the WBS as a statistical WBS.
On the FICO siide, we are using report FAGLL03 to view the G/L accounts.  On this report, KOSTL is available as a selection field to create the segmentation the customer desires.
A final issue we have not gotten to - is if we can get the Cost Center on the WBS and settle the WBS to the G/L accounts - will the Coster Center information come over to the CO tables for use in FAGLL03.
Thanks,
BGS

Hello everybody,
At first, I hope this is the correct thread for this posting.
I have a problem with processing the generated idocs.
I create Idocs for example for all Customers (message type DEBMAS) with the transaction bd12.
Afterwards I process the Idocs with the transaction WE14 (program RSEOUT00).
The parameters I set are for example the packages size (= 100) which is necessary to avoid a lock table overflow, the message type, receiver system and so on.
The jobs works fine and without errors and all Idocs will be process and receive a new Status.
I do this with a background job (sm36) and create for each programm a step.
The problem is, that if I start the transaction we14 inside the background job with this parameters the process use user dialog processes. This means that the process reserve all available user dialog process from the system.
I think it starts/reserve for each package which should be processed a new dialog process.
After a short time nobody can work longer with the system because no dialog processes are available.
Why use this process no background processes or why use this process dialog processes?
Is this possible to configure anywhere?
Regards
Christian