Paper dimensions

Post Author: JULIO.FAZENDEIRO
CA Forum: Crystal Reports
Hi,
I'm designing a report in CR 8,5 to work in a Epson TM-U210
In CR i've got to define paper height size, but i don't know the final height.
If I put the size height like an A4 the sales receipt shows a space in blank to achieve the height of A4.
Is there a way to not define the height?
Some help is apprecciated.
Thanks in advance,
JF

Custom paper size should not be set to No Printer.
In CR 2008 and above you can now set the paper size to Custom or User Defined and check on the Dissociate option and save the report with the printer you are using.
See this post for a sample app on this all works now:
http://scn.sap.com/message/15899751
Don

Similar Messages

  • PS gets wrong paper dimensions from printer driver

    Since yesterday I have trouble with PS CS5 und Mac OS X 10.7.5 as PS does not get correct paper dimensions from standard paper sizes or custom paper sizes from my Epson printer driver. Before yesterday I had no trouble, all went fine. Til Yesterday I printed mostly on roll paper, but yesterday I had to print on a A3+ sheet of paper and PS got in trouble and showed me instead of 32 by 48 cm of paper size than 42 by 59 cm in print dialog with preview. Thil than I have this behavior on all paper sizes but only in Photoshop CS5. All other Apps on my Mac which uses the Mac print dialog show me the correct paper dimenions.
    Any help appreciated.

    I bet that, if you check carefully and with almost pathological tenacity, you will find that the "odd" sizes are creeping into one of the settings in one of the dialog boxes but not in others.
    When something happens to an application "suddenly", that's a clear size to nuke and re-set the preferences, but NOT manually.  Use the key combo at launch.
    To re-create the preferences files for Photoshop, start the application while holding down Ctrl+Alt+Shift (Windows) or Command+Option+Shift (Mac OS). Then, click Yes to the message, "Delete the Adobe Photoshop Settings file?"
    Note: If this process doesn't work for you while you're using a wireless (Bluetooth) keyboard, attach a wired keyboard and retry.
    Important: If you re-create the preferences by manually deleting the Adobe Photoshop CS6 Settings file, make sure that you only delete that file. If you delete the entire settings folder, you also delete any unsaved actions or presets.
    Reinstalling Photoshop does not remove the preferences file. Before reinstalling Photoshop, re-create your preferences.
    NEW Video! Julieanne Kost created a video that takes you through two ways of resetting your Photoshop preferences. The manual preference file removal method is between 0:00 - 5:05. The keyboard shortcut method is between 5:05 - 8:18. The video is located here:
    How to Reset Photoshop CS6’s Preferences File | The Complete Picture with Julieanne Kost | Adobe TV
    Mac OS
    Important: Apple made the user library folder hidden by default with the release of Mac OS X 10.7. If  you require access to files in the hidden library folder to perform Adobe-related troubleshooting, see How to access hidden user library files.

  • Custom paper size - seems scaled for A4

    Hi,
    I'm trying to print on the front of a card which when unfolded is 15cm x 30cm.
    I've made a PDF in Inkscape (page size matches paper dimensions) and opened it in Preview.
    I set a custom paper size of 15 x 30cm for my printer (Samsung ML-2010) in the page setup dialogue. The scaling set to 100%. When I print preview everything looks fine.
    However, when I print it seems to be scaled for a much larger page and the text is much larger than original and runs off the page. If I print it onto an A4 sheet everything fits but the text is still larger than intended.
    Any ideas on what's going wrong?

    Unfortunately I don't seem to have that Scale to Fit option... just the usual Scale bit below the orientation (in Page setup) which I currently have at 100%.

  • Where did all the setting for printing go in PSE8-Mac?!

    OK, I'm probably missing some obvious settings somewhere, please tell me after you read my rantings...
    I'm using the 'Full Edit' mode, assuming that is important. But the new Print Dialog looks like it has been dumbed down for some one, not sure who, however has it has me completely confused. There are now only three 'steps' for printing. One and two are self explanatory. However...
    Step three concerns paper size, image size and several other details. Just for testing, I created a new 4 x 6 inch, 300dpi page and drew some lines. Command-P. Proper printer is selected, select "Letter" as the paper size. 4 x 6 inch appears selected as the "Print size" (I thought that was because of the original page size, but it appears to simply be the default). That is a detail that could easily be over looked by a new user. If the original image is larger than 4 x 6, it will, obviously be either cropped or reduced to fit those dimensions! It seems to me that the "Select Print Size" should automatically assume to be the image size. OTOH, I can see that some people may want to do all their printing on one size of paper. In that case, why not have a preference for the default and let the user change it when they change paper sizes (if they want)?
    Now, if the user happens to notice that a new 8 x 10 inch image is going to be printed in a 4 x 6 area, she will now decide to check the other settings available in the pop up menu. OK, there IS an 8 x 10 inch choice. But look, what's this "Custom" choice? Let's investigate...Now this is strange! The defaults there seem to be 1.383 inches for height AND width! Who came up with that weird number?!
    Oh, there is a "Scale to Fit Media" check box. Checking that now makes the height and width somewhat closer to reality, they now indicate the pape dimensions. That IS logical, but not extremely helpful, IMHO. By the way, the second time one selects the "Custom" choice, the correct, original image size appeared in the Print size boxes. Although I cannot seem to get those to reappear. Oh well...
    My point is, how do these confusing configurations help? Beyond me, anyway.
    BTW, the dpi settings all seem to be 'computed' at one less than the number set by the user for an image. For example, a new image page created at 300 dpi shows 299 in the Custom dialog, 150 shows 149, etc. Close, but why not exact? Furthermore, why can't the user select any dpi they choose? Isn't that what the computer if for; calculate what happens to the pixels when they print at a different setting than the image? Sure, the user should be warned that terrible images my result, but if that's what the user wants, let it be done! Who's running this show, anyway? Oh yeah, I remember, now...excuse me for asking, I'm only a paying customer, what do I know?!
    Lastly, if one has more than one image open, every single one can easily be printed, accidentally. Why? Because they will all appear in the Print Dialog. Don't you see them? Over there on the left. Yeah, I see them, but why doesn't the image I have in front, the one I'm working on, be the one I probably want to print? Many of the others may simply be images I'm borrowing parts from. Why do the developers think I always want to print every image that might be open? I don't have any idea, either. Sure, there are a couple of ways to prevent this multiple image printing; select the one you don't want to print and use the "minus" button or simply close all those images before going to the Print dialog. Guess what. Using the 'minus' button only works for this printing, the next time you ask to print they will all be there, again. And, what if you aren't really finished using some of those extra images that you closed? Now you get to re-open them all again. Completely unnecessary steps because of poor user considerations/research, in my humble opinion. Again, this is exactly the thing that preferences are made for. Or, put them in the "Edit Guided" mode! Or, better yet, just give me back the old Print dialog! Nice!
    Now, I am extremely glad to see that PSE can now remember to keep that stupid Panel bin out of the way! Finally! Three more inches of screen to work with!!! Hooray!! Unfortunately, it still can't remember what the last setting for the jpeg quality was...still defaults to ZERO! Sure, that's the setting I always want to use, it's so much fun letting people try to guess what is in the image...one would think after 8 iterations this could be fixed. One down, umpteen to go. Oh well, what do you want for $80?

    Thanks for your listening/reading and I'll take your advice about dropping a note to the developers, but I won't be holding by breath! I doubt that they consider this a real problem. It's really just my ranting!
    Your solution is probably the 'fix' they might suggest, anyway. However, I'd rather have the screen space than a list of thumbnails of images I already have open. command-plus and/or minus is a pretty quick way of making it easy to see anything that might be visible. Of course, I'm sure there are other uses for the Project Bin that many find useful. Even though I have a 24" iMac, I rather like using the screen space the way I want, not an arbitrary way that got developed. I just don't see why developers can't program an app to allow every conceivable method of use by every living and future user! LOL!!!
    I guess today was the first time I've printed anything since installing 8. I was, quite confused when presented with the new Print interface. Actually, I thought that must be part of the 'Guided' set up which I assume leads one by the hand as much as possible. "Thank you Adobe, but I'm trying to avoid unnecessary contact with strangers right now." LOL! At least I know I didn't miss some setting somewhere.
    Thanks! Have a great weekend! And don't get scared too much tonight!

  • Changing iCal Print Layout

    Hi
    When I print a calandar month, the month and year are top left on the paper so that when I hole-punch the page to stick in my filofax, the month has got a big hole in the middle.
    Is there a way of changing the print layout so that I can move the month a bit towards the centre ?
    Any suggestions very welcome. I hate it looking untidy !!

    I've been battling the lack of a "Page Setup..." menu in iCal for several hours, even after reading the fix above. Some of my conclusions and a tip:
    1. It seems that iCal 'gathers' the paper/printer info when it starts up. It is therefore a waste of time to set these dimensions while iCal is still running/open.
    2. Any app that allows access to the "Page Setup..." menu can be used to create/modify a custom/existing choice.
    3. It may be better to set up a 'custom' setting using "Any Printer" rather than any specific printer you may have.
    Perhaps the most important fact I discovered is that it is more important to set the paper dimensions than the actual margin numbers! iCal seems to prefer using a minimum margin setting regardless of what is defined in any "Page Setup..." item. But it will recognize and respect a slightly smaller page size and print within it. For example, my final success came when I re-defined the normal 8.5 x 11 inch paper as 8.25 x 10.75 inches! Just be sure to crate this as a custom, named setting so you can find and select it in iCal.
    BTW, I have not attempted other 'standard' paper sizes, just the 'full-size' version.
    Anyone have an idea why iCal ignore the GUI standards?! Or is simply another attempt at 'integrating' all apps; like using Safari to tell the OS to use another browser? What happened to Apple's 'user friendliness' mantra?

  • VF03 smartform: Output could not be issued

    Hi All,
    Ive created a custom invoice print program and associated smartform.
    These two run perfectly together when standing alone.
    However Ive created a custom  output type to call this program from VF03.
    This output type appears in the "Issue Output To "options in VF03.
    But it returns the message "Output could not be issued" when trying to print.
    In debug mode the Print Program and smartform execute perfectly when calling from VF03 in the same way, but the output fails to appear.
    In the Header -Output section inside the status of the output type is "Not Processed".
    Any ideas guys??

    Hi
    It seems that the Output determination is not taking place correctly
    the link between the Output type and Program and smartform is not established peoperly
    You have to assign this in SPRO  for the billing documents
    And most of the times it won't work we assign our custom program to the custom output type
    it is better to use the std output type and the Std program(you copy the std and can change it but the same copied ZPeogram to be attached) and Copied/modified smartform.
    check this.
    Output is a link between the Driver Program and the Sapscript,
    An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
    Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
    Check this link.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
    ex-how to config output type.
    You will assign output types using Transaction NACE.
    Do the follow steps to assign output type
    1)Select Application Type V2 which will have description Shipping.
    2)Click on Output types button.
    3)Go to change mode by pressing Ctrl+F4.
    4)Select one output type which already exists
    5)Do Copy As(F6)
    6)Give your output type against Output Type field.
    7)Under General data Tab, Give Program and Form routine and Save the data.
    i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
    Check the following documentation
    In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
    If suppose data can be read from EDI then we should go for condition records.
    So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
    Go to the Transaction NACE.
    choose the related sub module.. like billing or shipping
    doubel click on Output Types
    Choose the Output Type for which whcih you wanted your script to trigger
    Then select the Output Type and double click on Processing Routine
    Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
    Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
    Device Types for SAP Output Devices (Detail Information)
    Definition
    The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
    The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
    You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
    How do I choose the correct device type?
    • In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
    These standard device types are completely defined and need no modification or extension before you use them in device definitions.
    • You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
    • Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
    • Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
    • If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
    Attributes of a Device Type
    A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
    • Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
    • Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
    • Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
    • Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
    • Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
    • Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
    Output Determiantion :
    You can use output control to automate either messages or subsequent processing of partner-specific messages"
    This means, it provides a method for you to perform subsequent processing once a document is saved in the system. This subsequent processing is normally to print the document, but can also include activities such as:
    - Faxing the document
    - Emailing the document
    - Sending an idoc of the document
    - Sending an EDI message for the document (via an Idoc)
    - and so on.
    In general, it uses the condition technique to determine what, if any, output is to be produced. The condition technique works by selecting key fields from the document (document type, plant, etc.) and matching them to master data records you have previously set up. If there is a match, then output is produced.
    You can use transaction NACE for the output determination settings for all applications.
    1. When you start transaction NACE, a list of all represented applications appears.
    2. From this initial screen, you can access all the individual processing screens for output determination from the EDIT menu.
    3. Select the relevant application. This transaction does not have a menu path in customizing.
    Refer the following links.
    http://help.sap.com/saphelp_crm40/helpdata/en/b3/58bf39f7568648e10000000a11402f/content.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/c8/19878343b111d1896f0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/c0/4e4746497d11d385ee0000e81ddea0/content.htm
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • My Officejet Pro 8000 wireless printer prints to only 4x5" on 8x11 sheet when printing mult pages

    My Officejet Pro 8000 wireless prints to only 4x5 inches on the 8x11 sheet when I try to print multiple pages per sheet from an Adobe file.  The print preview shows the paper dimensions to be 8x11, and the four Adobe pages are properly scaled to fill the 8x11 printed sheet, yet when printing, all the printing is condensed to the upper left quarter of the sheet.

    What did it? I was still trying to figure it out

  • Hi, who can help me

    I want to print a picture to a printer, code lines used is following.
    converting image to a buffered image.
    Image i=(new javax.swing.ImageIcon("D:\\alex-projects\\ExportSystem\\export\\scanfiles\\GoldJade.bmp")).getImage();
    Frame f=new Frame();
    bi=new BufferedImage(100,50,BufferedImage.TYPE_INT_RGB);
    Graphics2D g=bi.createGraphics();
    g.drawImage(i,0,0,100,50,f);
    assuming print job variable name is pj have been initilized successfully,
    which was getting by the following code:
    PrintJob pj=frm.getToolkit().getPrintJob(frm,"Print Label",js,null); //frm who's type is JFrame had been initilized .
    Graphics g=pj.getGraphics();
    g.drawImage(bi,0,0,100,50,null);
    g.dispose();
    pj.end();
    The printting result difference with that expected by me is a black picture on a paper, I do not know why causing this problem.

    You must shift the origin of the image to printer origin and scale it to the print paper dimensions.
    Go through the following code, it might lead you in the right direction.
    PrinterJob printJob = PrinterJob.getPrinterJob ();
    PageFormat pageFormat = new PageFormat();
    // Inside the print method use the following.
    imageableX=pageFormat.getImageableX();
    imageableY=pageFormat.getImageableY();
    imageableWidth=pageFormat.getImageableWidth();
    imageableHeight=pageFormat.getImageableHeight();
    // width and height are image width,height.
    scale = Math.min(imageableWidth/width,imageableHeight/height);
    // g2d is the Graphics2D object from (Graphics2D)g of printer Graphics Contenxt
    g2d.translate(imageableX,imageableY);
    g2d.scale(scale,scale);
    g2d.drawImage(image,0,0,null);
    image.flush();
    g2d.dispose();varma

  • Pages '09 Templated Forms Not Printing in Pages 5.5.2

    I have an older Macbook Pro (circa 2009) running OSX 10.10.2 and Pages 5.5.2.  I am connected to a Canon MX320 printer.  While running my iWorks 09 version of Pages, I created a template that allowed me to print customizable checks.  I setup a template with customized settings (2.75" X 6.0" paper, 0" margins on all sides).  I would open the check "form", enter the payee, amounts, date, memo, then place the blank check into the printer and the check would print.   Since I upgraded OSX and Pages, my template no longer works.  The blank check slides through the printer with no printing being done.  I have tried changing the orientation and paper dimensions but I am unable to print with the defined paper size.  It will print with a larger sized paper (it doesn't seem to recognize the small form size).  I seek possible solutions.

    Then if you have exhausted all possible tests and printer drivers, go with what works, use Pages '09 and get a bonus 100+ features.
    Or switch to another application that does the job and has a long term future (hint not Pages 5).
    Peter

  • ID CS5.5 IDML file and missing plug-ins...need help

    I'm currently running ID CS5.5 and trying to open a CS5 file, ( I think). However, even after converting it to a IDML file extension it just hangs and forces me to shut down. The whole purpose of this is there are several plug-ins including InBooklet SE that I no longer have access to. I'm unable to find the other plugins as well but need to be able to work in this file as the original creator. Any help or suggestions?
    Here is my report:
    ADOBE INDESIGN PRINTING INSTRUCTIONS FOR SERVICE PROVIDER REPORT
    PUBLICATION NAME: 2010 Hayden Catalog 4-27-10 (CS5).indd
    PACKAGE DATE: 1/28/11 12:07 PM
    Creation Date: 1/28/11
    Modification Date: 1/28/11
    CONTACT INFORMATION
    Company Name:
    Contact:
    Address:
    Phone:
    Fax:
    Email:
    SPECIAL INSTRUCTIONS AND OTHER NOTES
    External Plug-ins 5
    InBooklet SE.4x.pln.framework
    WWStyling.pln.framework
    SmartTables.InDesignPlugin
    Style Flocker.InDesignPlugin
    SCFusionIDCS2Plugin.framework
    Non Opaque Objects :On PagePB, 5, 65, 66, 67, 69, 71, 72, 95, 96, 97, 98, 130
    FONTS
    31 Fonts Used; 0 Missing, 6 Embedded, 0 Incomplete, 0 Protected
    Fonts Packaged
    - Name: Arial-BoldMT; Type: TrueType, Status: Embedded
    - Name: ArialMT; Type: TrueType, Status: Embedded
    - Name: Eurostile; Type: Type 1, Status: OK
    - Name: Eurostile-Bold; Type: Type 1, Status: OK
    - Name: EurostileBold; Type: OpenType TrueType, Status: OK
    - Name: Futura-Condensed; Type: Type 1, Status: OK
    - Name: Futura-CondensedBold; Type: Type 1, Status: OK
    - Name: Futura-CondensedBoldOblique; Type: Type 1, Status: OK
    - Name: Futura-CondensedExtraBold; Type: Type 1, Status: OK
    - Name: Futura-CondensedLight; Type: Type 1, Status: OK
    - Name: Futura-CondensedOblique; Type: Type 1, Status: OK
    - Name: Futura-ExtraBold; Type: Type 1, Status: OK
    - Name: Futura-ExtraBoldOblique; Type: Type 1, Status: OK
    - Name: Futura-Heavy; Type: Type 1, Status: OK
    - Name: Helvetica-Bold; Type: Type 1, Status: OK
    - Name: Helvetica-BoldOblique; Type: Type 1, Status: OK
    - Name: Helvetica-Condensed-Bold; Type: Type 1, Status: OK
    - Name: HelveticaNeue-BoldCond; Type: Type 1, Status: OK
    - Name: HelveticaNeue-BoldItalic; Type: Type 1, Status: OK
    - Name: MyriadPro-Regular; Type: Type 1, Status: Embedded
    - Name: OfficinaSans-Bold; Type: Type 1, Status: OK
    - Name: OfficinaSans-Book; Type: Type 1, Status: Embedded
    - Name: OfficinaSans-BookItalic; Type: Type 1, Status: OK
    - Name: Techno; Type: Type 1, Status: Embedded
    - Name: TechnoRegular; Type: TrueType, Status: OK
    - Name: Times-BoldItalic; Type: TrueType, Status: OK
    - Name: Times-Italic; Type: TrueType, Status: OK
    - Name: Times-Roman; Type: TrueType, Status: OK
    - Name: Times-Roman; Type: TrueType, Status: OK
    - Name: Universal-NewswithCommPi; Type: Type 1, Status: Embedded
    - Name: ZapfDingbats; Type: Type 1, Status: OK
    COLORS AND INKS
    4 Process Inks; 0 Spot Inks
    - Name and Type: Process Cyan; Angle: 0.000; Lines/Inch: 0.000
    - Name and Type: Process Magenta; Angle: 0.000; Lines/Inch: 0.000
    - Name and Type: Process Yellow; Angle: 0.000; Lines/Inch: 0.000
    - Name and Type: Process Black; Angle: 0.000; Lines/Inch: 0.000
    LINKS AND IMAGES
    (Missing & Embedded Links Only)
    Links and Images: 284 Links Found; 0 Modified, 0 Missing 0 Inaccessible
    Images: 0 Embedded, 0 use RGB color space
    PRINT SETTINGS
    PPD: N/A, (AL-CX11-D06AAC)
    Printing To: Printer
    Number of Copies: 1
    Reader Spreads: No
    Even/Odd Pages: Both
    Pages: All
    Proof: No
    Tiling: None
    Scale: Scale to fit page
    Page Position: Center
    Print Layers: Visible & Printable Layers
    Printer's Marks: Crops
    Bleed: 0p0, 0p0, 0p0, 0p0
    Color: Composite RGB
    Trapping Mode: None
    Send Image Data: All
    OPI/DCS Image Replacement: No
    Page Size: Custom: 50p2.64 x 65p2.64
    Paper Dimensions: 51p0 x 66p0
    Orientation: Portrait
    Negative: No
    Flip Mode: Off
    FILE PACKAGE LIST
    1. 2010 Hayden Catalog 4-27-10 (CS5).indd; type: Adobe InDesign publication; size: 97320K
    2. Euros; type: Font file; size: 27K
    3. Eurostile; type: Font file; size: 7K
    4. EurosBol; type: Font file; size: 29K
    5. Eurostile-Bold; type: Font file; size: 5K
    6. FuturCon; type: Font file; size: 26K
    7. Futura-Condensed; type: Font file; size: 7K
    8. FuturConBol; type: Font file; size: 28K
    9. Futura-CondensedBold; type: Font file; size: 5K
    10. FuturConBolObl; type: Font file; size: 36K
    11. Futura-CondensedBoldOblique; type: Font file; size: 4K
    12. FuturConExtBol; type: Font file; size: 29K
    13. Futura-CondensedExtraBold; type: Font file; size: 5K
    14. FuturConLig; type: Font file; size: 27K
    15. Futura-CondensedLight; type: Font file; size: 5K
    16. FuturConObl; type: Font file; size: 34K
    17. Futura-CondensedOblique; type: Font file; size: 5K
    18. FuturExtBol; type: Font file; size: 29K
    19. Futura-ExtraBold; type: Font file; size: 6K
    20. FuturExtBolObl; type: Font file; size: 40K
    21. Futura-ExtraBoldOblique; type: Font file; size: 5K
    22. FuturHea; type: Font file; size: 28K
    23. Futura-Heavy; type: Font file; size: 5K
    24. HelveBol; type: Font file; size: 29K
    25. Helvetica-Bold; type: Font file; size: 8K
    26. HelveBolObl; type: Font file; size: 38K
    27. Helvetica-BoldOblique; type: Font file; size: 8K
    28. HelveConBol; type: Font file; size: 30K
    29. Helvetica-Condensed-Bold; type: Font file; size: 7K
    30. HelveNeuBolCon; type: Font file; size: 29K
    31. HelveticaNeue-BoldCond; type: Font file; size: 7K
    32. HelveNeuBolIta; type: Font file; size: 31K
    33. HelveticaNeue-BoldItalic; type: Font file; size: 8K
    34. OfficSanBol; type: Font file; size: 32K
    35. OfficinaSans-Bold; type: Font file; size: 12K
    36. OfficSanBooIta; type: Font file; size: 33K
    37. OfficinaSans-BookItalic; type: Font file; size: 11K
    38. TechnoRegular; type: Font file; size: 87K
    39. Times-BoldItalic; type: Font file; size: 91K
    40. Times-Italic; type: Font file; size: 92K
    41. Times-Roman; type: Font file; size: 89K
    42. ZapfDin; type: Font file; size: 40K
    43. ZapfDingbats; type: Font file; size: 4K

    You can't convert to .idml by changing the file extension. You must export the file from the oringal version as a .idml file.
    That said, you can use jongware's script to identify the version of the file, even if it won't open: Adobe Forums: [Ann] Identify Your InDesign File
    That said, InBooklet SE was part of InDesign CS3, but I see it listed inthe plugins used. I also see a number of what look like third-party plugins listed, and that may be the problem. What's happening when you try to open the file?

  • General questions

    hi,
    i have some doubts in reports.pls tell the answers.
    which contain the details of all name of the programs and forms?
    difference between pooled and cluster tables?
    what are output types and tcodes?
    what are the main events that are used in alv reports?
    thanx and regrads
    priya

    Hi
    which contain the details of all name of the programs and forms?
    In TNAPR table you will find them.
    difference between pooled and cluster tables?
    Pooled table
    Pooled tables can be used to store control data (e.g. screen sequences,
    program parameters or temporary data). Several pooled tables can be
    combined to form a table pool. The table pool corresponds to a physical
    table on the database in which all the records of the allocated pooled
    tables are stored.
    Cluster table
    Cluster tables contain continuous text, for example documentation.
    Several cluster tables can be combined to form a table cluster. Several
    logical lines of different tables are combined to form a physical record
    in this table category. This permits object-by-object storage or
    object-by-object access. In order to combine tables in clusters, at
    least part of the keys must agree. Several cluster tables are stored in
    one corresponding table on the database.
    what are output types and tcodes?
    Output is a link between the Driver Program and the Sapscript,
    An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
    Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
    Check this link.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
    ex-how to config output type.
    You will assign output types using Transaction NACE.
    Do the follow steps to assign output type
    1)Select Application Type V2 which will have description Shipping.
    2)Click on Output types button.
    3)Go to change mode by pressing Ctrl+F4.
    4)Select one output type which already exists
    5)Do Copy As(F6)
    6)Give your output type against Output Type field.
    7)Under General data Tab, Give Program and Form routine and Save the data.
    i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
    Check the following documentation
    In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
    If suppose data can be read from EDI then we should go for condition records.
    So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
    Go to the Transaction NACE.
    choose the related sub module.. like billing or shipping
    doubel click on Output Types
    Choose the Output Type for which whcih you wanted your script to trigger
    Then select the Output Type and double click on Processing Routine
    Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
    Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
    Device Types for SAP Output Devices (Detail Information)
    Definition
    The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
    The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
    You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
    How do I choose the correct device type?
    • In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
    These standard device types are completely defined and need no modification or extension before you use them in device definitions.
    • You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
    • Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
    • Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
    • If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
    Attributes of a Device Type
    A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
    • Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
    • Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
    • Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
    • Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
    • Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
    • Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
    OUTPUT EXECUTION TCODES
    ME9F - Pur Order Output
    ME9A -  RFQ Output
    ME9K - Contract Output
    MB90 - GRN Output
    VA02/VA03  - Sales order Output
    VF03/VF02  - Invoice output
    VL71   - Delivery Output
    VT70 - Shipment Output
    VL74 - Handling Unit Output
    what are the main events that are used in alv reports?
    REUSE_ALV_EVENTS_GET
    Description
    This table tells ALV which events are processed by the caller by CALLBACK.
    The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.
    You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module
    REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.
    The table structure contains the fields:
    •     IT_EVENTS-NAME
    Name of the Callback event.
    Possible Callback events:
    •     Action
    USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD
    Process actions on the list
    As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
    PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
    If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
    The STANDARD status of the function group SALV should be used as a template for a user-specific status.
    As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
    ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C
    Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.
    Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.
    RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.
    RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.
    CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.
    •     List processing events
    IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.
    TOP_OF_LIST no USING parameter. Information output at the start of the list
    END_OF_LIST no USING parameter. Information output at the end of the list
    TOP_OF_PAGE no USING parameter
    Equivalent to the list processing TOP-OF-PAGE event
    END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.
    Information output at the end of a page. This is only called for printing.
    TOP_OF_COVERPAGE no USING parameter
    The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:
    IS_PRINT-NO_COVERPAGE
    IS_PRINT-NO_PRINT_SELINFOS
    IS_PRINT-NO_PRINT_LISTINFOS
    IS_LAYOUT-GET_SELINFOS
    The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.
    END_OF_COVERPAGE no USING parameter
    Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.
    FOREIGN_TOP_OF_PAGE no USING parameter
    The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
    In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
    FOREIGN_END_OF_PAGE no USING parameter
    The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
    In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
    BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
    Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
    AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
    Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
    •     Internal use only
    LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
    R_INDEX LIKE SY-TABIX
    R_INDEX_ITEM LIKE SY-TABIX
    R_INDEX_SUM LIKE SY-TABIX
    •     IT_EVENTS-FORM
    Name of the form routine which should be called in the calling program at the event.
    Field_catalog:
    Field catalog with field descriptions
    2.7.1.     Description
    Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
    The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
    See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
    The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
    A field catalog need not be built-up and passed explicitly only under the following conditions:
    •     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
    •     all fields in this structure are to be output
    •     the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
    See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
    Positioning
    •     row_pos (row position)
    value set: 0, 1 - 3
    Only relevant if the list output is to be multi-line (two or three lines) by default.
    A multi-line list can also be defined by the user interactively if the default list is one-line.
    The parameter specifies the relative output line of the column in a multi-line list.
    •     col_pos (column position)
    value set: 0, 1 - 60
    only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
    Identification
    •     fieldname (field name)
    value set: internal output table field name (required parameter)
    Name of the internal output table field which is described by this field catalog entry
    •     tabname (internal output table)
    value set: SPACE, internal output table name
    This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
    Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
    Data Dictionary reference
    •     ref_fieldname (reference field name)
    value set: SPACE, Data Dictionary field name
    Name of the Data Dictionary field referred to.
    This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
    •     ref_tabname (reference table/structure field name)
    value set: SPACE, name of a Data Dictionary structure or table
    Structure or table name of the referred Data Dictionary field.
    This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
    Reference to fields with currency/measurement unit
    Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
    •     the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
    •     There is a field in the internal output table which contains the associated unit.
    •     There is also an entry in the field catalog for the unit field.
    (If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
    The association of a value field to a unit affects the output as follows:
    •     appropriate decimal places display for the unit
    •     an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
    •     an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
    •     When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
    Link to currency unit
    •     cfieldname (currency unit field name)
    value set: SPACE, output table field name
    Only relevant for amount columns with associated unit.
    Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
    •     ctabname (internal currency unit field output table)
    value set: SPACE, output table field name
    only relevant for hierarchical-sequential lists
    Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
    Link to measurement unit
    •     qfieldname (measurement unit field name)
    value set: SPACE, output table field name
    only relevant for quantity columns with unit link.
    Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
    The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
    •     qtabname (internal measurement unit field output table)
    value set: SPACE, output table field name
    only relevant for hierarchical-sequential lists
    Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
    Column output options
    •     outputlen (column width)
    value set: 0 (initial), n
    For fields with a Data Dictionary link this parameter can be left initial.
    For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
    initial = column width is the output length of the referred Data Dictionary field (domain).
    n = column width is n characters
    •     key (key column)
    value set: SPACE, 'X'           'X' = kex field (key field output in color)
    Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
    For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
    •     key_sel (hideable key column)
    value set: SPACE, 'X'
    only relevant when FIELDCAT-KEY = 'X'
    Key field which can be hidden interactively.
    The key column sequence cannot be changed interactively by the user.
    The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
    •     no_out (field in field list)
    value set: SPACE, 'X'          'X' = field is not displayed in the current list.
    The user can interactively choose the field for output from the field list.
    The user can display the contents of these fields at line level using the 'Detail' function.
    See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
    •     tech (technical field)
    value set: SPACE, 'X'          'X' = technical field
    Field cannot be output in the list and cannot be displayed interactively.
    Field can only be used in the field catalog (not in IT_SORT, ...).
    •     emphasize (highlight columns in color)
    value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
    'X' = column is colored with the default column highlight color.
    'Cxyz' = column is colored with a coded color:
    •     C: Color (coding must begin with C)
    •     x: color number
    •     y: bold
    •     z: inverse
    •     hotspot (column as hotspot)
    value set: SPACE, 'X'
    'X' = column cells are output as hotspots
    •     fix_column (fix column)
    value set: SPACE, 'X'
    Not relevant for block lists (output of several lists consecutively)
    'X' = column fixed (does not scroll horizontally)
    All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
    IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
    •     do_sum (sum over column)
    value set: SPACE, 'X'           'X' = a sum is to be calculated over this internal output table field.
    This function can also be called by the user interactively.
    •     no_sum (sums forbidden)
    value set: SPACE, 'X'          'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
    •     input (column ready for input)
    Function not available
    Format column contents
    •     icon
    value set: SPACE, 'X'           'X' = column contents to be output as an icon.
    The caller must consider the printability of icons.
    •     symbol
    value set: SPACE, 'X'          'X' = column contents are to be output as a symbol.
    The internal output table column must be a valid symbol character.
    The caller must consider the printability of symbols.
    Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
    •     just (justification)
    value set: SPACE, 'R', 'L', 'C'
    Only relevant for fields of data type CHAR or NUMC
    ' ' = default justification for this data type
    'R' = right-justified output
    'L' = left-justified output
    'C' = centered output
    The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
    •     lzero (leading zeros)
    value set: SPACE, 'X'
    Only relevant for fields of data type NUMC
    ALV outputs NUMC fields right-justified without leading zeros by default.
    'X' = output with leading zeros
    Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
    •     no_sign (no +/- sign)           Only relevant for value fields
    value set: SPACE, 'X'     'X' = value output without +/ sign
    •     no_zero (suppress zeros)           Only relevant for value fields
    value set: SPACE, 'X'          'X' = suppress zeros
    •     edit_mask (field formatting)
    value set: SPACE, template
    template = see documentation of WRITE formatting option USING EDIT MASK template
    The output conversion conv can be made by template = '== conv'.
    Texts
    The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
    The 'long field label' is also used in display variant definition, sort, etc. popups.
    •     seltext_l (long field label)
    •     seltext_m (medium field label)
    •     seltext_s (short field label)
    •     reptext_ddic (header)
    analogous to the Data element maintenance 'Header'
    The specified text is not necessarily output in the list, an optimum among all texts is sought.
    •     ddictxt (specify text)
    value set: SPACE, 'L', 'M', 'S'
    You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
    Parameters for program fields without Data Dictionary reference
    see also 'Text' parameters
    •     datatype (data type)
    value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
    Only relevant for fields without Data Dictionary reference
    Program field data type
    •     ddic_outputlen (external output length)
    value set: 0 (initial), n
    Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
    Prerequisites:
    •     FIELDCAT-EDIT_MASK = '==conv'
    see also the documentation of the parameter FIELDCAT-EDIT_MASK
    •     FIELDCAT-INTLEN = n
    see also the documentation of the parameter FIELDCAT-INTLEN
    n = external format field output length
    The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
    •     intlen (internal output length)
    value set: 0 (initial), n
    Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
    Prerequisites:
    •     FIELDCAT-EDIT_MASK = '==conv'
    see also the documentation of the parameter FIELDCAT-EDIT_MASK
    •     FIELDCAT-DDIC_OUTPUTLEN = n
    see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
    n = internal format field output length
    •     rollname (data element)
    value set: SPACE, Data Dictionary data element name
    F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
    When F1 help is called for this field, the documentation of the specified data element is displayed.
    If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
    Others
    •     sp_group (field group key)
    value set: SPACE, CHAR(1)
    Field group key.
    Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
    When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
    •     reprep (Report/Report interface selection criterion)
    value set: SPACE, 'X'
    Prerequisites:
    •     The system contains the Report/Report interface (function group RSTI, table TRSTI)
    •     Parameter LAYOUT-REPREP = 'X'
    (see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
    'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
    2.7.2.     Default
    •     The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
    •     fieldname
    •     ref_tabname
    Notes:
    ALV gets the remaining information from the Data Dictionary.
    If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
    REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
    Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
    Priority rule:
    Entries in the field catalog have priority over differing entries in the Data Dictionary.
    •     The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
    •     fieldname
    •     outputlen
    •     datatype
    •     seltext_s
    •     seltext_m
    •     seltext_l
    Notes:
    F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
    If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.
    Reward points for useful Answers
    Regards
    Anji

  • Printing to a PDF

    I have the following class:
    import java.awt.*;
    import javax.swing.*;
    import java.awt.print.*;
    public class PrintUtilities implements Printable {
      private Component componentToBePrinted;
      public static void printComponent(Component c) {
        new PrintUtilities(c).print();
      public PrintUtilities(Component componentToBePrinted) {
        this.componentToBePrinted = componentToBePrinted;
      public void print() {
        PrinterJob printJob = PrinterJob.getPrinterJob();
           PageFormat pageFormat = new PageFormat();
           if(printJob.pageDialog(printJob.defaultPage()).getOrientation()==pageFormat.LANDSCAPE){
             try{
                     pageFormat.setOrientation(pageFormat.LANDSCAPE);
              catch(java.lang.IllegalStateException ise){
                      System.out.println("Print error...\n"+ise);
          printJob.setPrintable(this,pageFormat);
           if (printJob.printDialog()){
               try{
                    printJob.print();
               catch(java.awt.print.PrinterException pe){
                    System.out.println("Could not print...\n" + pe);
    /*   printJob.setPrintable(this);
        if (printJob.printDialog())
          try {
            printJob.print();
          } catch(PrinterException pe) {
            System.out.println("Error printing: " + pe);
      public int print(Graphics g, PageFormat pageFormat, int pageIndex) {
         if (pageIndex > 0) {
         return(NO_SUCH_PAGE);
         else {
              Graphics2D g2d = (Graphics2D)g;
              Toolkit toolkit = componentToBePrinted.getToolkit();
              /* scaling is added to fit printout of maximized birdseye
              window onto a 8.5 X 11 sheet of paper
              Dimension screenSize = toolkit.getScreenSize();
              //fit screen to printable (landscape) page
              double scaleX = (pageFormat.getImageableWidth()) / (screenSize.getWidth());
              double scaleY = (pageFormat.getImageableHeight())/(screenSize.getHeight());
              if(scaleX>.3){
                   double scaleFactor = java.lang.Math.min((double)(screenSize.getWidth())/
                   (double)(pageFormat.getImageableWidth()),(double)(screenSize.getHeight())/(double)(pageFormat.getImageableHeight()));
                   g2d.translate(pageFormat.getImageableX(), pageFormat.getImageableY());
                   g2d.scale(.7/scaleFactor,.95/scaleFactor);
              else{
                   double scaleFactor = java.lang.Math.min((double)(screenSize.getWidth())/
                   (double)(pageFormat.getImageableWidth()),(double)(screenSize.getHeight())/(double)(pageFormat.getImageableHeight()));
                   g2d.translate(pageFormat.getImageableX(), pageFormat.getImageableY());
                   g2d.scale(.85/scaleFactor,.95/scaleFactor);
              /** It is important that translation be done before the scaling.
              * Failure to follow this order will result in unusual behavior
              * such as strange cropping
              //g2d.translate(pageFormat.getImageableX(),
              //pageFormat.getImageableY());
              //g2d.scale(scaleX,scaleY);
              // speeds up printing process
              disableDoubleBuffering(componentToBePrinted);
              componentToBePrinted.printAll(g2d);
              enableDoubleBuffering(componentToBePrinted);
              return(PAGE_EXISTS);
      public static void disableDoubleBuffering(Component c) {
        RepaintManager currentManager = RepaintManager.currentManager(c);
        currentManager.setDoubleBufferingEnabled(false);
      public static void enableDoubleBuffering(Component c) {
        RepaintManager currentManager = RepaintManager.currentManager(c);
        currentManager.setDoubleBufferingEnabled(true);
    }It prints well for the most part. The problem is that I have Adobe Acrobat 6 Professional and I want to
    create a pdf using the print class that I have, however it doesn't work. I click the print button in my GUI, and
    it calls the PrintUtilities class functions, and I select the printer to be the Adobe PDF Writer, but then I get the following exception message when I click 'ok' to print:
    java.lang.IllegalArgumentException: Zero length string passed to TextLayout cons
    tructor.
    at java.awt.font.TextLayout.<init>(TextLayout.java:471)
    at sun.java2d.pipe.OutlineTextRenderer.drawString(OutlineTextRenderer.ja
    va:67)
    at sun.java2d.pipe.GlyphListPipe.drawString(GlyphListPipe.java:32)
    at sun.java2d.SunGraphics2D.drawString(SunGraphics2D.java:2534)
    at sun.print.ProxyGraphics2D.drawString(ProxyGraphics2D.java:720)
    at javax.swing.plaf.basic.BasicGraphicsUtils.drawStringUnderlineCharAt(B
    asicGraphicsUtils.java:234)
    at javax.swing.plaf.basic.BasicLabelUI.paintEnabledText(BasicLabelUI.jav
    a:81)
    at javax.swing.plaf.basic.BasicLabelUI.paint(BasicLabelUI.java:164)
    at javax.swing.plaf.ComponentUI.update(ComponentUI.java:142)
    at javax.swing.JComponent.paintComponent(JComponent.java:541)
    at javax.swing.JComponent.printComponent(JComponent.java:908)
    at javax.swing.JComponent.paint(JComponent.java:812)
    at javax.swing.JComponent.print(JComponent.java:891)
    at javax.swing.JComponent.paintChildren(JComponent.java:651)
    at javax.swing.JComponent.printChildren(JComponent.java:921)
    at javax.swing.JComponent.paint(JComponent.java:820)
    at javax.swing.JComponent.print(JComponent.java:891)
    at javax.swing.JComponent.paintChildren(JComponent.java:651)
    at javax.swing.JComponent.printChildren(JComponent.java:921)
    at javax.swing.JComponent.paint(JComponent.java:820)
    at javax.swing.JComponent.print(JComponent.java:891)
    at javax.swing.JComponent.paintChildren(JComponent.java:651)
    at javax.swing.JComponent.printChildren(JComponent.java:921)
    at javax.swing.JComponent.paint(JComponent.java:820)
    at javax.swing.JLayeredPane.paint(JLayeredPane.java:557)
    at javax.swing.JComponent.print(JComponent.java:891)
    at javax.swing.JComponent.paintChildren(JComponent.java:651)
    at javax.swing.JComponent.printChildren(JComponent.java:921)
    at javax.swing.JComponent.paint(JComponent.java:820)
    at javax.swing.JComponent.print(JComponent.java:891)
    at java.awt.GraphicsCallback$PrintCallback.run(GraphicsCallback.java:32)
    at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:
    60)
    at sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallback.java:97
    at java.awt.Container.print(Container.java:1367)
    at sun.awt.windows.WComponentPeer.print(WComponentPeer.java:223)
    at sun.awt.windows.WCanvasPeer.print(WCanvasPeer.java:97)
    at sun.awt.windows.WPanelPeer.print(WPanelPeer.java:26)
    at java.awt.GraphicsCallback$PeerPrintCallback.run(GraphicsCallback.java
    :85)
    at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:
    60)
    at java.awt.Component.printAll(Component.java:2532)
    at PrintUtilities.print(PrintUtilities.java:95)
    at sun.print.RasterPrinterJob.printPage(RasterPrinterJob.java:1628)
    at sun.print.RasterPrinterJob.print(RasterPrinterJob.java:1085)
    at sun.print.RasterPrinterJob.print(RasterPrinterJob.java:986)
    at PrintUtilities.print(PrintUtilities.java:32)
    at PrintUtilities.printComponent(PrintUtilities.java:9)
    at gui.actionPerformed(gui.java:8369)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:17
    86)
    at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Abstra
    ctButton.java:1839)
    at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel
    .java:420)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258
    at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
    at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1
    113)
    at javax.swing.plaf.basic.BasicMenuItemUI$MenuDragMouseHandler.menuDragM
    ouseReleased(BasicMenuItemUI.java:1006)
    at javax.swing.JMenuItem.fireMenuDragMouseReleased(JMenuItem.java:584)
    at javax.swing.JMenuItem.processMenuDragMouseEvent(JMenuItem.java:481)
    at javax.swing.JMenuItem.processMouseEvent(JMenuItem.java:428)
    at javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManag
    er.java:277)
    at javax.swing.plaf.basic.BasicMenuUI$MouseInputHandler.mouseReleased(Ba
    sicMenuUI.java:360)
    at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:2
    31)
    at java.awt.Component.processMouseEvent(Component.java:5100)
    at java.awt.Component.processEvent(Component.java:4897)
    at java.awt.Container.processEvent(Container.java:1569)
    at java.awt.Component.dispatchEventImpl(Component.java:3615)
    at java.awt.Container.dispatchEventImpl(Container.java:1627)
    at java.awt.Component.dispatchEvent(Component.java:3477)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
    at java.awt.Container.dispatchEventImpl(Container.java:1613)
    at java.awt.Window.dispatchEventImpl(Window.java:1606)
    at java.awt.Component.dispatchEvent(Component.java:3477)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchTh
    read.java:201)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
    ad.java:151)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

    SIr
    I am also doing the same to print a component. I need to print a table data. When i send myTable object
    PrintUtility.printComponent(myTable).
    It just prints as much table data as fits into 1 page. But i want to print whole table data that may be multipage. Please suggest something if can. thanx

  • Printing in Mac OS X

    Hello all,
    I created a printable class that works in Windows and Linux, but for some reason will not work on Mac OS X. It either prints a blank page or throws a nasty exception:
    Exception in thread "Thread-0" java.lang.NullPointerException
    at javax.swing.plaf.metal.BumpBuffer.fillBumpBuffer(MetalBumps.java:183)
    at javax.swing.plaf.metal.BumpBuffer.<init>(MetalBumps.java:148)
    at javax.swing.plaf.metal.MetalBumps.getBuffer(MetalBumps.java:71)
    at javax.swing.plaf.metal.MetalBumps.paintIcon(MetalBumps.java:97)
    at javax.swing.plaf.metal.MetalScrollBarUI.paintThumb(MetalScrollBarUI.java:242)
    at javax.swing.plaf.basic.BasicScrollBarUI.paint(BasicScrollBarUI.java:301)
    at javax.swing.plaf.ComponentUI.update(ComponentUI.java:142)
    at javax.swing.JComponent.paintComponent(JComponent.java:541)
    at javax.swing.JComponent.paint(JComponent.java:808)
    at javax.swing.JComponent.paintChildren(JComponent.java:647)
    at javax.swing.JComponent.paint(JComponent.java:817)
    at javax.swing.JComponent.paintChildren(JComponent.java:647)
    at javax.swing.JComponent.paint(JComponent.java:817)
    at javax.swing.JComponent.paintChildren(JComponent.java:647)
    at javax.swing.JComponent.paint(JComponent.java:817)
    at javax.swing.JLayeredPane.paint(JLayeredPane.java:557)
    at javax.swing.JComponent.paintChildren(JComponent.java:647)
    at javax.swing.JComponent.paint(JComponent.java:817)
    at java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback.java:21)
    at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:60)
    at sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallback.java:97)
    at java.awt.Container.paint(Container.java:1312)
    at apple.awt.CComponent.print(CComponent.java:130)
    at apple.awt.ContainerModel.print(ContainerModel.java:633)
    at java.awt.GraphicsCallback$PeerPrintCallback.run(GraphicsCallback.java:85)
    at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:60)
    at java.awt.Component.printAll(Component.java:2532)
    at PrintUtilities.print(PrintUtilities.java:111)
    at apple.awt.CPrinterJob.printToPathGraphics(CPrinterJob.java:509)
    JavaAWT: Assertion failure: Java exception thrown
    JavaAWT: File src/macosx/native/apple/awt/util/AWTException.m; Line 40
    JavaAWT: Assertion failure: _javaException
    JavaAWT: File src/macosx/native/apple/awt/util/AWTException.m; Line 48
    2004-06-28 10:34:43.295 java[448] PMSessionEndDocumentNoDialog failed (error code = -30879)
    2004-06-28 10:34:43.297 java[448] *** -[NSAutoreleasePool dealloc]: Exception ignored while releasing an object in an autorelease pool: NSInternalInconsistencyException Failed to end PMPrintContext
    *** malloc[448]: Deallocation of a pointer not malloced: 0xbfffc7c0; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
    I am using Java 1.4.2. Any ideas?
    Here is my code:
    import java.awt.*;
    import javax.swing.*;
    import java.awt.print.*;
    public class PrintUtilities implements Printable {
      private Component componentToBePrinted;
      public static void printComponent(Component c) {
        new PrintUtilities(c).print();
      public PrintUtilities(Component componentToBePrinted) {
        this.componentToBePrinted = componentToBePrinted;
      public void print() {
        PrinterJob printJob = PrinterJob.getPrinterJob();
           PageFormat pageFormat = new PageFormat();
           printJob.setPrintable(this, pageFormat);
           if(printJob.pageDialog(printJob.defaultPage()).getOrientation()==pageFormat.LANDSCAPE){
             try{
                     pageFormat.setOrientation(pageFormat.LANDSCAPE);
              catch(java.lang.IllegalStateException ise){
                      System.out.println("Print error...\n"+ise);
          printJob.setPrintable(this,pageFormat);
           if (printJob.printDialog()){
               try{
                    printJob.print();
               catch(java.awt.print.PrinterException pe){
                    System.out.println("Could not print...\n" + pe);
      public int print(Graphics g, PageFormat pageFormat, int pageIndex) {
         if (pageIndex > 0) {
         return(NO_SUCH_PAGE);
         else {
              Graphics2D g2d = (Graphics2D)g;
              Toolkit toolkit = componentToBePrinted.getToolkit();
              /* scaling is added to fit printout of maximized birdseye
              window onto a 8.5 X 11 sheet of paper
              Dimension screenSize = toolkit.getScreenSize();
              /** It is important that translation be done before the scaling.
              * Failure to follow this order will result in unusual behavior
              * such as strange cropping
              g2d.translate(pageFormat.getImageableX(),
              pageFormat.getImageableY());
              g2d.scale(.45,.45);
              //g2d.scale(scaleX,scaleY);
              // speeds up printing process
              disableDoubleBuffering(componentToBePrinted);
              componentToBePrinted.printAll(g2d);
              enableDoubleBuffering(componentToBePrinted);
              return(PAGE_EXISTS);
      public static void disableDoubleBuffering(Component c) {
        RepaintManager currentManager = RepaintManager.currentManager(c);
        currentManager.setDoubleBufferingEnabled(false);
      public static void enableDoubleBuffering(Component c) {
        RepaintManager currentManager = RepaintManager.currentManager(c);
        currentManager.setDoubleBufferingEnabled(true);
    }Thanks

    pharmastat59 wrote:
    Trouble printint to a Dell Laser MFP 1815dn.
    Check if the Dell driver is PPC. If it is, and if you installed the first version of Apple's latest Security Update, then that's probably where the issue is, because it broke Rosetta, the software which runs PPC code under SL. Re-install the Sec Update (the problem is fixed in v1.1, which replaced the goofy version on Apple's servers) through Software Update or by downloading it again, then re-install the Dell driver, and try again.
    Apple stuff is great, except for their casual disregard of their customers who want to use any product that is not Apple
    I'm sorry, but that's non-sense. I'm no fan of Apple, but they're no better and no worse than any large corporation of this type. Mostly, they do things which make business sense as they see it -- which is exactly what you'd want, if you had serious money invested in Apple shares -- wouldn't you?
    In this instance, it was up to Dell to release an Intel Mac driver for this printer/scanner, which is, what, 5 or 6 years old? If they didn't, it was probably because they decided it didn't make business sense for them to spend money on developing and testing one. Keep in mind that Dell and Apple and Microsoft and all the rest are in business to make money, not to support every single customer for ever and ever and a day.

  • When converting word doc to pdf with Acrobat words getting cut off?

    Hi all,
    As you can see from this example:
    When converting from word document the words on the pages in the final PDF are getting cut off on the edge of the page?
    I've adjusted the margins in page layout in MS Word to Normal, Moderate & Wide etc, etc
    Never ever had this problem before...does anybody have any idea why or what I could do?
    Thanks in advance.

    As a quick check, set the printer to the Adobe PDF printer in WORD and then check for the proper operation. Also be sure the paper dimensions and orientation of your document and the printer properties match up (I have had some problems with the orientation when I have auto-rotate on). You may have to play some to get something to work. I have done that before and settled on a process that works for me, but I can't claim it all makes perfect sense. To many things are going on in some sense.

  • How to create jpegs from pdfs without pixellated results

    I have been creating jpegs from high quality pdfs (typically 20-30 MB files) of maps (paper dimensions roughly 2 ft by 3 ft) with no problems until this week.  I use the export function in Adobe X Standard and select jpeg.  Did I recently get an update which changed my settings?  Now I notice that sometimes the process generates a progress bar which says it is optimizing the content for the web.  I don't remember seeing this either.  Previous conversions worked great and the jpegs could be blown up on the screen with crisp detail.  Yesterday I did the same process with a new map (I checked it for good resolution and the pdf can be zoomed way in with no loss of resolution). But the resulting jpeg pixellates very quickly when zooming in.  What gives?  It may be possible that this new map (pdf) is in layers.  I think the others were scans of the paper maps.  Does this affect the conversion?  Also noticed that the jpegs now have little lock symbols on them.  Is that related?  I don't think it is, because a map I recently converted has the lock symbol on it and is OK (as a jpeg).  I am converting the pdfs into jpegs so I can import them into Autocad.

    As the helpcenter(2005 helpcenter) has missed this bit of documentation (on UserQueries) could someone please provide an example of using this object
    thanks
    Message was edited by: George Savery
    hmm I thought it had timed out .... Woops

Maybe you are looking for

  • Transaction Codes used for clearing Open Items

    Hi Gurus, I want to know all the T.Codes used for clearing normal transactions and Open Items. Please tell me when to use which code (viz., while clearing vendors, customers, WH Tax, etc) Your earliest reply will be of great help. and naturally i wil

  • Passing a Path string results in mangled name

    So I have a script that I made that takes a bunch of PDFs from a folder, and puts the resulting PDF into DropBox's Public folder. So, the DropBox path is ~/ericdannewitz/Dropbox/Public/JulieanneMartin/ and the file name would be JuileAnne Martin - 08

  • ODBC: connect from oracle to filmaker pro 7 to extract data

    sorry for the cross post, i posted this in th ODBC forum, but that's in the windows.net subhead, so idunno. here is is again: we have a filemaker pro server and some of the data needs to be imported weekly into an oracle database. my understanding is

  • How to play you own movies on i PAD2

    peoeple i cant seem to sync my own movies from my hardrive or etc. please if you know how and if it is possible assist

  • Brand new MBP with a problem...

    We just bought a 15" MBP 2.0 today for my wife and had them install an extra gig at the store. We brought it home and she immediately began downloading the updates. While downloading she was poking around with Safari. About 3/4 of the way through the