Delivery output print preview issue.

Hello Friends,
While going for the print preview of the outbound delivery by T-code VL71 i am getting the message-->
"Output could not be displayed (it may not be complete)
Message no. VN069"
As i have maintained VV21 & output type in the delivery.
Please help me with the solution.
Thank you.
Sadanand.

hi
did u maintained the output type in NACE for appliacation V2
and also check whether u have maintained the custom form in smartforms place
Output type LD00
trans medium : 1
short tecxt : print out
Program ; RLE_DELNOTE
FORM routine : ENTRY
smartforms : ur z form
trans medium : 2
short text : fax
Program ; RLE_DELNOTE
FORM routine : ENTRY
smartforms : LE_SHP_DELNOTE
hopre this would sove ur problem.
Regards,
Venkat.
Edited by: venkatakrishnan Parthsarathy on Apr 14, 2008 2:40 PM

Similar Messages

  • Delivery challan print preview for transaction j1if01 problem

    hi , i have problem with print preview of delivery challan. after creating it from j1if01 im unable to get a print preview of it
    as i dont find any tab or button for print preview .
    plz guide me how can i  get an output . also plz give form name for it . thanks !!

    In u2022     SPRO > Logistics - General > Tax on Goods Movements > India > Business Transactions > Subcontracting > Subcontracting Attributes maintain the Output type. Other attributes are as under fyi
    Excise Group         XX
    Excise TT            57FC
    Subtransaction Type  01
    Subtran Type Text   57FC CHALLAN
    Subc. Period        180
    Rate-subcontracting
    Mvt Grp Issues      0001
    Mvt Grp Receipt     0002
    Filter Non exise    X
    EI Items            10
    No. range no.       01
    ***. Val. /Exc Inv
    Subcon Output Type  J1IF

  • Header not visible in alv output print preview using html_top_of_page

    hi to all experts,
    im using html_top_of_page for alv header and using fm reuse_alv_grid_display. when i see the print preview im getting the report output but not the alv header . what could be the problem

    Hi tarun,
    im unable to see the header print preview . I can see it in the report output .
    here is my code
    FORM html_top_of_page USING document
            TYPE REF TO cl_dd_document .
      CREATE OBJECT:  document.
      DATA:text TYPE sdydo_text_element.
      DATA: l_repid TYPE sy-repid,
            l_mandt TYPE sy-mandt,
            l_date(10),
            l_yr(4),
            l_mm(2),
            l_dd(2),
            l_hr(2),
            l_sec(2),
            l_min(2),
            l_time(10).
      CALL METHOD document->add_gap
        EXPORTING
          width = 70.
      text = text-005.
      CALL METHOD document->add_text
        EXPORTING
          text      = text-005
          sap_style = 'HEADING'.
      CALL METHOD document->new_line.
      CONCATENATE 'Report:' sy-repid INTO text.
      CALL METHOD document->add_text
        EXPORTING
          text         = text
          sap_emphasis = 'Strong'.
      CALL METHOD document->add_gap
        EXPORTING
          width = 206.
      l_date = sy-datum.
      MOVE: l_date+0(4) TO l_yr,
            l_date+4(2) TO l_mm,
            l_date+6(2) TO l_dd.
      CONCATENATE 'Run Date:' l_dd '.' l_mm '.' l_yr
                  INTO text.
      CALL METHOD document->add_text
        EXPORTING
          text          =  text
          sap_style     =  space
          sap_color     =  space
          sap_fontsize  =  cl_dd_document=>medium
          sap_emphasis  =  cl_dd_document=>strong
          style_class   =  space
    *  CHANGING
    *    document      =
      CALL METHOD document->new_line.
      CONCATENATE 'Client:' sy-mandt INTO text.
      CALL METHOD document->add_text
        EXPORTING
          text          = text
          sap_fontstyle = cl_dd_document=>medium
          sap_emphasis  = cl_dd_document=>strong.
      CALL METHOD document->add_gap
        EXPORTING
          width = 220.
      l_time = sy-uzeit.
      l_hr = l_time+0(2).
      l_mm = l_time+2(4) .
      l_sec = l_time+4(6).
      CONCATENATE l_hr ':' l_mm ':' l_sec
           INTO l_time.
      CONCATENATE 'Time:' l_time INTO text.
      CALL METHOD document->add_text
        EXPORTING
          text           = text
          sap_fontstyle =  cl_dd_document=>medium
          sap_emphasis  =  cl_dd_document=>strong
          style_class   =  space
    *  CHANGING
    *    document      =
      CALL METHOD document->new_line.
      CONCATENATE 'User Id:' sy-uname INTO text.
      CALL METHOD document->add_text
        EXPORTING
           text          =  text
          sap_style     = space
          sap_color     = space
          sap_fontstyle = cl_dd_document=>medium
          sap_emphasis  = cl_dd_document=>strong
          style_class   = space
    *  CHANGING
    *    document      =
      CALL METHOD document->new_line.
      CALL METHOD document->new_line.
      text = 'Note: The maximum value for the column Qty to Print is 10,000.'.
      CALL METHOD document->add_text
        EXPORTING
           text          = text
    *    text_table    =
    *    fix_lines     =
    *     sap_style     =  cl_dd_document=>strong
           sap_color     = cl_dd_document=>list_negative
    *    sap_fontsize  =
          sap_fontstyle = cl_dd_document=>strong
    *    sap_emphasis  =
    *    style_class   =
    *  CHANGING
    *    document      =
      CALL METHOD document->new_line.
      CALL METHOD document->new_line.
      text = 'Selection Criteria:'.
      CALL METHOD document->add_text
        EXPORTING
           text          = text
    *      text_table    =
    *      fix_lines     =
           sap_style      = 'KEY'
    *      sap_color     =
           sap_fontsize  = cl_dd_document=>medium
           sap_fontstyle = cl_dd_document=>strong.
    *  CALL METHOD document->new_line.
    *  CALL METHOD document->new_line.
      IF so_mblnr[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_mblnr-high IS NOT INITIAL.
          CONCATENATE 'Material Doc:' so_mblnr-low '  TO   '  so_mblnr-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Material Doc:' so_mblnr-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_bwart[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_bwart-high IS NOT INITIAL.
          CONCATENATE 'Movement Type:' so_bwart-low ' TO  ' so_bwart-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Movement Type:' so_bwart-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_bldat[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_bldat-high IS NOT INITIAL.
          CONCATENATE 'Document Date:' so_bldat-low ' TO  ' so_bldat-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Document Date:' so_bldat-low  INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_budat[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF  so_budat-high IS NOT INITIAL.
          CONCATENATE 'Posting Date:' so_budat-low ' TO  ' so_budat-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Posting Date:' so_budat-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_matnr[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_matnr-high IS NOT INITIAL.
          CONCATENATE 'Material ID:' so_matnr-low ' TO  ' so_matnr-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Material ID:' so_matnr-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_werks[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_werks-high IS NOT INITIAL.
          CONCATENATE 'Plant:' so_werks-low ' TO  ' so_werks-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Plant:' so_werks-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_lgort[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_lgort-high IS NOT INITIAL.
          CONCATENATE 'Storage Location:' so_lgort-low ' TO  ' so_lgort-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Storage Location:' so_lgort-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_lifnr[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_lifnr-high IS NOT INITIAL.
          CONCATENATE 'Vendor:' so_lifnr-low ' TO  ' so_lifnr-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Vendor:' so_lifnr-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_xblnr[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_xblnr-high IS NOT INITIAL.
          CONCATENATE 'Delivery Note:' so_xblnr-low 'TO' so_xblnr-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'Delivery Note:' so_xblnr-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_ebeln[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_ebeln-high IS NOT INITIAL.
          CONCATENATE 'PO NO:' so_ebeln-low ' TO  ' so_ebeln-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'PO NO:' so_ebeln-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      IF so_usnam[] IS NOT INITIAL.
        CALL METHOD document->new_line.
        IF so_usnam-high IS NOT INITIAL.
          CONCATENATE 'User Name:' so_usnam-low ' TO  ' so_usnam-high INTO text SEPARATED BY space.
        ELSE.
          CONCATENATE 'User Name:' so_usnam-low INTO text SEPARATED BY space.
        ENDIF.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      CALL METHOD document->new_line.
      IF 1x3 = 'X'.
        text = 'Barcode label 1x3 maintained'.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ELSE.
        text = 'Bar Code label 2x4 maintained'.
        CALL METHOD document->add_text
          EXPORTING
            text          = text
            sap_fontsize  = cl_dd_document=>medium
            sap_fontstyle = cl_dd_document=>strong.
      ENDIF.
      CALL METHOD document->new_line.

  • Regarding Smart Form Printing, Print Preview issues

    Hi,
    I have couple of issues regarding Smart Form Printing, Print Preview.
    In my program i am passing below parameters to smart form function module:
    t_control-device = c_printer.
    t_control-no_dialog = space.
    t_control-preview = space.
    t_control-no_dialog = c_x.
    t_output-tddest = g_spld.
    t_output-tdimmed = c_x. " Print Immediately
    t_output-tddelete = space. " Don't Release spool after output
    g_user_settings = c_x.
    Issue#1: Though i have set preview paramter to space, after executing program it is prompting for Preview Screen, There again i have to give printer name though i am passing printer name as above and i need to hit on print preview button to set Layout output.
    Here how can i go directly to layout output without preview screen.
    Issue#2: In some cases we need to Print the layout set output after executing program immediately without prompting for preview screen and then Layout set output should also be shown after printing the output.
    How can i solve these issues!
    Thanks in advance.
    Thanks,
    Deep.

    Hi,
    In the SAP menu screen goto <b>System->User Profile->Own data</b>
    There in the defaults tab, for the output device give the value you had maintained for <b>g_spld.</b> This will not prompt you a dialog screen, and if you want to print immediately select the checkbox as well. Then try to execute the smartform. Hope this solves ur issue.
    Tushar

  • Print preview issue for amendment purchase order

    Hi
    Whenever i have created po in me21n t.code for two materials that time my outputype neu coming automaticaly and po print out also come for two materials in me9f .
    Supoose i have change quantity in me22n t.code for first line item for same po that time also neu coming automatically.but in   me9f coming printout first line item only,after that  po quantity changed available text in print preview,second line item material not comes,i need second line material also in print preview,plz help.
    Following configurations are completed for my output type(NEU) automatic generation in ME21N t.code and ME22N t.code
    in nace t.code EF purchase order for my condition records NEU for my document type nb and my vendor vn and message transsmission medium 5, dispatch time 3,language En,and my communication output device HP and save it
    SPRO-IMG-MM-PURCHASING-MESSAGES-MESSAGE TYPES-DEFINE MESSAGE TYPES FOR PURCHASE ORDER-FINED TUNED CONTROL PURCHASE ORDER-operation 1 for neu automatic generation in me21n, then operation  2 for neu automatic generation  in me22n.
    Regards
    Sam
    Edited by: sadaraji on Apr 15, 2011 3:50 PM
    Edited by: sadaraji on Apr 15, 2011 3:53 PM

    Hi,
      One thing you can do is, create a GUI Status resembleing the current GUI status, except the Print Prieview Button.Ans set the GUI Status before calling the Transaction in BADI or User Exit.
    Thanks & Regards,
    Vamsi.

  • Goods issue print preview issue

    Hi
    I have created stock transport order,goods issue in mb11 tcode 351 movement type,in mb90 tcode print preview shown only transferred from site details only,transferred to details of plant not shown,plz help
    Regards
    sam

    Hi,
    Contact ur abaper to change smart form.
    Arun

  • Print preview issue

    Hi ,
    while clicking print preview , the system is showing below said message
    ( proper output type is assigned )
    No print-relevant changes to document 2200000149 exist
    Message no. ME140
    what setting is required in PO

    Hi,
    Chcek the setting for your OUTPUT TYPE in NACE t.code for appplication EF. Also check program , form & routine for OUTPUT TYPE .Also check the despatch time setting for the put type.
    Also check the  transmission medium  in condition record for your output type MN04/MN05 . 
    Regards,
    Biju K

  • Print preview issue with invoice script

    Hi folks
    i am working on preparing UTP for a invoice script(modification of standard one).
    here when i am running the billing document number in VF02 i am not able to see the print preview.
    i would like to know what should i do on this as i need a printpreview to prepare  UTP on this layout.
    when i select the message type(output type) of that layout and press the option print preview nothing is happening.
    when i say print in the status bar it is giving success message and when i saw in the spool the status is in waiting.
    can anyone let me know what i need to do ?
    thanks in advance

    Hi
    Do u know the o/p type  of the script ?
    if not ist see the out put type by going to Tcode NACE
    after thatjust go through the steps...
    1 vf02 > give a doc no-> enter
    2
    from menue bar chose GOTO> Header> output
    3.
    now give the output type . medium -> printout press enter
    4
    save and go bck to 1st screen of vf02
    from menue bar chose billing document--> issueoutput type
    chose select the printout and select print preview.
    rewards if useful
    Regards
    Sachhi

  • Print Preview issue related to Purchase Order

    HI,
    I am working on purchase order printout. For the creation of P.O. I have worked on printout ad its working fine. As comes to change purchase order, client is using same output type and if they take the printout its coming as
    Amendment to P.O. (In case creation of new purchase order printout Its coming as Purchase order only.) And in the change purchase order printout, its showing the items changed(But in print preview i am able to see the the new created purchase order only....not the changed purchase order print preview)..
    How can I see the change purchase order print preview?..so that I can make the changes as per the client requirement.
    Thanks,
    Kishore

    Kalyan,
    This is possible provided you have mantained Individual Capacity Defination in the Capacity header of the work center. Since yours is Labour you need to assign the person to the Individual capacity details for Machine you can define your own naming. With this you should be able to confirm every product with referance to the Individual Machine.
    Since you are using Serial Numbers, I assume that GR you are doing using transaction MB31 or MIGO, where you can assign the Serial Number to the material.
    Regards,
    Prasobh

  • RFQ Output print preview

    Hi friends,
    I want to see the print preview of my RFQ. But I am unable to see the print preview in ME41/ME42/ME43. In my PO i can see the print preview, but for RFQ its not showing at all.
    Please suggest.
    Thanks & Regards
    Satya

    Hi.
    Which component are you using purchase order?
    I guess ME21N.
    Preview function should be added in Enjoy transaction like ME21N, ME22N etc.
    So when you try to create ME21, you won't find the way to preview the output.
    You can reffer to Note 457497(18).
    18. In the EnjoySAP Transaction ME21N, ME22N or ME23N you go into in the
        print preview for a purchase order.It can happen that the system
        displays too much or too little data.However, the print output of
        the document is correct.
    It's not the comment about "Enjoy can use the preview" but we can guess from the
    text.
    Instead of that, you can see the Nast data from ME9A(for RFQ and for PO ME9F)
    and you can use the preview function.
    I'm not sure if this help you, but it should be restriction of old transaction.
    Just only information, the coding of ME21N to call preview function.
    *LMEGUICJL
    preview output
          WHEN 'PREVOUTPUT'.
            CALL METHOD l_appl->preview.
            CLEAR im_fcode.

  • MIGO output Print Preview

    Hi,
    I have made settings for output determination.
    Now while creating MIGO , one output TAB is coming .
    But while entering into that TAB ,I cant find any option for print preview.
    Is in standard SAP , print preview is not possible?
    How to make settings for connecting this output to my network printer.?
    Kindly advise.
    regards,

    In MIGO , the messge is generated when we save/post the document . Hence preview of teh document is not possible. Only after post u will come to know wr message is generated or not.
    In case you are testing the message set up, I suggest to use MB01 for goods receipt .
    Hope this answers your query. Please reward points if u are satisfied with or post your query back.....
    Regards
    Mani

  • Output Type - Print Preview issue

    Dear Friends,
    I have an Output Type which when seen in the output preview / printing of billing doc shows the PO No. along with the other data.
    The Output Type picks up the Sales Order no. from the table VBFA based on the billing doc no. and collects the preceding doc no. This preceding doc i.e. the Sales Order doc no. is then passed in the VBKD table along with the line item no. of the billing doc. and then the PO No. maintained at the item level is picked up from the field BSTKD by matching it with the line item no. of the Sales Order Doc No.
    Now, I am facing a problem where when the PO No at the header level and the PO No of all the Item levels are same at the Sales Order doc, the output preview does not display the PO No. in the Output preview / print. This happens with only those sales order doc where the header level PO No. and Item level PO No. are the same. For rest other docs, things are running smooth.
    Kindly suggest me with some solution.
    Regards
    Vineet Jain

    When business data is the same on header and items, VBKD does not contain any lines for the items - it only contains a single line for the header where the item number is initial.  This fails your logic of looking up VBKD by line numbers.
    Edited by: Keerthi Hiremath on May 29, 2008 9:00 AM

  • Print program for delivery output printing

    Hi,
    I need help with creating a custom smart form and print program for outbound delivery.
    1. i want to know how to select data in my print program ? i mean how to i get the delivery number when the output type is executed.
    2. What parameters are to be passed so that delivery opens as soon as the output type is processed.
    Thank you.
    Usha

    Details of output triggered can be obtained from nast. By default structure nast is populated with the values when the print program is being processed. Field OBJKY is used for the delivery number; Application : V2
    It could be enough to pass an internal table with item level details and an header structure. This more or less is dependent on the output desired.
    Rgds,
    Karthik

  • PO Print preview is not appearing properly for the Bulgarian

    Hello Experts,
    We are facing an issue on PO output print preview and print.
    Where we are expecting the PO output was supposed to print Bulgarian
    language.
    Bulgarian letters are not appearing properly in PO print preview smart
    form
    We are able to see the Bulgarian letters in the GUI, when output gets
    processed in PO Spool output. And we are not able to see it in the
    portal .Its appearing as some junk characters
    Could you please provide me any pointers to resolve the issue?
    Looking forward your help.
    Thank you,
    Bharathi.

    Hi Ganesh,
    Thanks for your reply
    Can anybody tell me, is this is because of the PDF issue or output device issue?
    If the data is maintained in Bulgarian language, that we can see in portal.
    Where when we click on the PO Pint output preview, itu2019s not appearing as some junk characters only
    thank you
    bharathi

  • Firefox print preview

    This is not a question, it is more of a statement of a Print Preview issue in Firefox 4.01 and 3.6.
    When using min-height styling on a webpage, if an element (any element) extends beyond one page while using print-preview, then the element stretches AGAIN to that min-height on the second page.. In other words, min-height is re-applied, even though the element may already be that greater than that min-height.

    Haha, Mr. Smarty Pants, that is pretty much exactly what we ended up doing :) Very quick answer, though, nice stuff. It took us about a half hour so of testing to find out what was causing this issue though... we couldn't figure out why the table was extending so far until I did a print screenshot and measured it in Paint and was able to connect the dots.
    (edit)
    Preferably, rather than doing special, kooky css that i hope looks right, maybe Firefox can fix this.. I probably should have pushed this somewhere else.. it was just difficult for me to find the bug submit area.

Maybe you are looking for

  • Error in installing ERP 2005

    Hi All, While installing SAP ERP 2005 we are getting an error CJS-30022  'Program migration monitor' exists with error code 103. Import.monitor.log TRACE: 2008-02-19 17:37:27 com.sap.inst.migmon.LoadTask run Loading of 'SAPNTAB' import package is sta

  • G5 leopard doesn't recognize airport network

    airport utility, network diagnostics, and other ways to try to get my G5 to recognize my network don't work. my MAcBook pro is setting on the same desk and has no trouble. thanks in advance for any help.

  • RT: 9512 modules fault when using hybrid mode

    Hello, I am having an issue with my cRIO hyrbid setup. I am currently using Labview 2010, cRIO 9074, x1 NI 9234, and x3 NI 9512. Summary: What you are trying to accomplish? -I have built two VIs. One that acquired data from an NI 9234. This vi is the

  • Ordering Photo Books in Australia with iPhoto 5

    We've just spend ages building a photo book using iPhoto 5.0.4 in Australia. We couldn't actually place the order though. After a call to Apple support in Australia, we have discovered that you can only order a photo book from iPhoto in Australia usi

  • Should I upgrade from OS X Lion (10.7.5) to Mavericks or Yosemite

    I think I need to upgrade OS X (am starting to hit sites that tell me my version of Safari is not supported and indications are that I need to upgrade OS X)!  I know Yosemite is the latest version, but the reviews in the App Store aren't encouraging