Output type - Print preview Commodity code

Hi All,
I have created an F8 billing document and I can see the commodity code in the foreign trade tab.
Is there standard output type which I can use to view the invoice and see if the commodity code is getting printed?
Any ideas?
Regards,
Meghna

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

Similar Messages

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

Help reqd to display the form output without print preview

Hi all,
I did one gate pass form and i want to view the form in my selection screen or output screen(just in monitor) as a display by giving one t-code.
i.e, we can view the form thru Print preview...the same preview, i want to display after i give my parameter in the selection screen.
For example.ZGPOUT if i enter as a t-code.
it should ask my Gate Pass number in the Selection screen...if its right then my Form will come out to the display screen. (instead of going by Print method).,
Pls post ur comment and reply me with examples,if possible.
thanks & regards
sankar.

Hi Sankar,
Simply put a parameter statement .
for example.
parameters : vbeln type vbrk-vbeln .
when u ll execute.U ll get the selection screen asking u for the perticular parameter,U input that and execute.U ll get the output as print preview.In the above query i ll input vbeln and ll get the o/p.Similarly u enter Ur getpass no and u ll get the printpreiview as o/p.
Reward if useful.
Regards
Rudra

Output types assignment with transaction codes(MIGO)

We have different output types in system for output determination in inventory management.
eg: WE01,WA01 etc
Now while GR(101) how system will determine which output type it should use.
Suppose I am doing MIGO, then how system determining it should pick WE01 output type?
Is there any configuration setting telling the assignments of different output types to different transaction codes?
Please advice.
Thanks

It is based on the 7th Step in the below steps
Check following are some of steps for GR collective printing from SDN only
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
2. Ensure that in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for GI/Transfer Posting Documents
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, maintain the Output device for all your Plants
7. Go to MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.
Now the settings are ready for Printing Material doc
8. While doing MIGO, ensure that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
9. Now depending on the setting in 5a, the Matl doc is printed. If it is 3, you have to print it using MB90. If it is 4, it is printed immediately.

Output type print

Dear All
I select particular output type DC print . In that particular output type printing slowly 1 hr what is the reason
Thanks and Regards
Suresh

hi,
in the messages->further data under dispatch time give it as send immediately.
\[removed by moderator\]
siri
Edited by: Jan Stallkamp on Jul 24, 2008 12:43 PM

Output type for the managed codes cut letter is hard coded

Hello,
Very Good afternoon!
I have a requirement to create new Output Types for a Smart Form.
The already existing Output types are hard coded as shown Below :
CONSTANTS : c_kschl_order LIKE nast-kschl
                         VALUE 'ZUS0',
            c_kschl_order1 LIKE nast-kschl
                         VALUE 'ZUS1',
Now they do not want to use ZUS1. Insted they wnat to use New Output Types.
u2022 Remove ZUS1 as we no longer use this one.
u2022     Add ZAU0
u2022     Add ZNZ0
u2022     Add ZJP0
u2022     Add ZCN0
u2022     Add ZKR0
How to add these Output types without Hardcoding as shown ABove.
Any Suggestions will be appreciated.....
For reference..I will paste the code of the Program here.
Here is the code :
                 PROGRAM DECLARATION
PROGRAM ID           Z_RVADOR01_SALES_CUT_LETTER
TABLES: vbak,    "Sales Document: Header Data
       vbap,    "Sales Document: Item Data
       vbpa,    "Sales Document: Partner
       vbep,    "Sales Document: Schedule Line Data
       kna1,    "General Data in Customer Master
       MARA,    "Material Master
        KOMK,                          "Communicationarea for conditions
        KOMP,                          "Communicationarea for conditions
        KOMVD,                         "Communicationarea for conditions
        VBCO3,                         "Communicationarea for view
        VBDKA,                         "Headerview
        VBDPA,                         "Itemview
        VBDPAU,                        "Subitemnumbers
        CONF_OUT,                      "Configuration data
        SADR,                          "Addresses
        TVAG,                          "Reason for rejection
        VEDKA,                         "Servicecontract head data
        VEDPA,                         "Servicecontract position data
        VEDKN,                         "Servicecontract head notice data
        VEDPN,                         "Servicecontract pos. notice data
        RISERLS,                       "Serialnumbers
        KOMSER,                        "Serialnumbers for print
        TVBUR,                         "Sales office
        TVKO,                          "Sales organisation
        ADRS,                          "Communicationarea for Address
        FPLTDR,                        "billing schedules
        WTAD_ADDIS_IN_SO_PRINT,        "additional
        WTAD_BUYING_PRINT_EXTRA_TEXT, "texts belonging to additional
        adrc,
        adr6,
        t247.
INCLUDE RVADTABL.
INCLUDE RVDIREKT.
INCLUDE VEDADATA.
data for access to central address maintenance
INCLUDE SDZAVDAT.
TYPE-POOLS: ADDI.
DATA PRICE_PRINT_MODE(1) TYPE C.       "Print-mode
DATA: RETCODE   LIKE SY-SUBRC.         "Returncode
DATA: REPEAT(1) TYPE C.
DATA: XSCREEN(1) TYPE C.               "Output on printer or screen
DATA: BEGIN OF STEU,                   "Controldata for output
        VDKEX(1) TYPE C,
        VDPEX(1) TYPE C,
        KBKEX(1) TYPE C,
        KBPEX(1) TYPE C,
      END OF STEU.
DATA: BEGIN OF TVBDPA OCCURS 0.        "Internal table for items
        INCLUDE STRUCTURE VBDPA.
DATA: END OF TVBDPA.
DATA: BEGIN OF TKOMV OCCURS 50.
        INCLUDE STRUCTURE KOMV.
DATA: END OF TKOMV.
DATA: BEGIN OF TKOMVD OCCURS 50.
        INCLUDE STRUCTURE KOMVD.
DATA: END OF TKOMVD.
DATA: BEGIN OF TVBDPAU OCCURS 5.
        INCLUDE STRUCTURE VBDPAU.
DATA: END   OF TVBDPAU.
DATA: BEGIN OF TKOMCON OCCURS 50.
        INCLUDE STRUCTURE CONF_OUT.
DATA: END   OF TKOMCON.
DATA: BEGIN OF TKOMSERVH OCCURS 1.
        INCLUDE STRUCTURE VEDKA.
DATA: END   OF TKOMSERVH.
DATA: BEGIN OF TKOMSERVP OCCURS 5.
        INCLUDE STRUCTURE VEDPA.
DATA: END   OF TKOMSERVP.
DATA: BEGIN OF TKOMSERVHN OCCURS 5.
        INCLUDE STRUCTURE VEDKN.
DATA: END   OF TKOMSERVHN.
DATA: BEGIN OF TKOMSERVPN OCCURS 5.
        INCLUDE STRUCTURE VEDPN.
DATA: END   OF TKOMSERVPN.
DATA: BEGIN OF TKOMSER OCCURS 5.
        INCLUDE STRUCTURE RISERLS.
DATA: END   OF TKOMSER.
DATA: BEGIN OF TKOMSER_PRINT OCCURS 5.
        INCLUDE STRUCTURE KOMSER.
DATA: END   OF TKOMSER_PRINT.
DATA: BEGIN OF TFPLTDR OCCURS 5.
        INCLUDE STRUCTURE FPLTDR.
DATA: END   OF TFPLTDR.
DATA: TADDI_PRINT TYPE ADDI_SO_PRINT_ITAB WITH HEADER LINE.
TYPES:BEGIN OF ty_orders ,
     xblnr    LIKE mkpf-xblnr,       "delivery number
     erfmg    LIKE mseg-erfmg,       "goods issue quantity
     custname LIKE kna1-name1,       "customer name
     bstnk    LIKE vbak-bstnk,       "purchase order number
     ean11    LIKE vbap-ean11,       "upc
     kdmat    LIKE vbap-kdmat,       "customer material code
     arktx    LIKE vbap-arktx,       "description
     csrno    LIKE kna1-kunnr,       "customer service rep number
     spras    LIKE kna1-spras,       "customer language key
     csrname LIKE kna1-name1,       "customer service rep name
     csremail LIKE adr6-smtp_addr,   "csr email
     csrphone LIKE kna1-telf1,       "csr telephone
     csrext   LIKE adrc-tel_extens, "csr extension
     csrfax   LIKE kna1-telfx,       "csr fax
     total    LIKE lips-lfimg,       "cut quantity
     ldate(18)    TYPE c,
   END OF ty_orders.
CONSTANTS: c_kschl_order LIKE nast-kschl
                         VALUE 'ZUS0',
            c_kschl_order1 LIKE nast-kschl
                         VALUE 'ZUS1',            c_parvw_shipto LIKE vbpa-parvw
                         VALUE 'WE',
            c_parvw_csr    LIKE vbpa-parvw
                         VALUE 'ZS',
             c_eng(1)       TYPE c VALUE 'E',
             c_sep(1)       TYPE c VALUE '/',
             c_sale(25) type c VALUE 'Sales Order'.
DATA: WA_VBAK TYPE VBAK,
      tbl_ord TYPE ty_orders OCCURS 0 WITH HEADER LINE,
      w_csrname(30) TYPE c,
     w_csrno(30)    TYPE c,
     w_email    LIKE adr6-smtp_addr,
     f_shipto_found     TYPE c,
     w_custname(30) TYPE c,
     w_month(2),
     w_ldate(18),
     w_total LIKE lips-lfimg,
     w_lines        TYPE i VALUE 0,
     f_mail(1) TYPE c,
     cnt_1          TYPE i VALUE 0,
     cnt_2          TYPE i VALUE 0,
     tbl_otf     LIKE itcoo OCCURS 0 WITH HEADER LINE,
     w_type(25)     TYPE c,
     st_doc_data   LIKE sodocchgi1,
     tbl_objtxt    LIKE solisti1 OCCURS 10 WITH HEADER LINE,
     tbl_line      LIKE tline OCCURS 0 WITH HEADER LINE,
     tbl_attach    LIKE solisti1 OCCURS 10 WITH HEADER LINE,
     tbl_objhead   LIKE solisti1 OCCURS 10 WITH HEADER LINE,
     tbl_proc_para LIKE soparai1 OCCURS 10 WITH HEADER LINE,
     tbl_maillist LIKE somlreci1 OCCURS 10 WITH HEADER LINE,
     tbl_pack_list LIKE sopcklsti1 OCCURS 10 WITH HEADER LINE,
     tbl_cpo      LIKE itcpo OCCURS 0 WITH HEADER LINE,"SAPscript output
                                                            " interface
     tbl_cpp LIKE itcpp OCCURS 0 WITH HEADER LINE,"SAPscript output
                                                   " parameters
     tbl_smtp TYPE szadr_adsmtp_line OCCURS 0 WITH HEADER LINE,
     tbl_cdhdpos LIKE cdshw OCCURS 0 WITH HEADER LINE,
     tbl_cdpos LIKE cdshw OCCURS 0 WITH HEADER LINE,
     wrk_lines LIKE sy-tabix,
     hltlines   TYPE i,
     off1       TYPE p,
     fle1(2)    TYPE p,
     fle2(2)    TYPE p,
     htabix     LIKE sy-tabix,
     hfeld(500) TYPE c.
FORM ENTRY USING RETURN_CODE US_SCREEN.
if sy-tcode = 'VA01'.
IF nast-kschl = c_kschl_order.
SELECT SINGLE * FROM VBAK INTO WA_VBAK WHERE vbeln = nast-objky.
IF SY-SUBRC = 0.
CLEAR RETCODE.
XSCREEN = US_SCREEN.
PERFORM PROCESSING USING us_screen.
IF RETCODE NE 0.
    RETURN_CODE = 1.
ELSE.
    RETURN_CODE = 0.
ENDIF.
   ELSE.
      retcode = sy-subrc.
      syst-msgid = 'ZVERROR'.
      syst-msgno = '000'.
      syst-msgty = 'E'.
      syst-msgv1 = NAST-KSCHL.
     syst-msgv1 = 'Sales Order cut letter
                   for this order already issued'.
     syst-msgv2 = ' '.
      PERFORM protocol_update.
    ENDIF.
ELSE.
    CLEAR retcode.
    xscreen = us_screen.
    PERFORM processing USING us_screen.
    IF retcode NE 0.
      return_code = 1.
    ELSE.
      return_code = 0.
    ENDIF.
ENDIF.
endif.
ENDFORM.
      FORM PROCESSING                                               *
FORM PROCESSING USING proc_screen.
CASE nast-kschl.
    WHEN c_kschl_order.
      PERFORM get_orders.
      CHECK retcode = 0.
      PERFORM openform USING proc_screen vbak-landtx.
      CHECK retcode = 0.
      PERFORM layout.
      CHECK retcode = 0.
      CHECK proc_screen NE 'X'.
      w_type = c_sale.
      PERFORM send_email USING proc_screen.
WHEN c_kschl_order1.
     PERFORM get_orders.
     CHECK retcode = 0.
     CHECK proc_screen NE 'X'.
     w_type = c_sale.
     PERFORM send_email USING proc_screen.
   WHEN OTHERS.
      retcode = 1.
      syst-msgid = 'E0'.
      syst-msgno = '430'.
      syst-msgty = 'E'.
      PERFORM protocol_update.
ENDCASE.
IF retcode EQ 0.
    syst-msgid = '69'.
    syst-msgno = '254'.
    syst-msgty = 'S'.
    syst-msgv1 = nast-kschl.
    PERFORM protocol_update.
ELSE.
    syst-msgid = 'CKCC'.
    syst-msgno = '036'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.
      FORM PROTOCOL_UPDATE                                          *
      The messages are collected for the processing protocol.       *
FORM PROTOCOL_UPDATE.
IF xscreen EQ space.
    CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
       EXPORTING
            MSG_ARBGB = SYST-MSGID
            MSG_NR    = SYST-MSGNO
            MSG_TY    = SYST-MSGTY
            MSG_V1    = SYST-MSGV1
            MSG_V2    = SYST-MSGV2
            MSG_V3    = SYST-MSGV3
            MSG_V4    = SYST-MSGV4
       EXCEPTIONS
            OTHERS    = 1.
   ELSE.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   ENDIF.
ENDFORM.
*&      Form get_orders
      text
--> p1        text
<-- p2        text
FORM get_orders.
DATA : f_csr_found        TYPE c.
SELECT SINGLE vbeln vkorg vdatu bstnk kunnr
    FROM   vbak
    INTO (vbak-vbeln,vbak-vkorg,vbak-vdatu,vbak-bstnk,vbak-kunnr)
    WHERE vbeln EQ nast-objky.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'VN'.
    syst-msgno = '203'.
    syst-msgty = 'E'.
    syst-msgv1 = 'VBAK'.
    syst-msgv2 = sy-subrc.
    PERFORM protocol_update.
ENDIF.
SELECT vbeln posnr matnr pmatn arktx abgru kdmat werks
FROM vbap
INTO (vbap-vbeln,vbap-posnr,vbap-matnr,vbap-pmatn,
vbap-arktx,vbap-abgru,vbap-kdmat,vbap-werks)
WHERE vbeln = vbak-vbeln
AND abgru NE space "select items havng Rejection Reason
and PSTYV NE 'ZHDR'.
to check whether the reason for rejection was picked from the
managed codes tables
data: war_abgru type abgru,
      w_exist type c.
clear : war_abgru, w_exist.
select single abgru from ZMAT_REJ002
                into war_abgru
                where vkorg = vbak-vkorg
                and kunnr <> vbak-kunnr
                and MATNR = vbap-matnr
                and datef <= vbak-vdatu
                and datet >= vbak-vdatu.
   if sy-subrc <> 0.
         select single abgru from ZMAT_REJ003
                          into war_abgru
                          where vkorg = vbak-vkorg
                          and kunnr <> vbak-kunnr
                          and MATNR = vbap-matnr
                          and datef <= vbak-vdatu
                          and datet >= vbak-vdatu.
         if sy-subrc <> 0.
                select single abgru from ZMAT_REJ001
                          into war_abgru
                          where vkorg = vbak-vkorg
                          and werks <> vbap-werks
                          and matnr = vbap-matnr
                          and datef <= vbak-vdatu
                          and datet >= vbak-vdatu.
                if sy-subrc <> 0.
                     select single abgru from ZMAT_REJ004
                                         into war_abgru
                                         where vkorg = vbak-vkorg
                                         and matnr = vbap-matnr
                                         and datef >= vbak-vdatu
                                         and datet <= vbak-vdatu.
                     if sy-subrc <> 0.
                     else.
                     w_exist = 'X'.
                     endif.
               else.
               w_exist = 'X'.
               endif.
         else.
         w_exist = 'X'.
         endif.
   else.
   w_exist = 'X'.
   endif.
if w_exist = 'X'.
end for check from managed codes table
*to find the quantity fields
    SELECT SINGLE wmeng bmeng
    FROM vbep
    INTO (vbep-wmeng,vbep-bmeng)
    WHERE vbeln EQ vbap-vbeln
    AND   posnr EQ vbap-posnr.
*to get info about the customer
    SELECT SINGLE kunnr
    FROM vbpa
    INTO vbpa-kunnr
    WHERE vbeln EQ vbak-vbeln
    AND    parvw EQ c_parvw_shipto.
     IF sy-subrc EQ 0.
      f_shipto_found = 'X'.
      SELECT SINGLE name1 spras
        FROM kna1
        INTO (kna1-name1,kna1-spras)
        WHERE kunnr EQ vbpa-kunnr.
      IF sy-subrc EQ 0.
        w_custname = kna1-name1.
        CLEAR kna1-name1.
      ENDIF.
     ENDIF.
     SELECT SINGLE kunnr
    FROM vbpa
    INTO vbpa-kunnr
    WHERE vbeln EQ vbak-vbeln
    AND   parvw EQ c_parvw_csr.
    IF SY-SUBRC EQ 0.
     f_csr_found = 'X'.
      SELECT SINGLE kunnr name1 name2 adrnr
       FROM kna1
       INTO (kna1-kunnr,kna1-name1,kna1-name2,
             kna1-adrnr)
       WHERE kunnr EQ vbpa-kunnr.
      IF sy-subrc EQ 0.
        w_csrno = kna1-kunnr.
        w_csrname = kna1-name1.
        CLEAR kna1-name1.
           SELECT SINGLE tel_number tel_extens fax_number
             FROM adrc
             INTO (adrc-tel_number,adrc-tel_extens,
   adrc-fax_number)
             WHERE addrnumber EQ kna1-adrnr.
        CLEAR: adr6, w_email.
        SELECT SINGLE * FROM adr6 WHERE addrnumber = kna1-adrnr.
        IF sy-subrc = 0.
          w_email = adr6-smtp_addr.
        ENDIF.
      ENDIF.
    ENDIF.
*to get the date format in french
    IF kna1-spras NE c_eng.
      w_month = sy-datum+4(2).
      SELECT SINGLE ltx
        FROM t247
        INTO t247-ltx
        WHERE spras EQ kna1-spras
        AND mnr EQ w_month.
      CONCATENATE sy-datum+6(2)
                  t247-ltx
                  sy-datum+0(4)
                  INTO w_ldate
                  SEPARATED BY space.
      ELSE.
      CONCATENATE sy-datum+4(2)
                  sy-datum+6(2)
                  sy-datum+0(4)
                  INTO w_ldate
                  SEPARATED BY c_sep.
    ENDIF.
    w_total = vbep-wmeng - vbep-bmeng.
     IF w_total GT 0.
     PERFORM fill_orders.
    ELSE.
      IF vbap-abgru NE space.
        w_total = vbep-wmeng.
        PERFORM fill_orders.
      ENDIF.
    ENDIF.
    CLEAR vbap.
    endif.           " check for w_exist for Managed Codes entry
ENDSELECT.
IF tbl_ord[] IS INITIAL.
    retcode = 1.
    syst-msgid = 'FZ'.
    syst-msgno = '027'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
IF f_csr_found IS INITIAL.
    syst-msgid = '8B'.
    syst-msgno = '127'.
    syst-msgty = 'W'.
    syst-msgv1 = c_parvw_csr.
    PERFORM protocol_update.
ENDIF.
IF f_shipto_found IS INITIAL.
    syst-msgid = '8B'.
    syst-msgno = '127'.
    syst-msgty = 'W'.
    syst-msgv1 = c_parvw_shipto.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " get_orders
*&      Form layout
      text
--> p1        text
<-- p2        text
FORM layout.
SORT tbl_ord BY bstnk kdmat.
LOOP AT tbl_ord.
    AT FIRST.
      PERFORM writeform_text.
    ENDAT.
    PERFORM writeform.
    AT LAST.
      PERFORM writeform_footer.
    ENDAT.
ENDLOOP.
CLEAR : cnt_1,cnt_2.
PERFORM closeform.
ENDFORM.                    " layout
*&      Form openform
      text
FORM openform USING us_screen us_country.
DESCRIBE TABLE tbl_ord LINES w_lines.
IF w_lines EQ 0.
    retcode    = '1'.
    syst-msgid = 'FE'.
    syst-msgno = '078'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
CHECK retcode EQ 0.
INCLUDE zrvadopfo.
ENDFORM.                    " openform
*&      Form send_email
      text
     -->P_PROC_SCREEN text
FORM send_email USING    PROC_SCREEN.
f_mail = 'X'.
PERFORM openform USING proc_screen vbak-landtx.
LOOP AT tbl_ord.
    AT FIRST.
      PERFORM writeform_text.
    ENDAT.
    PERFORM writeform.
    AT LAST.
      PERFORM writeform_footer.
    ENDAT.
ENDLOOP.
CLEAR cnt_2.
PERFORM closeform.
CALL FUNCTION 'CONVERT_OTF'
       EXPORTING
            format                = 'PDF' "'ASCII'
       IMPORTING
            bin_filesize          = st_doc_data-doc_size
       TABLES
            otf                   = tbl_otf
            lines                 = tbl_line
       EXCEPTIONS                                           "DEVK912166
            err_max_linewidth     = 1
            err_format            = 2
            err_conv_not_possible = 3
            OTHERS                = 4.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'OA'.                                      "DEVK912166
    syst-msgno = '186'.                                     "DEVK912166
    syst-msgty = 'E'.                                       "DEVK912166
    PERFORM protocol_update.
ENDIF.
REFRESH tbl_objtxt.
CLEAR tbl_objtxt.
CLEAR tbl_proc_para.
REFRESH tbl_proc_para.
CLEAR tbl_maillist.
REFRESH tbl_maillist.
CLEAR tbl_pack_list.
REFRESH tbl_pack_list.
st_doc_data-obj_name   = 'Sales Order Cut Letter'.
st_doc_data-obj_langu   = 'E'.                            "DEVK905849
st_doc_data-sensitivty = 'F'.                            "DEVK905849
st_doc_data-obj_prio    = 1.                             "DEVK905849
CONCATENATE w_type 'Cut Letter' INTO          "#EC NOTEXT
                              st_doc_data-obj_descr SEPARATED BY space.
DATA w_line(3) TYPE c.
PERFORM format_pdf.                                       "DEVK905849
concatenate VBAK-VBELN '.PDF' into tbl_objhead.
tbl_objhead = 'Sales Order Cut Letter.PDF'.
APPEND tbl_objhead.
       "DEVK905849
CLEAR wrk_lines.
DESCRIBE TABLE tbl_attach LINES wrk_lines.
fields needed for email
tbl_maillist-com_type = 'INT'.
tbl_maillist-receiver = w_email.
tbl_maillist-rec_type = 'U'.
APPEND tbl_maillist.
send email
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                                  STARTING NEW TASK 'MAIL'
       EXPORTING
            document_data              = st_doc_data
            document_type              = 'PDF'
            COMMIT_WORK                = 'X'    " added after ECC6.0 upgrade
       TABLES
            object_header              = tbl_objhead
            object_content             = tbl_objtxt
            receivers                  = tbl_maillist
       EXCEPTIONS                                           "DEVK912166
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            OTHERS                     = 8
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'ZA_G'.                                    "DEVK912166
    syst-msgno = '922'.                                     "DEVK912166
    syst-msgty = 'E'.                                       "DEVK912166
    syst-msgv1 = sy-subrc.                                  "DEVK912166
    syst-msgv2 = tbl_smtp-adsmtp-smtp_addr.                 "DEVK912166
    PERFORM protocol_update.
    syst-msgid = 'VW'.
    syst-msgno = '001'.
    syst-msgty = 'E'.
    syst-msgv1 = 'Print successful:email Recepient Invalid'."#EC NOTEXT
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " send_email
*&      Form fill_orders
      text
--> p1        text
<-- p2        text
FORM fill_orders.
tbl_ord-bstnk    = vbak-bstnk.
tbl_ord-kdmat    = vbap-kdmat.
tbl_ord-xblnr    = vbak-vbeln.
tbl_ord-ean11    = vbap-pmatn.
tbl_ord-arktx    = vbap-arktx.
tbl_ord-csrno    = w_csrno .
tbl_ord-csremail = w_email.
tbl_ord-spras    = kna1-spras .
tbl_ord-csrphone = adrc-tel_number.
tbl_ord-csrfax   = adrc-fax_number.
tbl_ord-csrext   = adrc-tel_extens.
tbl_ord-total    = w_total.
tbl_ord-custname = w_custname.
tbl_ord-csrname = w_csrname .
tbl_ord-ldate    = w_ldate.
APPEND tbl_ord.
CLEAR tbl_ord.
CLEAR w_total.
CLEAR w_ldate.
ENDFORM.                    " fill_orders
*&      Form writeform_text
      text
--> p1        text
<-- p2        text
FORM writeform_text.
CALL FUNCTION 'WRITE_FORM'
       EXPORTING
            element = 'WTEXT'
            window = 'WINDOW2'
       EXCEPTIONS
            element = 1
            window = 2.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'EBR'.
    syst-msgno = '056'.
    syst-msgty = 'E'.
    syst-msgv1 = 'WTEXT'.
    syst-msgv2 = 'WINDOW2'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " writeform_text
*&      Form writeform
      text
--> p1        text
<-- p2        text
FORM writeform.
CALL FUNCTION 'WRITE_FORM'
       EXPORTING
            element = 'EMAIN'
            window = 'MAIN'
       EXCEPTIONS
            element = 1
            window = 2.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'EBR'.
    syst-msgno = '056'.
    syst-msgty = 'E'.
    syst-msgv1 = 'WTEXT'.
    syst-msgv2 = 'WINDOW2'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " writeform
*&      Form writeform_footer
      text
--> p1        text
<-- p2        text
FORM writeform_footer.
IF nast-spras = 'N'.
    CALL FUNCTION 'WRITE_FORM'
         EXPORTING
              element = 'FOOTER'
              window = 'MAIN'
         EXCEPTIONS
              element = 1
              window = 2.
ENDIF.
CALL FUNCTION 'WRITE_FORM'
       EXPORTING
            element = 'WFOOTER'
            window = 'WINDOW12'
       EXCEPTIONS
            element = 1
            window = 2.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'EBR'.
    syst-msgno = '056'.
    syst-msgty = 'E'.
    syst-msgv1 = 'WFOOTER'.
    syst-msgv2 = 'WINDOW12'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " writeform_footer
*&      Form closeform
      text
--> p1        text
<-- p2        text
FORM closeform.
CALL FUNCTION 'CLOSE_FORM'
       TABLES
            otfdata                  = tbl_otf
       EXCEPTIONS
            unopened                 = 1
            bad_pageformat_for_print = 2
            OTHERS                   = 3.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'PS'.
    syst-msgno = '005'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " closeform
*&      Form format_pdf
      text
--> p1        text
<-- p2        text
FORM format_pdf.
FIELD-SYMBOLS <fs>.
DESCRIBE TABLE tbl_line    LINES hltlines.
DESCRIBE FIELD tbl_line    LENGTH fle1 IN BYTE MODE . Defect#1579-
DESCRIBE FIELD tbl_objtxt LENGTH fle2 IN BYTE MODE . Defect#1579-
Start of Defect#1579+
DESCRIBE FIELD tbl_line    LENGTH fle1 IN CHARACTER MODE.
DESCRIBE FIELD tbl_objtxt LENGTH fle2 IN CHARACTER MODE.
End of Defect#1579+
CLEAR   tbl_objtxt.
REFRESH tbl_objtxt.
LOOP AT tbl_line.
    htabix = sy-tabix.
    MOVE tbl_line TO hfeld+off1.
    IF htabix = hltlines.
      fle1 = strlen( tbl_line ).
    ENDIF.
    off1 = off1 + fle1.
    IF off1 GE fle2.
      CLEAR tbl_objtxt.
      tbl_objtxt = hfeld(fle2).
      APPEND tbl_objtxt.
      SHIFT hfeld BY fle2 PLACES.
      off1 = off1 - fle2.
    ENDIF.
    IF htabix = hltlines.
      IF off1 GT 0.
        CLEAR tbl_objtxt.
        tbl_objtxt = hfeld(off1).
        APPEND tbl_objtxt.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDFORM.                    " format_pdf
ANy Suggestion or help will be appreciated!
Regards,
Kittu
Edited by: Kittu on Jun 30, 2008 12:32 PM

Hello Julie Waller,
Very Good evening!
Thank you very much for your response!
Sometimes...I miss the basic things and start concentarcting on typical ways to fix the issue. ....which will only make my issue critical.
Hello Sathya,
Thank you for your response!
POints are rewarded..
Have a great day ahead!
Regards,
Kittu

New condition type print preview time out.

Dear all,
I am a ABAPer.
I am facing one problem in PO Print preview.
My MM consultant defines one new condition type-ZPF5 .
Instead of ZPF2 we are using this condition type- ZPF5.
After that in PO ,Net value & everything coming fine.
There is a smartform also related to this.
I have added all logic related to ZPF5 .
But when going to print preview In production & clicking on print preview,
It is giving time out after 9-10 mint-Time out for ALL po,not only for this condition related .
v_no = &SFSY-JOBPAGES& -1. "in this line.
&SFSY-JOBPAGES& means " Total number of pages in the currently formatted print request.
I saw M/08 - ZPF5 Print equal to 'X ' & Statistics is ticked for this.
But when I revert back old SMART FORMS & PRINT = blank,print preview is coming fine for all PO except
ZPF5 Is not affecting in print preview,but in PO affecting.
Any help from MM side?
Thanks
Gourav.

Dear all,
Issue resolved.
I have changed my select query & remove old condition from that,now I am using only ZPF5.
Like :
SELECT SINGLE KBETR KWERT KRECH FROM KONV INTO (V1_KBE,V_PF,V_KREC)
         WHERE KNUMV EQ V_KNUM AND
               KPOSN EQ WA_MAT-EBELP AND
               KSCHL EQ 'ZPF5'. " not zpf2
Thanks all for your time.
Thanks
Kumar Gourav.

Output Type Print Issue

Hi Experts ,
I have a output type ZDDC that is triggered from Shipment document and printed automatically at the end user . Now they dont want the print out automatically for only Belgium. Means ZZDC will be triggered but no auto print out for Belgium . What configuration modification is required for ZDDC so that it wont be printed at the user end automatically only for Belgium.Do I need to modify all the condition records maintained for ZDDC for Belgium . If so what Medium shall I choose or should I keep ..

If the users dont maintain condition record for Belgium, then your requirement would be addressed. On the other hand, if you want to prevent users maintaining condition record for this country, then the logic can be added in the existing smart form being used currently.
G. Lakshmipathi

4650dn printer changing document output from print preview

recently installed 4650dn printer set up was a breeze, then suddenly the printer started changing the document output like there was an internal setting overriding the software settings. almost as if it was confused about the orientation of the paper. i am running vista with the print driver PCL 5. i have tried restoring factory settings, tried different software, finally got it to work in MS word but prefer to use MS publisher, adobe illustrator etc.

Hi Narasimhan,
Yes, your guess is correct. We have tried out the possibility of controlling the print from the user status configuration side of things, but as the user status is at an Operation level, the system status at the header level still gets set, confusing the user that a print was created.
Any other ideas / alternates ?
Cheers,
Ashok.

WE03 Output type with print version '3' (Collective Slip)

I am using output type WE03 with combination of print version 3 (Collective Slip) to print GR slips.
My requirement is to print all the line items on single page (unless there is no room) .
However with this output type one line item is printed per page.
Does anyone manage to print items continously on the page without page break?
Is there any other output type/print version for that?
Well, the last option will be to change the print program and sapscript, but I am trying to avoid that...

Created new print program and replaced sapscript with smartform

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

Configuring output type

Dear experts,
We have attached using NACE smartform for deliveryNote.
I select the output type which is ZD00.
Form preview opens as i have defined preview option only in my code.User goes to Text->Print.
Print is fired .But i get message "output cannot be issued."
Further no entry goes in nast and output type ZD00 comes
yellow triangle.I have used function module for NAST updation.
But it is not working here.I want to define output type ZD00
from my code itself so that i get Output issued succesfully.
and could see green triangle on print out.Simultaneously
nast entry should be populated.
st_control_parameters-preview = 'X'.
st_control_parameters-device = 'PRINTER'.
st_control_parameters-no_dialog = 'X'.
st_output_options-tddest     = 'ZERP'.
st_output_options-tdimmed   = 'X'.
CALL FUNCTION FM_NAME
EXPORTING
ARCHIVE_INDEX              =
ARCHIVE_INDEX_TAB          =
ARCHIVE_PARAMETERS         =
    CONTROL_PARAMETERS         = st_control_parameters
MAIL_APPL_OBJ              =
MAIL_RECIPIENT             =
MAIL_SENDER                =
    OUTPUT_OPTIONS             = st_output_options
    USER_SETTINGS              = ' '
IMPORTING
DOCUMENT_OUTPUT_INFO       =
JOB_OUTPUT_INFO            =
JOB_OUTPUT_OPTIONS         =
TABLES
    i_header                   = i_heading1
    i_detail                   = i_lipsvbap
EXCEPTIONS
   FORMATTING_ERROR           = 1
   INTERNAL_ERROR             = 2
   SEND_ERROR                 = 3
   USER_CANCELED              = 4
   OTHERS                     = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
EXPORTING
    msg_arbgb                    = SYST-MSGID
    msg_nr                       = SYST-MSGNO
    msg_ty                       = SYST-MSGTY
    MSG_V1                       = SYST-MSGV1
    MSG_V2                       = SYST-MSGV2
    MSG_V3                       = SYST-MSGV3
    MSG_V4                       = SYST-MSGV4
EXCEPTIONS
    MESSAGE_TYPE_NOT_VALID       = 1
    NO_SY_MESSAGE                = 2
    OTHERS                       = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

When a Output type in an apllication doc is configured with a Medium, Partner, Lang and other communication paramters an entry is created in NAST table
so to trigger the output an entry in NAST is compulsory
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?
u2022 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.
u2022 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.
u2022 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.
u2022 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.
u2022 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.
u2022 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).
u2022 Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
u2022 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.
u2022 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).
u2022 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.
u2022 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.
Nace

Script form configured to VA01,VA02 & VA03..help me with Print preview?

Hello,
Very Good afternoon!
There is a Script form which is configured to VA01, VA02, VA03.
I have difficulty to access Print preview from Va01/va02/va03.
I am able to access it through T-code SOST.
It is correctly configured in Nace.
When I go to T-code VA02 and provide appropritae saled Order number then it will take me to the next screen there...
I had clicked on Extras>Output>Header-->Print Preview.
It says that Output could not be issued.
When I click on Extras>Output>Header-->Edit
It will display the Output type, Medium, Print Output and
Partner function. I see that it is displaying in yellow color. Genrally it should be green in color.
Can anyone guide me what are the things that I need to check in this window genrally to access Print preview.
Do i need to check anything here in Nast table...?
Please suggest...
Any suggestion would be appreciated.
Thanks & Regards,
Developer.

Hello Sathya,
Thank you for your response!
Sathya- It is correctly configured. it has something to do in the NAST TAble. If it is not configured properly in the NACE then it will not show the out put in the T-code SOSt.
Can you please suggest what I can chcek in the NSAT table or plz tell the standard way to configureing the Output type in this path.
VA03 > Extras->Output>Header>Edit.
Here you have to give its settings....Please chek..
Any suggestions will be apprecaited.
Thanks & Regards,
Developer.

Output types for delivery documents

Hi All,
Please help me out.
Thanks in advance,
Here i got a requirement like i already have the output types for the delivery documents.However i need to copy the existed output types into different names bcoz to customize it for different organization in different region.
The problem is i already copied the o/p types but when i went to vl03n and tris to see the output , am not able to find my o/p type there...am i need to do anything more..
Please help me out as i am a ABAPER and not the functional guy am facing lot of difficulty...
again thanks in advance.

dear govardhan
please refer below
Output Determination Procedure
Output is a form of media from business to one of its business partners. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of Order Confirmations, Freight List, Delivery Notes, Invoices & Shipping Notifications. Determining form of output is output determination
Types of Output: Print Output, Fax, Telex, E-Mail & EDI (Electronic Data Interchange)
PRINT OUTPUT:
SPRO- IMG- Basic Functions- Output Control- Output Determination- Output Det using Cond Tech- Output Det for Sales Documents & output determination for billing documents.
Create Condition Table: select the field Sales Doc Type from field catalog & Save
Maintain Access Sequence: 4-digits code & description. Assign condition table to access sequence. Select Accesses line item and Goto Fields. Fields will display the fields we have selected in the condition table i.e. sales doc type.
Select BA00 & Copy & Rename. Give the same 4-digit code as given to acc seq.
You Can Maintain:
Languages of Output
Partners (to whom we want to send output)
Print Program- print specification
Sap Script- layout
Assign Output Types to Partner Functions: go to new entries & assign your output type to partner functions.
Maintain Output Determination Procedure: V10000 (Standard Procedure). Go to new entries & create your own 6-digit code with descp. Select the procedure & go to Control Data. Here mention the output type i.e. cond type & leave requirement and manual only columns as blank.
Determination Rule: link the 6-digit procedure code to doc types.
Create Condition Records: VV11. Select document type and click on Communication. Mention partner function, medium, time. Output device: LP01, Spool request Name: SD_003, Suffix 2: order_confir & flag on print immediately.
Once you press enter you will come across 2 key combinations:
Sales organization/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to whom the output should be sent, time, medium, language. {It contains: Sales Orgn, Customer, Partner Function (The abbreviated form of the name that identifies the Partner) (During output determination, the system determines the recipient of the output from the master record for the specified partner function. In this field, you can explicitly specify a recipient that will override the standard partner. There must also be a master record for the partner that is specified explicitly.), Medium, Time & Language.}
Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time & Language.
In SAP we can send the documents to respective partner functions through different transmission mediums. SAP uses condition technique to determine output t relevant partners with relevant transmission mediums.
Out put determination procedure has a integration with technical module, as ABAPers has to write SMART forms and FORMS to print the output , that SMART form output can be send to relevant partner function through relevant transmission mediums.
Out put determination procedure for order confirmation: (V/57)
a) Maintain condition table:
Path:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain condition tables
Maintain out put condition table for sales document
Here we define condition table
Ex: 007 order type (sales order types)
Save it
b) Maintain output types:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain out put types
Here we define out put types
Ex:     AF00 -- Inquiry
     AN00 quotation
     BA00 Order confirmation
     BA01 EDI odd response
     KRMLCredit processing
     LP00 -- Scheduling agreement
     MAIL Internal message
     RD03cash sales invoice
Choose BA00 copy it and rename as a MA00
click on details icon
click on display to change icon
then again choose MA00 click on details icon
Maintain data in general data tab
General data tab:
Access sequence: 0010(order type)
In IMG define access sequence and assign to the output type
Check access to conditions:
     This indicator allows the system to read the condition records for output. If it is not been activated then system determines out put from customer master ex: By following out put determination procedure DB0001
Check cannot be changed:
     This control specifies whether the out put can be changed or not
Ex: direct mailings can be changed during processing
Check multiple issuing:
This indicator allows the system to send the output multiply
Ex: sales order has been sent for 10 items again one item has been added to sales order so that business has to issue the new out put for sold to party with added line items. This indicator allows the system to send out put repeatedly.
Check partner independent out put:
During output processing when the indicator has not set then system allows only specific functions in specific partner functions
Dont write processing:
This indicator determines whether system has to write processing log for output
Default values tab:
Dispatch time:
Ex: send immediately: when carry the application this indicator determines when the output should be sent.
Transmission medium:
Ex:     print out
     Fax
     Telex
     Internal send
     EDI
     Simple mail
     Special function
     Events (SAP business workflow)
     Distribution (ALE)
     Tasks (SAP business work flow)
Specify the transmission medium through which the output should be sent. (Ex: print output)
Communication strategy
Specify the communication strategy if you want to send the output externally
A) Time tab:
Check timing: (Periodic job not allowed)
This indicator allows the system to carry out print program periodically.
B) PRINT NEXT TAB):
Print parameter: Ex sales org.
     Specify the print parameter.
Click on mail title & Text control button under dialog structure.
Here we assign title for the mail along with relevant text Ex:-EN (English)
Processing routines control button under dialog structure.
Here we assign programs form routines & form that are written by ABAPER, they           they various transmission mediums.
Ex; - Transmission medium      shortest      program     form routine
          1                  print out     RVADOR       entry
Click on position function control button here we assign relevant partner function to relevant transmission mediums
          EX: print out: SP (Sold to party)
C) Maintain access sequences:
     Here we define Access sequence.
EX: 0010 & Assign the condition tables to this output.
D) Assign out put types to partner function:
     Here we assign output types along with transmission mediums to relevant partner functions.
EX:      Out put type          Transmission medium
       MA00                    1
                              2
                              6
                              A
       MAIL                    7
E) Maintain output determination procedure:
     Here we define output determination procedure
Ex:     V10000     -     Order output
     V05000     -     Inquiry output
     V06000     -     quotation output
     V10001     -     Cash sales output
Choose output determination procedure EX; V10000, copy it& rename it as MA0000
Assign output type MA00 by going control date section.
Save it.
F) Assign output determination procedures;
Allocate sales document Header.
_ Choose sales document type OR & Assign output determination procedure i.e MA0000 & Assign output type MA00.
Assign sales document items.
-Choose item category TAN & Assign output determination procedure Ex: Ma0000
- save it & exit.
Maintain output records (vv11)
Path:
Logistic > S&D > Master data > output > sales document > VV11 Create
Specify output MA00, Click on Key combination & specify sales document type (OR), partner function (sp) transmission medium (1) dispatch type (4) language (EN)
Click on communication button on application tool bar
Specify output device LOCL or LP01
Check print immediately check release after output
Save it
Go to Va01 raise the sales order
Go to extra button output header edit.
Specify output type: MA00 partner function
Select line, click on communication methods
Specify logical destination
Check print immediately
Check release after output
go back save it & exit
Go to VA02, Go to Extras output header print preview
Check out (order confirmation
(ERROR: out put MA00 for partner cannot be processed)
rewards pls
siva

Print preview in abap list format (OMLV) - Need preview in graphical format

Dear All
I am facing a problem with the print preview. (transaction code OMLV)
When i am clicking on print preview button the system is displaying the output in a ABAP list format.
and also the printout shows only the ABAP content.
Pl. advise on how to view the print preview in a graphical format and not in the ABAP list format and pl. let me know the setting to print the spool in the graphical format.
Thanks,
Maxx

Hi,
this problem is not only related to warehouse. even the print preview spool for GR/GI slip in t-code SP01 shows as ABAP list and not as graphical screen.
my question is why does the system shows the print preview for spool as an ABAP list instead of graphical view.
pl. advise
Thanks,
Maxx

Output type - Print preview Commodity code

Similar Messages

Maybe you are looking for