Line Sizing Problem

I am running several reports to produce PDFs that have an interesting behavior. When I publish a report out to our reports server, text in a text box is showing up at or near the top of the box that contains it. This report output does not look very good. On my desktop environment, when I run the report it produces a PDF with no sizing issues.
I have read in several places that this might be a postscipt printer issue. So, I switched the printer on the report server machine to a postscript printer but it did not fix the problem. The font that I am using is Arial as that is the standard font that the client uses. The report server is 6. Any recommendations are appreciated.
Thanks,
Greg

Greg,
This is probably that server is not using the printer fonts for formatting and uses the system fonts.
Please ensure you use the same printer / similar driver for both the desktop and server to see the effect.
Also, the server if you run as service, by default it runs in the system login and the defaukt printer wouldn't be accessible. Please go to the services properties and ensure the login account has admin privilages to access the printer
Thanks
The Oracle Reports Team

Similar Messages

PDF Letterhead Text LINE SPACING PROBLEM

I recently upgraded from Pro 8 to X Pro on my Windows XP desktop. With Pro * I used the typewriter fucntion to place text onto my pdf letterhead. I have my letterhead in pdf format on my hardrive. I saved this texted letterhead without a problem, i.e., with the font, paragraphs, and line spacing eaxtly as it was when I creared it. With X Pro, after having placed text in my letterhead using the Typewriter function, my attempt to save the texted in letter head results in a pdf document which does not respect the line spacing I used w=hen creating it. Why am I have this line spacing problem?

Thank you Michael,
I am simply trying to continue using X Pro the way I used Pro 8. In Pro 8 I
used the Typewriter function to input text to the letter head stored in my
hard drive. Perhaps this is a functionality I lost as a result of the
upgrade to X Pro -- I hope not??
Joseph S. Tann, Jr., Esq.
CONFIDENTIALITY NOTICE: This transmission is intended only for the addressee
shown above. It may contain information that is privileged, confidential, or
otherwise protected from disclosure. If you are not the intended recipient,
please do not read, copy, or use it, and do not disclose it to others.
Please notify the sender of the delivery error by replying to this message
and then delete it from your system. Thank you.

Q10 Screen Sizing Problem in Blackberry 10.3

Has anyone else noticed that there seems to be a screen sizing problem in Blackberry 10.3.
When you wake the screeen with a gesture or pull the handset from the Q10 pocket, the screen that it "wakes" up to is enlarged, requiring the user to use the finger gestures to shrink it down to regular size.
Or have I just not mastered 10.3 yet?
Rgds
E.T.
Solved!
Go to Solution.

Hi Folks,
I've sussed this one out!
It is not a problem with the screen resolution or the software update, I had within the accessibility settings the "Magnify Mode" enabled.
Disable this and the screen behaves perfectly..........
False Alarm. Sorry!
Revert to Defcon 5........... :-)

At Line selection problem

hi,
iam stuck up with AT LINE-SELECTION problem ie i designed a screen where they need month list on clicking F4. i got the month list using month_names_get in the screen but while clicking the relevant month no.it's not entering into the required parameter. i have attached the codings,
MODULE MONTH_DIS OUTPUT.
SUPPRESS DIALOG.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
SET PF-STATUS SPACE.
NEW-PAGE NO-TITLE.
WRITE:/ 'SELECT MONTH' COLOR COL_HEADING.
ULINE.
DATA: T_MNTH LIKE T247 OCCURS 12 WITH HEADER LINE.
refresh t_mnth.
CALL FUNCTION 'MONTH_NAMES_GET'
   EXPORTING
     LANGUAGE                    = SY-LANGU
IMPORTING
RETURN_CODE                 =
    TABLES
      MONTH_NAMES                 = T_MNTH
   EXCEPTIONS
     MONTH_NAMES_NOT_FOUND       = 1
     OTHERS                      = 2
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
loop at t_mnth.
    write:/ t_mnth-mnr, t_mnth-ltx.
endloop.
CLEAR T_MNTH-MNR.
ENDMODULE.                 " MONTH_DIS OUTPUT
AT LINE-SELECTION.
p_period = t_mnth-mnr.
CHECK NOT p_period IS INITIAL.
LEAVE TO SCREEN 0.
here in the AT LINE-SELECTION, the selected month is not coming to the required parameter.
pls help me in this issue,
Thanks in advance,
Premnath.

You need to set a "Hide" after the write... I suggest you also set your own dialog PF-STATUS too so you can have just a PF2 "pick" button and a Cancel button ( this will look better to the user).
loop at t_mnth.
write:/ t_mnth-mnr, t_mnth-ltx.
hide: t_mnth. "needs this
endloop.
clear: t_mnth.

[ASAP] Need Help Exporting to PDF - Line weight problems (Illustrator file)

So, I've drawn some stuff in Illustrator which I've then placed in InDesign.
It all looks right on screen, but when I export the document to pdf (Adobe PDF Presets: High Quality Print) the Illustrator stuff appears to lose the line weight settings. This is easily noticeable on some really thin lines that print much thicker than they were supposed to.
I gotta be missing something when exporting to pdf... 'cause if I export to Jpeg everything comes out right. No more line weight problems! The question is: what the hell am I doing wrong???
Please, somebody help me out.
Thx!

1. How are you printing?
I'm using one of the Adobe PDF Export Presets: High Quality Print.
2. What are you using to determine the line weight?
What do you mean? I talking about the stroke size.
3. Have you tried opening the PDF in Illustrator to see what the reported line weight is?
I've tried it now and it looks just fine! Just like it was supposed to! All the line weights are correct.
4. This might just be a limitation of your printer or printer driver.
I don't think so. I have never had this problem up until now!
I'm starting to think it has something to do with some Acrobat preferences settings...

Line art problem outputting to pdf

I have a problem with exporting pages of a magazine going to print as pdf, relating to line art placed on the page as a bitmap tiff (typically at 1200 ppi). At present I have a workaround for an annoying problem that really needs clearing up ...
I'm using CS4 InDesign and Acrobat (files prepared in Photoshop). So, high-res bitmap tiff containing line art sized (that is, just placed - no resizing in Indesign) and placed in Indesign, looks fine on the page. Output to pdf using 'export' and the resulting file, when viewed on screen, has a thin line down the right-hand edge of any and all bitmap files.
To ensure no misunderstanding, the 'bitmap' reference is what Photoshop calls it - a bilevel file with black lines in it, which enables me easily to overlay other files such as a photo (because the file is black/transparent) and assign a colour or tint to the bitmap, or even a drop shadow etc. I've used this workflow for years, from Photoshop through Indesign, but the latter always gives me this line on the right edge, in the pdf. It did this in CS3 Indesign/Acrobat as well (but never in Pagemaker).
My workaround is to lay a white-filled box over the edge of the file, thus masking it. But of course, that also limits me to where I can place the file - not easily on a graded tint background, not on a photo and so on. So I'd like to solve this.
Any ideas? OS is Win XP Pro (all updates applied to this and the CS programs - I don't believe they make a difference to this problem, as it has existed through several iterations of both OS and CS).
Anyone else seen this effect? Or is it just me? And has anyone a potential solution?
Chris

I think by reason of not knowing what else I can do, I'm heading to the same conclusion - put up with it! I'll certainly try sending a line to print and see if it appears, but for on-screen stuff, I think I have to stick with the safe workaround I use and accept the layout limitations. (Or resort to Pagemaker for the pages that I just cannot do otherwise.)
Seems to me, if people have reported this for years, Adobe might have tried sorting it out. On screen or not, it still must be due to *something* in the file and/or Acrobat/Distiller to allow it to appear. If I create a white greyscale tiff with the same resolution etc, and place it on a page, there's no line down the edge on output - just a white page with a white (invisible) box. If I do this with an 'empty' bitmap file, a line appears ... Both files created in Adobe programs, so it's not me as a user ...
Just me whinging! I'm really coming from the angle that if this is indeed a display problem, it can only be a display problem if there is something in the file for the display to react to (badly phrased that!).
Thanks everyone for your support and ideas - I think that's me finished for now; I have files to upload and then sleep.

Line Item Problem in while Proforma Invoicing in case of STO

Hi All,
The problem is related to Line Item Quantity in Proforma Invoice which is explained with an example -
When we are doing Outbound Delivery for STO ( Stock Transfer Order ) we have the batch-split function where 2 line generates for a single line item material A in which in the first line no delivery quantity and value gets reflected and in the second line for the same material the delivery quantity gets reflected with batches. Then we save the order and done PGI. After that while doing the proforma invoice there also again the 2 lines appear for the single material A where the first line doesn't contain invoice quantity and value and show as 0pcs.In the second line for the same material it shows the invoice quantity with value. I want to remove this first line for the same line item from proforma invoice and want the system to generate only one line for the line item containing the invoice quantity.
Point to be noted that this thing doesn't happen for normal sales cycle done through Sales Order.
I have also checked with the Item Category NLN where i have tried the Billing relevance N - Pro Forma - no zero quantities (including main batch items) and L - Pro Forma - no zero quantities. Still the same problem is arising.
What is the problem here and how can it be solved?
Looking forward to some valuable suggestions
Thanks & Regards
Priyanka Mitra

check for your batch item cateogry,,, maintain the batch item cateogry setting same as it is ther in case of normal sale cycle. or what you can do ,,,copy your batch item cateogry and create a new batch item cateogry for your STO delivery .
i did it and it is working fine for me. please check the batch item cateogry and matain it the same way.
cheers

Line Alignment Problem while sending Fax from SAP Script

Moderator message: please do not post the same question in different forums
Hi Experts,
While sending fax the horizontal lines are not displaying till the end of the page.
But in the print preview the lines are displying till the end.
If this is printed using local printer the lines are printing fine but the problem is with the fax.
Please provide me a solution for this.
Regards,
Rajesh.
Edited by: Matt on Nov 25, 2008 2:51 PM

Puzzling.
I've seen where the printed output doesn't match the print preview but not a fax not matching a print.
Do you use SAPConnect or the older SAPComm method for faxing?
How do you produce the horizontal lines? BOX commands, ULINE, '-', etc.?

Recording from LINE-IN problem

Hi at all,
I have a problem with recording input audio coming from LINE-IN of my pc.
I looked up on google and on this forum to find something useful but I found nothing. If I try to access line-in I get exception: Line unsupported.
I found a discovery code to find what I have on my pc:
ArrayList<Mixer.Info> mixerInfos = new ArrayList<Mixer.Info>(Arrays.asList(AudioSystem.getMixerInfo()));
Line.Info portInfo = new Line.Info(Port.class);
for (Mixer.Info mixerInfo: mixerInfos) {
     Mixer mixer = AudioSystem.getMixer(mixerInfo);
     if (mixer.isLineSupported(portInfo)) {
          // found a Port Mixer
          System.out.println("Found mixer: " + mixerInfo.getName());
          System.out.println("\t" + mixerInfo.getDescription());
          System.out.println("Source Line Supported:");
          ArrayList<Line.Info> srcInfos = new ArrayList<Line.Info>(Arrays.asList(mixer.getSourceLineInfo()));
          for (Line.Info srcInfo: srcInfos) {
               Port.Info pi = (Port.Info) srcInfo;
               System.out.println("\t" + pi.getName() + ", " + (pi.isSource() ? "source" : "target"));
               showControls(mixer.getLine(srcInfo));
          } // of for Line.Info
          System.out.println("Target Line Supported:");
          ArrayList<Line.Info> targetInfos = new ArrayList<Line.Info> (Arrays.asList(mixer.getTargetLineInfo()));
          for (Line.Info targetInfo: targetInfos) {
               Port.Info pi = (Port.Info) targetInfo;
               System.out.println("\t" + pi.getName() + ", " + (pi.isSource() ? "source" : "target"));
               showControls(mixer.getLine(targetInfo));
     } // of if
.....follow the result:
Found mixer: Port Intel [hw:0]
    HDA Intel, Realtek ALC662 rev1
Source Line Supported:
     Front Mic Boost, source
          Available controls:
               Front Mic Boost Control containing Volume, and Balance Controls.
                    Volume with current value: 0.6666667 (range: 0.0 - 1.0)
                    Balance with current value: -2.9802322E-8 (range: -1.0 - 1.0)
     Mic Boost, source
          Available controls:
               Mic Boost Control containing Volume, and Balance Controls.
                    Volume with current value: 0.6666667 (range: 0.0 - 1.0)
                    Balance with current value: -2.9802322E-8 (range: -1.0 - 1.0)
     Capture, source
          Available controls:
               Capture Control containing Volume, Balance, and Select Controls.
                    Volume with current value: 1.0 (range: 0.0 - 1.0)
                    Balance with current value: 0.0 (range: -1.0 - 1.0)
                    Select Control with current value: true
     Capture, source
          Available controls:
               Capture Control containing Volume, Balance, and Select Controls.
                    Volume with current value: 1.0 (range: 0.0 - 1.0)
                    Balance with current value: 0.0 (range: -1.0 - 1.0)
                    Select Control with current value: true
Target Line Supported:
     Master, target
          Available controls:
               Master Control containing Volume, and Mute Controls.
                    Volume with current value: 1.0 (range: 0.0 - 1.0)
                    Mute Control with current value: false
     Headphone, target
          Available controls:
               Headphone Control containing Volume, Balance, and Mute Controls.
                    Volume with current value: 1.0 (range: 0.0 - 1.0)
                    Balance with current value: 0.0 (range: -1.0 - 1.0)
                    Mute Control with current value: false
     PCM, target
          Available controls:
               PCM Control containing Volume, and Balance Controls.
                    Volume with current value: 1.0 (range: 0.0 - 1.0)
                    Balance with current value: 0.0 (range: -1.0 - 1.0)
     Front, target
          Available controls:
               Front Control containing Volume, Balance, and Mute Controls.
                    Volume with current value: 1.0 (range: 0.0 - 1.0)
                    Balance with current value: 0.0 (range: -1.0 - 1.0)
                    Mute Control with current value: false
     Front Mic, target
          Available controls:
               Front Mic Control containing Volume, Balance, and Mute Controls.
                    Volume with current value: 0.61290324 (range: 0.0 - 1.0)
                    Balance with current value: -1.8822519E-8 (range: -1.0 - 1.0)
                    Mute Control with current value: true
     Front Mic Boost, target
          Available controls:
               Front Mic Boost Control containing Volume, and Balance Controls.
                    Volume with current value: 0.6666667 (range: 0.0 - 1.0)
                    Balance with current value: -2.9802322E-8 (range: -1.0 - 1.0)
     Line, target
          Available controls:
               Line Control containing Volume, Balance, and Mute Controls.
                    Volume with current value: 0.7096774 (range: 0.0 - 1.0)
                    Balance with current value: 2.9802322E-8 (range: -1.0 - 1.0)
                    Mute Control with current value: false
     Mic, target
          Available controls:
               Mic Control containing Volume, Balance, and Mute Controls.
                    Volume with current value: 0.7419355 (range: 0.0 - 1.0)
                    Balance with current value: -1.0366025E-8 (range: -1.0 - 1.0)
                    Mute Control with current value: true
     Mic Boost, target
          Available controls:
               Mic Boost Control containing Volume, and Balance Controls.
                    Volume with current value: 0.6666667 (range: 0.0 - 1.0)
                    Balance with current value: -2.9802322E-8 (range: -1.0 - 1.0)
     Beep, target
          Available controls:
               Beep Control containing Volume, Balance, and Mute Controls.
                    Volume with current value: 0.0 (range: 0.0 - 1.0)
                    Balance with current value: 0.0 (range: -1.0 - 1.0)
                    Mute Control with current value: trueThis is the class I use for my test:
import java.io.File;
import java.io.IOException;
import java.text.SimpleDateFormat;
import java.util.Date;
import javax.sound.sampled.AudioFileFormat;
import javax.sound.sampled.AudioFormat;
import javax.sound.sampled.AudioInputStream;
import javax.sound.sampled.AudioSystem;
import javax.sound.sampled.DataLine;
import javax.sound.sampled.LineUnavailableException;
import javax.sound.sampled.Mixer;
import javax.sound.sampled.TargetDataLine;
import org.apache.commons.configuration.ConfigurationException;
import org.apache.commons.configuration.PropertiesConfiguration;
import org.apache.log4j.Logger;
public class LineinRecorder extends Thread {
     /** Logger instance */
     private static Logger log = Logger.getLogger(LineinRecorder.class);
     private TargetDataLine m_line;
     private AudioFileFormat.Type m_targetType;
     private AudioInputStream m_audioInputStream;
     private File m_outputFile;
     private LineinRecorder(TargetDataLine line, AudioFileFormat.Type m_type, File file) {
          m_line = line;
          m_targetType = m_type;
          m_audioInputStream = new AudioInputStream(line);
          m_outputFile = file;
      * Starts the recording. To accomplish this, (i) the line is started and
      * (ii) the thread is started.
     public void start() {
           * Starting the TargetDataLine. It tells the line that we now want to
           * read data from it. If this method isn't called, we won't be able to
           * read data from the line at all.
          m_line.start();
           * Starting the thread. This call results in the method 'run()' (see
           * below) being called. There, the data is actually read from the line.
          super.start();
      * Stops the recording.
      * Note that stopping the thread explicitely is not necessary. Once no more
      * data can be read from the TargetDataLine, no more data be read from our
      * AudioInputStream. And if there is no more data from the AudioInputStream,
      * the method 'AudioSystem.write()' (called in 'run()' returns. Returning
      * from 'AudioSystem.write()' is followed by returning from 'run()', and
      * thus, the thread is terminated automatically.
      * It's not a good idea to call this method just 'stop()' because stop() is
      * a (deprecated) method of the class 'Thread'. And we don't want to
      * override this method.
     public void stopRecording() {
          m_line.stop();
          m_line.close();
      * Main working method. You may be surprised that here, just
      * 'AudioSystem.write()' is called. But internally, it works like this:
      * AudioSystem.write() contains a loop that is trying to read from the
      * passed AudioInputStream. Since we have a special AudioInputStream that
      * gets its data from a TargetDataLine, reading from the AudioInputStream
      * leads to reading from the TargetDataLine. The data read this way is then
      * written to the passed File. Before writing of audio data starts, a header
      * is written according to the desired audio file type. Reading continues
      * untill no more data can be read from the AudioInputStream. In our case,
      * this happens if no more data can be read from the TargetDataLine. This,
      * in turn, happens if the TargetDataLine is stopped or closed (which
      * implies stopping). (Also see the comment above.) Then, the file is closed
      * and 'AudioSystem.write()' returns.
     public void run() {
          try {
               AudioSystem.write(m_audioInputStream, m_targetType, m_outputFile);
          } catch (IOException e) {
               e.printStackTrace();
     public static void record() {
           * We have made shure that there is only one command line argument. This
           * is taken as the filename of the soundfile to store to.
          String strFilename = "audios/linein_rec.wav";
          File outputFile = new File(strFilename);
           * For simplicity, the audio data format used for recording is hardcoded
           * here. We use PCM 44.1 kHz, 16 bit signed, stereo.
          AudioFormat audioFormat = new AudioFormat(8000.0F, 16, 1, true, false);
           * Now, we are trying to get a TargetDataLine. The TargetDataLine is
           * used later to read audio data from it. If requesting the line was
           * successful, we are opening it (important!).
          Mixer.Info[] aInfos = AudioSystem.getMixerInfo();
          TargetDataLine targetDataLine = null;
          try {
                        // aInfos[2] is the only supported
               targetDataLine = AudioSystem.getTargetDataLine(audioFormat,aInfos[2]);
               targetDataLine.open(audioFormat);
          } catch (LineUnavailableException e) {
               out("unable to get a recording line");
               e.printStackTrace();
               System.exit(1);
           * Now, we are creating an AudioRecorder object. It contains the
           * logic of starting and stopping the recording, reading audio data from
           * the TargetDataLine and writing the data to a file.
          LineinRecorder recorder = new LineinRecorder(targetDataLine, AudioFileFormat.Type.WAVE, outputFile);
           * Here, the recording is actually started.
          recorder.start();
          out("Recording...");
          try {
               if (p==null) {
                    Thread.sleep(5000);
               } else {
                    Thread.sleep(p.getLong("registrationTime"));
          } catch (InterruptedException e1) {
               e1.printStackTrace();
           * Here, the recording is actually stopped.
          recorder.stopRecording();
          out("Recording stopped.");
     private static void out(String strMessage) {
          System.out.println(strMessage);
}So, when i call LineinRecorder.record() I get :
java.lang.IllegalArgumentException: Line unsupported: interface TargetDataLine supporting format PCM_SIGNED 8000.0 Hz, 16 bit, mono, 2 bytes/frame, little-endian
     at com.sun.media.sound.PortMixer.getLine(PortMixer.java:120)
     at javax.sound.sampled.AudioSystem.getTargetDataLine(AudioSystem.java:731)
     at capture.LineinRecorder.record(LineinRecorder.java:149)
     at entrypoint.MainEntry.main(MainEntry.java:73)I don't understand why ? I don't know if I must specify explicitly     the line port but I don't know how to build TargetDataLine object.
Please help me I'm in trouble.
Any help is granted.
Regards,
edcruise.

Thanks for the reply..
I read the article and followed the example...but, I get:
java.lang.IllegalArgumentException: No line matching interface TargetDataLine supporting format PCM_SIGNED 44100.0 Hz, 16 bit, stereo, 4 bytes/frame, little-endian is supported.
     at javax.sound.sampled.AudioSystem.getLine(AudioSystem.java:459)
     at entrypoint.MainEntry.main(MainEntry.java:133)Is there a way to list all available audio formats ? I wonder that does not exist a simple method to get them.
Follow my code taken from above example:
               File outputFile = new File("audios/linein-rec.wav");
               AudioFormat recordingFormat = new AudioFormat(AudioFormat.Encoding.PCM_SIGNED, 44100.0F, 16, 2, 4, 44100.0F,
                         false);
               DataLine.Info info = new DataLine.Info(TargetDataLine.class,
                         recordingFormat);
               TargetDataLine recordLine = null;
               try {
                    recordLine = (TargetDataLine) AudioSystem.getLine(info);
                    recordLine.open(recordingFormat);
               } catch (LineUnavailableException e) {
                    System.out.println("unable to get a recording line");
                    e.printStackTrace();
                    System.exit(1);
               adjustRecordingVolume();
               AudioFileFormat.Type fileType = AudioFileFormat.Type.WAVE;
               KokRecorder recorder = new KokRecorder(recordLine, fileType, outputFile);
               recorder.start();
               System.out.println("Recording...");
               try {
                    Thread.sleep(5000);
               } catch (InterruptedException e1) {
                    e1.printStackTrace();
               recorder.stopRecording();
               System.out.println("Recording stopped.");
     public static void adjustRecordingVolume() throws Exception {
          Port.Info recPortInfo = new Port.Info(Port.class, "Capture", true);
          Port recPort = (Port) AudioSystem.getLine(recPortInfo);
          setRecControlValue(recPort);
     private static void setRecControlValue(Port inPort) throws Exception {
          inPort.open();
          Control[] controls = inPort.getControls();
          for (int i = 0; i < controls.length; i++) {
               if (controls[i] instanceof CompoundControl) {
                    Control[] members = ((CompoundControl) controls).getMemberControls();
                    for (int j = 0; j < members.length; j++) {
                         setCtrl(members[j]);
                    } // for int j
               } // if
               else
                    setCtrl(controls[i]);
          } // for i
          inPort.close();
     private static void setCtrl(Control ctl) {
          if(ctl.getType().toString().equals("Select")) {
               ((BooleanControl)ctl).setValue(true);
          if(ctl.getType().toString().equals("Volume")) {
               FloatControl vol = (FloatControl) ctl;
               float setVal = vol.getMinimum() + (vol.getMaximum() - vol.getMinimum()) * 0.8f;
               vol.setValue(setVal);
Thanks in advance.
Regards,
edcruise.

TV @nywhere Line-In Problem

I have a tv tuner card that I have been using for the past few months to play ps2 on my pc. I just had a RAID-0 Card installed on my pc, and now when I try to use the MSI PVS software to play games, I get video from my ps2, but the sound comes from the coax cable and not from my ps2.
When I hook it all up, I have the ps2 S-Video connected to the TV card, and I have the composite sound plugged into an RCA to Stereo converter and then connected to the line-in on the TV card. I have tested my ps2 on a tv, and it works properly, and I have tried connecting other devices to the TV card's line-in and I have gotten no sound. ;(
I was wondering if anyone has had a problem like this or knows how to fix it. I think it might be an IRQ conflict, but windows xp doesn't detect it, and its a pain in the @$$.
Thanks.

Well, what you said is a workaround, but it doesn't solve the problem that MSI TV@nywhere does not work as described/designed.
For example, if the TV@nywhere has a SVHS/RCA-in, and it don't work. The workaround is to use a TV for that, but that totally defeat the point of having a TV-card. (of course I'm exaggerating, but I hope MSI can provide some *real* solution to the mistakes they made.

FBL3N-Spool Line Items Problem

Hi Guys,
The following problem started after upgrade to 5.0.
After executing tcode FBL3N, I'm able to see the report.
Problem:
Now when I go for the print option, in the spool (SP01> 2nd column>TYPE), instead of showing the actual line items it shows messages like " xxxxx archived documents were selected ". This is NOT happening for all the users.
Is it a basis issue ar related to ABAP only?
Thanks and Regards,
Pritam

hi,
compare settings of transaction <b>fb00</b> for users
Andreas

Line item problem in FBL3n and FS10n

Dear ALL FI expert
In my one G/L account(WIP) I do not see any line item data using FBL3n, FS10n.
But the transaction is made in period jan ~ march/2009.
Can anybody tell me why the problem happend?
Note: Actually I can see last year data and it is okay.
Thanks & B.Rgds
Bishnu
23/04
Edited by: Bishnu Dey on Apr 23, 2009 11:08 AM

Hi Bishnu,
For the said GL, check in FS04, whether the line item mgmt tick was changed?
If changed do the following:
Activation of Line item management
For the same a GL had been created with no tick in 'Line item display'. Documents were posted.
Now the line item Display is to activated in the above GL.
For the same for the following process:
a)Tick the line item display in the GL master and save
b)The GL has to blocked for posting
In FS00, Click on the block button and tick the Block for posting button and save.
c)After the blocking of the GL, go to SE38 and enter RFSEPA01 as the program and press execute
d)Enter the Company code and the GL
e)Press Execute.
Now the line items were generated for the GL. Table BSIS was updated. Unblock the GL for further postings
Deactivation of line item management
Now for deactivating line item in a GL the following process should be followed.
a)Untick the line item display in the GL master and save
b)Block the GL for postings (as shown in 1.2.1)
c)Go to SE38 and enter RFSEPA04 as the program and press execute
d)Enter the Company code and the GL
e)Execute
After the execution of the program all the line items of that particular GL will be deleted from BSIS table. Unblock the GL for further postings
Regards,
Kiran

Dbms_lob and line size problem

Hi,
below is a simple function which returns a CLOB.
When I call this function from sqlplus and spool the result in a
file via the SPOOL command I get a line break after 80 characters.
When I replace in the function the CLOB type with a VARCHAR2 type
the whole TESTSTRING is printed on ONE line.
I do specify 'SET LINESIZE 200' in both cases and the length of
TESTSTRING is smaller than 200 characters.
How can I increase the line size for the CLOB case ?
CREATE OR REPLACE FUNCTION GetSimple (
RETURN CLOB
IS
RESULT CLOB;
TESTSTRING CONSTANT VARCHAR2(4000) := '123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_AFTER_LINEBREAK' ;
BEGIN
-- create CLOB for RETURN
dbms_lob.createtemporary(RESULT, TRUE);
dbms_lob.writeappend(RESULT, length(TESTSTRING), TESTSTRING);
RETURN RESULT;
END GetSimple;
/

problem solved !
I had to add
SET LONGCHUNKSIZE 4096;
default is 80

New Line Character problem in mail attachment

Hi all,
my xi-box is in patch level 16. i need to send the mapped xml as a pipe delimited file(a lineitem per line) attachment to a mail id. so i use MTB to content convert the payload and attach the content as an attachment using a custom module and send the mail. Since the naming convention of the attachment (as per my requirement) says the file should be a .txt file, i 've used text/plain as the content-type.
if i open the attachment in textpad or wordpad i can see one lineitem per line; but if i open it with notepad its not the case.lineitems do not appear in separate lines but appear continuously. i 'm seeing a box character as a separator between the lineitems. i'm not able to figure it out why.
i used MTB in file adapter and content converted the payload and opened the file in notepad;it was fine.
But i'm not able to figure out why its happening with the mail attachment. If you have come across such a problem please suggest me to solve this.
Regards,
Sundararamaprasad

Is there any way you can send the file in an ASCII format instead of BINARY format. In many of my resolved cases I just change from binary to ascii and it works for eg., while doing FTP.
thansk,
rakesh

Svg line chart problem with latest patch?

Hi team,
I was checking out one page containing an SVG chart that I didn't modify in 2 weeks, according to the application builder, but it seems to hang after displaying the first line series of 4 total.
It was working before the last patch was installed.
It's page 65 of application 21670 in the online environment.
Choose "automobile" from the first drop down list and click on the button, the chart appears but then it seems to be waiting for something to download.
If you move the mouse over any textual part, you can see in the status line the following message:
"xml processing instuction not at start of external entity: line 172, column 0".
If you open up the SVG source by right clicking on the chart, you will see at the end of the file an error text message returned by oracle (ORA-06502), but what is particularly strange is the presence of an <?xml> processing instruction just in the middle of the source code listing.
It looks like it is trying to append the second chart series by appending another svg source file.
Could you check if I did anything wrong or if it is a problem of the patch?
I have got other chart type running without problems.
Thanks!
Bye,
Flavio

Things are getting complicated.
I found some cases where the chart is displayed correctly, which made me think of some unexpected values returned by the underlying queries.
Since my chart is made up of 4 different series returning 12 points each, I assembled the queries with UNION ALL and checked out what was returned both in a failing case and a successful one but I can't figure out a valid explanation, the only thing I notice is that in the failing case there are some values higher than average, say 10 times bigger than the average value and for some reason the chart stops drawing points exactly after the peak value (1155.62, see below).
Each series returns exactly 12 points, some nulls, but that's doesn't seem to be the problem.
I wonder if the problem is with the "autoscale" algorithm, but I am lost at the moment...
Here is a successful data sample:
- APRIL -
- APRIL 119.57125
- APRIL -
- APRIL -
- AUGUST 160.5
- AUGUST 157.53
- AUGUST 157.53
- AUGUST 119.57125
- DECEMBER -
- DECEMBER 119.57125
- DECEMBER 113.67
- DECEMBER 131.214
- FEBRUARY 104
- FEBRUARY 119.57125
- FEBRUARY 126.418333333333333333333333333333333333
- FEBRUARY 125
- JANUARY 153
- JANUARY 119.57125
- JANUARY 134.845
- JANUARY 145
- JULY 154.56
- JULY 119.57125
- JULY 154.56
- JULY 154.56
- JUNE -
- JUNE -
- JUNE -
- JUNE 119.57125
- MARCH 43.5
- MARCH 119.57125
- MARCH 106.918333333333333333333333333333333333
- MARCH 100.166666666666666666666666666666666667
- MAY -
- MAY 119.57125
- MAY -
- MAY -
- NOVEMBER 118
- NOVEMBER 131.214
- NOVEMBER 125.3775
- NOVEMBER 119.57125
- OCTOBER 164
- OCTOBER 119.57125
- OCTOBER 134.5175
- OCTOBER 134.5175
- SEPTEMBER 59.01
- SEPTEMBER 119.57125
- SEPTEMBER 124.69
- SEPTEMBER 124.69
and now an offending one:
- APRIL -
- APRIL 287.743333333333333333333333333333333333
- APRIL -
- APRIL -
- AUGUST 1155.62
- AUGUST 655.09
- AUGUST 655.09
- AUGUST 287.743333333333333333333333333333333333
- DECEMBER 135
- DECEMBER 287.743333333333333333333333333333333333
- DECEMBER 197.2525
- DECEMBER 349.865
- FEBRUARY 114
- FEBRUARY 287.743333333333333333333333333333333333
- FEBRUARY 315.947142857142857142857142857142857143
- FEBRUARY 130
- JANUARY 153
- JANUARY 287.743333333333333333333333333333333333
- JANUARY 321.741428571428571428571428571428571429
- JANUARY 190
- JULY 154.56
- JULY 287.743333333333333333333333333333333333
- JULY 154.56
- JULY 154.56
- JUNE -
- JUNE -
- JUNE -
- JUNE 287.743333333333333333333333333333333333
- MARCH 223.5
- MARCH 287.743333333333333333333333333333333333
- MARCH 182.787142857142857142857142857142857143
- MARCH 156.375
- MAY -
- MAY 287.743333333333333333333333333333333333
- MAY -
- MAY -
- NOVEMBER 118
- NOVEMBER 392.838
- NOVEMBER 452.4075
- NOVEMBER 287.743333333333333333333333333333333333
- OCTOBER 354
- OCTOBER 287.743333333333333333333333333333333333
- OCTOBER 461.5475
- OCTOBER 461.5475
- SEPTEMBER 182.01
- SEPTEMBER 287.743333333333333333333333333333333333
- SEPTEMBER 497.396666666666666666666666666666666667
- SEPTEMBER 497.396666666666666666666666666666666667
Weird, isn'it?
Bye,
Flavio

Line Sizing Problem

Similar Messages

Maybe you are looking for