Version Management-Output Type

Hi Gurus,
Is there anyway Version Management in PO, related with output type of PO. I mean is there config to be done in message determination for Version PO?.
Thanks in Advance.

Hi,
Version management relates to PO output.
There is no configuration required in output type / message determination , but in Version management configuration, we set this check box for output.
Materials Management -->Purchasing >Version Management>Set Up Change Displays ..
Unless you complete the version in Purchase order you will not be able to generate Print out.
Thanks & Regards,
Sridhar.G

Similar Messages

Version management output type issue

hi,
we have activated version management and all working fine .
but while taking print out through ME9F we have assigned to 3 output types (NEU,ZNEU,ZNIU) for a single PO , until and unless we take print for 3 output tyes we are not able to amend the PO .we are getting the below error .
"No new version created because a message has not yet been transmitted"
is there any option if we take print for one output type(ZNEU )out of 3 output types(NEU,ZNEU,ZNIU) it should allow us to do changes in PO .
please assist we need to close the requirement on priority .
thanks in advance

HI,
is there any option if we take print for one output type(ZNEU )out of 3 output types(NEU,ZNEU,ZNIU) it should allow us to do changes in PO .
No i don't think so system will create new version.
new version is created when you output PO completely
try this create pool request for other two message in Message tab in PO in ME22N and then try PO it will work
Regards
Kailas Ugale

Clarifications in pick list output type EK00

Hello ,
Have any one of you used the pick list output EK00 . I have
tried this and I do have some issues with
We are using SAP R/3 4.7 x 200 version .
Output type EK00 is not available in the application V2 (
Shipping ) . Its available in application V4 (Shipping special
case).
1. I have assigned the shipping points through T code VOK2 as I
am not able to find the output EK00 through customization menu.
2. I have maintained the printers details through VP01SHP ( correct me if I am wrong) . I am using the standard program RVADEK01 and form
SD_PICK_SINGLE in the output EK00.
After doing the above setting when I am creating delivery in
VL01N , the output type EK00 is not assigned automatically and
when I try to assign it manually , it gives an error message
"Processing program missing for output EK00 (medium 1)in
application V2" . I dont know why the system is looking for
application V2 when it is not available in V2 and only available
in V4 .
Am I missing anything in my process . Can some one help me in this .
With regards,
Joseph Anand.B

Dear Joseph,
Have you done the following setting in transaction v/38:
1.On the Display View "Output Types": Overview screen, in the Output type group box, select EK00. (Application V4)
2.In the left frame, under Dialog Structure, double-click on the Processing routines folder.
3.On the Change View "Processing Routines": Overview screen, choose .
4.In the first medium, for Print output, enter the Smart Form print program /SMB40/RVADEK01 under Program and Smart Form /SMB40/SDPIK_L under SmartForm.
Document Types        Picking List
Output Types          EK00
Transaction Code      v/38
Smart Form Program    /SMB40/RVADEK01
Smart Form            /SMB40/SDPIK_L
                      /SMB40/SDPIK_A
5. Save the changes.
Regards,
Naveen.

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

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

Need to call custom version of RSNAST00 from VF03 output type

I have created a customized version of the RSNAST00 program which is valid for two existing ouptut types for billing condition "V3". This new program (ZRSNAST00) works fine when called directly (i.e. se38). However, when issuing output type via VF03, the old program is called (RSNAST00). Is there a setting to tell the output type to use ZRSNAST00?
FYI, I have checked NACE, and the output type references the print program (which is the same for both versions of the driver program.
Thanks for any help!
jeff

There is some special sort I had to include for printing. Client needed to have page-number order (single page first, 2-page next, etc.) in the spool.
I may need to create new output type for the ZRSNAST00 version to run, and leave RSNAST00 for the "normal" single processing via VF03.

How to create a new output type in inventory management

dear consultants .
how to create a new output type in inventory management...........?
please give me a solution
regards
ratan

Refer:
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/attaching-smartform-to-the-standard-transaction-2316027

Version management print output

Dear SAP Gurus,
How to fetch version management changes in the print output.
My client requirement is in the print output they need, in the first page the original data should be fetch and in the second page they need only the changes which has been made for that particular version number,
ex:data before po changes
materialx quantity 10 delivery date 01.05.2014.
after changes
material x quantity 15 delivery date 01.05.2014.
In the printout put first page
materialx quantity 10 delivery date 01.05.2014(dathanges)a before c
second page
changes:quantity 15.(version1)

Hi pavan kumar ;
Can you try to run AUT10 for ME21N tcode ? You will get a list which can be filtered table EREV.
Regards.
M.Ozgur Unal

Configuration of Output Type within Inventory Management

Hi Experts,
I am on ECC 5.0 and have a following requirement.
I need to create a output type for printing the material documents. There is a requirement that, newly created output type should be only used by given Company code and Plants under it. In other words, need to restrict use of this output type by Company Code.
I was initially thinking of creating new (by copying standard ofcourse ) Condition Table and Access Sequence, reading documentation help on their config nodes, I understood that SAP does not recommend to create new Condition table for fields like Plants, Storage Location. Printer determination can be restricted on Plant and Storage location level, but my issue is regarding restricting use of outuput type itself.
Can anybody suggest please?
Thanks and Regards,
Amit

Hi Charlie,
Thanks again, thats very nice of you.
According to help document on this node and the config which goes into this node, it seems that this node controls only "printer determination" for the combinatin of O/p Type, Plant and Storage Location, Whereas my requirement is to restrict the use of O/P type itself per Plant and not the Printer. Can you please address this?
Looking forward for you kind reply.
Best Regards,
Amit

Output Type MLFH

Hi,
wondering if anyone knows how to set up the MLFH output type to print the document to for example a LOCL printer at the time of the GR. Is that possible vs. just sending a e-mail ? I've tried all the configuration related to maintaining the output types and conditions as well as maintaining the printer determination but I can't get the document to print.
In maintaining output types the notes state:
An entry must exist in table TNADR for each output type of application ME (Inventory Management) but this is not a table with a table maintence dialog.
Any help is appreciated.
Thanks

Go through these steps you can get the GRN Printout
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
Enter the local printer where you want to print your Goods posting document
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 Goods Receipt/GI/Transfer Posting Documents
Here for Particular mvt type 101,201,121,311 etcu2026 Maintain the Print item as 1--Material document printout
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 following--
Select the particular Output type then goto Details
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Transmission medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Printer Determination by Plant/Str Loc, 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.

Two output type

Hi Gurus,
I've a typical issue here.
I've two output types for sales order .Maintain condition record ,access sequence,VOFM routines individually perfectly for both output types.
1st output type - no multiple issue..(maintained in NACE)
2nd output type - multiple issue.(maintained in NACE properly)
While creating order both outputs are issued(fine).
But while changing order, 2nd output type has to be issued but its not.
When I debugged , its looping the entries already present in NAST table.(checking the first output type for multiple issue)
its not and then its completely coming out of the program without checking the second output type for multiple issue.
Is there any extra settings I've to do or its SAP bug.
Regards,
Ponraj.s.

Hi,
There are two options.
First is, use the same output type for all the movement types. Iin the smartform itself you can put conditions
based on movement type to call a particular window.
Other options is in SPRO->Materials Management->Inventory Management and Physical Inventory->Print Control
->Maintain Print Indicator for Goods Receipt Documents. Maintain different indicators for 102 and 122 (For ex. 2)
Then maintain the condition record for the output types WE02 and ZA01 accordingly.
Maintain output type WE02 for Trans./Event Type - WE, Print Version - 1 or 2 or 3 and Print Item as 1.
Maintain output type ZA01 for Trans./Event Type - WE, Print Version - 1 or 2 or 3 and Print Item as 2.

Basic Version Management

I would like to see basic version management functionality built into LR. This would allow the user to not only create different versions of an image, but keep track of their relationships and status.
As a fine art nature photographer, I might have an original RAW file, a PSD master file, a series of TIFFs optimized for various print sizes, a JPEG for my web gallery, and maybe a different JPEG for slideshows. I can stack these together, but LR doesn't allow me to relate them as different versions of the same image or keep track of their status (maybe the TIFF for a 16x20 print needs more work, but the 11x14 is done).
Ideally, the Version Management would allow the user to set up a list of version types and statuses. Image versions could be moved from one status to another manually or automatically based on rules. An interactive chart could display the version relationships and allow the user to change statuses quickly.
Different versioning templates would be needed for different types of workflow. One might be used in the above example of a landscape photo that has multiple output types and sizes. A different template would be needed for a panorama built from multiple original images but going to the similar types of output.
Full-featured version management might be best left to a 3rd party module, but the versioning and status information would have to be kept in the LR database.
Brent Gilstrap

Jeff,
First may I say, "Thank You" for the excellent LR video tutorial you did with Michael Reichmann. That got me up and running much faster than I expected!
And thank you for taking the time to reply to my request. Getting back to version management, I must disagree with you that this is a simply an old vs. new workflow issue. This is about letting me work around the limitations of LR.
I don't know about you, but I sharpen somewhat differently for different size prints and for different papers. I also print colored borders on many of my prints - the width of the border varies with the print size (and is well beyond the 20pt maximum stroke border in LR). Also, as I use the ImagePrint RIP and often wish to print borderless on roll paper - at times I must go outside the LR print module to get the print output I want (LR + PTAPP does not support borderless on roll paper yet).
I can't imagine that LR will ever be feature-rich or smart enough to support everything I want from within the Develop and Print Modules. Ok, I CAN imagine it, but I'm not expecting mass-marketed software to meet all of my needs. Once LR has expert sharpening & noise reduction, soft proofing, more flexible print borders, etc... I'll re-evaluate the situation.
For now and the foreseeable future, I will need multiple physical files for print output. I can stack these to group them with the original RAW file - but LR would be so much more useful to me if it could also keep track of the use and status of these different files.
Based on your reply... I'm thinking I'm going to have to develop a Version Management module for LR myself. If only LR had scripting. Doh!
-BG

IM output types

Dear MM Consultants,
I want to knoe the differance between the following output types.
WE01/0/03 WA01/02/03
My reqt is i want to print morethan 1 item in GR/I print out.
I made all setiting in OMBr/ NACE/Mn21etc...
Still i am not getting the output
One more qn
Can we use we01 for collective slip??
pl reply
guru

Guru,
You should have all of the following settings:
1. Configure Print Control for transaction MIGO:
>SPRO: Materials Management > Inventory Management and Physical Inventory > Print Control > General Settings > > Print Version
>
>Tcode = MIGO
>P = 3 (Collective slip)
>
>This will set the default selection on the MIGO screen to "3" (Collective Slip)
2. Configure output Type
>SPRO: Materials Management > Inventory Management and Physical Inventory > Output Determination > Maintain Output Types
>
>Output type = WE03
3. Configure Output Determination Procedure
>SPRO: Materials Management > Inventory Management and Physical Inventory > Output Determination > Maintain Output Determination Procedures > > Conditions: Procedure
>
>Condition Type = WE03
>Requirement = 173
>
>Requirement 173 limits output to be generated for the first item only (even If you want all line items to print on the same GR slip - you only want the output record to be created once - not for each line. 173 does this for you
4. Create Output Condition Record in each client in Tcode MN21
>Output type = WE03
>Trans/Event Type = WE (Goods Receipt for Purchase Order)
>Print version = 3 (Collective slip)
>
>If you already have WE03 set up with settings other than described above, you may need to delete it first and then re-create it using the information above.
5. If all of the above settings are correct and you still do not see all line items on the same GR slip, then I would consult your developer to see if they changed anything in the Output program, Routine, or the SAP Script/SmartForm

PO Version Management

Hi All ,
For PR we can configure the fields which are relevant for VERSION MGMT but feel there is no such config available for PURCHASE ORDER ( or other external documnemts)
In this regard I have two queries ,
1) What all fields of PO are being considered to create a NEW VERSION , as per SAP standard funcationality.
Would like to share , I did check for Qty and Price change , for both these fields system is creating new Version ( after message is outputted) , but it is not creating NEW version for certain fields.
2) SPRO - MM- Purchasing - Version MGMT->"SETUP FOR CHANGE DISPLAY"
What is the use of this Config , here we can define combination for Document Type , Table , Field + some more settings related to display etc
Also here is field called "Category"
As per system help , it is saying
"You can assign a character to related fields. You can then use this character to select the fields in the application" ..................Which application is this ??
Thx in advance for all your valuable reply.
regards
Shrey

Hi
You activate version management for purchas orders. The changes to purchase requisition fields (which you define in version relevant fields for PRs) trigger version creation in purchase order - if you are creating PO w.r.t PR.
Thanks

FORM ROUTINE in Output Types

Hi group,
there is a requirement in which after the generation of accounting document(after saving VF01), we need to immediately reverse some of the lines in the accounting document by using F-02. We have thought of using the Output Type Program to write our code as that was the only genuine place we could find to write our enhancement ( searched for user-exits after accounting doc is generated but cudn't find any). In the program , we shall write the BDC for aor reversal process. Now, when we SAVE VF01, this program(RLB_INVOICE, output type RD00) gets triggered. I thought instead of writing something in the standard program( or even a Z version of it ), we wud write our code in a new program & then assign this program in NACE. I tried with some dummy program(zxxxxx), but there is an error log which says 'Processing Routine Entry does not exist for program zxxxxx).
what is the significance of this FORM Routine 'ENTRY' in the output type??? wat is the solution for my problem??
hope i am clear enough
ur valuable inputs awaited...
Thanks & Regards,
Bikash Agarwal

Hi
The routine ENTRY is the start form called by the progam runs the print (RSNAST00 for example), that routine has to be defined in the program is assigned to output type.
See the program RLB_INVOICE, here you can find the form ENTRY.
So the program manages the print for the output type RD00 run a comand like this:
PERFORM ENTRY IN PROGRAM RLB_INVOICE USING .......
I don't think there's an exit after accounting document is created, there are some BTE (trx FIBF) are triggered just before it is generated, for example in BTE 1030: here you can know all accounting number and data (but the document isn't stored in database yet).
I don't know if it's a good idea to insert the code in the routine of the print: remember all the process of saving of account document are running in update tusk, so while the output is been printing you can't be sure the accounting document is really stored in database.
Max

Version Management-Output Type

Similar Messages

Maybe you are looking for