Defining output type to a transaction

Hi friends,
1) I have a transaction VF02.
I have created two smartforms for this transaction.
While issuing output in VF02. i can find only one output type RD00.
i also want to include ZD00.
2) is it possible to create our output types for any transaction. if yes , how to do it?
thank you,
kat.

Hi,
Is the out put types already available, if yes then just use VV31 to create new condition record for billing types and sales org.
Alse you need to follow the below steps,
SPRO-Sales & Distribution-> Basic Functions-> Output Control-> Output Determination-> Output Determination Using the Condition Technique-> Maintain Output Determination for Billing Documents-> Maintain Output Types, Maintain Access Sequences, Assign Output Types To Partner Functions, Maintain Output Determination Procedure, Assign Output Determination Procedures.
Once it is done use VV31 to create condition record.
Just an example below:
Check this hope it helps, select the meduim 1 print instead of edi. hope it helps..STEP 1: Output Type Config
Create Z810 output type with access sequence key Billing Type  Sales Org  Customer. Z810 is based on the SAP standard RD00.
The following steps are executed in the IMG at the following path:Sales and Distribution -> Basic Functions -> Output Contrl -> Output Determination -> Output Determination Using the condition technique -> Maintain Output Determination for Billing Documents
1.       Create Condition table (Tx: V/63)
·         Table 950
·         Description Bill.type / Sales org. / Bill to
·         Selected fields Billing type, Sales organization, Bill-to party
2.       Maintain access sequence (V/54)
·         Access sequence ZEDI
·         Description Bill.type / Sales org. / Bill to
·         Access Table 950, Exclusive
·         Fields:
o        FKART, KOMKBV3, FKART
o        VKORG, KOMKBV3, VKORG
o        KUNRE, KOMKBV3, KUNRE
3.       Maintain output type (Tx: V/40)
·         Output type: Z810
·         Description: Invoice
o        General data:
§         Access sequence: ZEDI
§         Check: Access to conditions
o        Default Values:
§         Time: 1
§         Transmission medium: 6
§         Partner function: BP
·         Processing routines:
o        Medium: 6
o        Program: RSNASTED
o        Form routine: EDI_PROCESSING
·         Partner functions:
o        Medium: 6
o        Function: BP
4.       Maintain Output Determination Procedure
·         Procedure: V10000
·         Control data: Insert step 11: Condition type: Z810 after RD00. No requirement
5.       Assign output determination procedure (V/25)
·         Doc type: ZF1
·         Output procedure: V10000. Clear output type => Either RD00 or ZD00 can be used
STEP 2: Condition Record (VV32)
The table below shows the values for the condition records.
·         Part Fn: Partner function
·         Med: Transmission medium
o        6 = EDI
·         Time
o        Timing = 1 implies that a background job (running program RSNAST00) will process the output.
o        Timing = 4 implies that the output will be created immediately on document save.
Thanks & Regards,
Nagaraj  Kalbavi

Similar Messages

  • Hiii friends! how attached output type to a transaction

    Hi gurus!
    how to attached output type to a transaction.
    for eg - i have created a outout type zexpt and i have to assigned to transaction VF01.
    Regards,
    Rahul

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

  • Update LIKP table while saving the output type in VT02N transaction

    Hi All,
    I have a requirement where i have to update Delivery Priority(LPRIO) field in LIKP table while saving the output type in VT02N transaction. I am not able to use the BAPI "BAPI_OUTB_DELIVERY_CHANGE" or FM "WS_DELIVERY_UPDATE" because, when we save the output type the programs that are configured in NACE are triggered in update mode and hence i will get a roll back error.
    Let me know other ways of updating the table at the time of saving output type for shipment transaction VT02N.

    This could be a result of one of the following reasons:
    1: Incorrect smart form/routine assigned in the output configuration (NACE)
    2: Serial number range of the delivery expired
    3: The default settings of the user (SU01) processing the delivery is missing the default printer name.
    Hope this is helpful
    Manish

  • Define Output type and Local destination per user

    Hi Gurus,
    Nowadays us have defined Output type by Sales Organiztion/Order Type (S_TCODE = VV11).
    Is possible define Output type and Local destination per user?. How to do?.
    thanks and best regards,
    Wilson

    Hi Wilson
    As per my understanding of requirement: you want output type and Local destination for each SAP End user (i.e. who is processing sales order) not the customer. If this is the requirement, we have two solution for it:
    1) If for a particular region/sales district customer are contacting to one particular destination, then create access sequence with output type/order type/sales district. Means for one sales district one Local destination. If sales district is big area and you have many local destination with in that, then you can divide it into regions.
    2) Ask your ABAPer to create a Z table and maintain Local destination for all Users. And amend the print program such that before saving the output entry into NAST table, based on SY-UNAME(user's id), fetch the printer (local destination) from Z table and update the NAST table accordingly.
    As per my observations, option 2 is simpler and more effective.
    try and revert.

  • 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.

  • How to change output type of MI21 transaction ?

    Hi All,
    Whenever I am executing the MI21N transaction, its default output type is SAP Script.I want to get this output as a SMARTFORM. How can I do that ? Kindly advise on the same.
    Regards,
    Ankur Mishra

    Hi Ankur Mishra,
       Are you planning to print Physical Inventory Documents through Smart forms (MI21)? As this is related to MM, please post your question on SAP MM forum.
    With Regards,
    Srinivas

  • Hiding the Output types for ME22n transaction

    Hi,
    We have a requirement in removing the output types from the message tab of ME22n trasaction.we have defined 2 output types for the same NEU and ZFES a special function,we need to check if the PO is already assigned with ZFES then the NEU output types should not be displayed over there in messgaes tab.
    Any pointers will be really helpful.
    Thanks,
    Jay

    Use EXIT function  VN000001 for output selection
    write down your code as per your need .
    thanks
    abhishek

  • DEFINE VALUATION TYPE IN  MIGO TRANSACTION.

    DEAR ALL,
    pls. guide me how to define the valuation type in material master and basic criteria for it. as well as i want to define this valuation type in migo transaction also.
    pls. reply as soon as possible.... its urgent.
    bst rgds,
    rajesh

    Hi,
    Refer below link;
    [Split Valuation|http://www.sap123.com/showthread.php?t=29]

  • How to define output types email or external send in the report program

    Hi all,
    now we are using a zprogram for output type printer and standard program RVADOR01 for output type external send. Now i want to modify my zprogram itself to support external send email as well as printer also. What modifications should I have to make in my zprogram. My form is a script.
    Thank you,
    Mallik

    hi all,
    i made the following changes in my code and it worked well.
    thank you for all who tried to share my pain.
    thanks one and all.
    hope this code will help anybode.
    thanks & regards
    FORM OPEN_FORM_EMAIL.
    TABLES: TNAPR,                         "Programs & Forms
            ITCPO,                         "Communicationarea for Spool
            ARC_PARAMS,                    "Archive parameters
            TOA_DARA,                      "Archive parameters
            ADDR_KEY.                      "Adressnumber for ADDRESS
    TYPE-POOLS SZADR.
    DATA: LVF_DEVICE LIKE ITCPP-TDDEVICE,
          LVF_DIALOG(1)     TYPE   C   VALUE ' ',
          LVS_RECIPIENT     LIKE   SWOTOBJID,
          LVS_SENDER        LIKE   SWOTOBJID,
          LVS_SNAST         TYPE   SNAST,
          LVF_PROGRAM       LIKE   SY-REPID,
          LVS_COMM_TYPE     TYPE   AD_COMM,
          LVS_COMM_VALUES   TYPE   SZADR_COMM_VALUES,
          LVS_TITLE LIKE SNAST-TDCOVTITLE.
    reset return code
      RETCODE = 0.
    if there is a communication strategy used ...
    IF NOT NAST-TCODE IS INITIAL AND NAST-NACHA EQ '5'.
      ... use stratagy to get communication type
        CALL FUNCTION 'ADDR_GET_NEXT_COMM_TYPE'
             EXPORTING
                  STRATEGY           = NAST-TCODE
                ADDRESS_TYPE       =
                 ADDRESS_NUMBER     = KNA1-ADRNR
                PERSON_NUMBER      = VBDKA-ADRNP
                  PERSON_NUMBER      = ADDR_KEY-PERSNUMBER
             IMPORTING
                  COMM_TYPE          = LVS_COMM_TYPE
                  COMM_VALUES        = LVS_COMM_VALUES
           TABLES
                STRATEGY_TABLE     =
             EXCEPTIONS
                  ADDRESS_NOT_EXIST  = 1
                  PERSON_NOT_EXIST   = 2
                  NO_COMM_TYPE_FOUND = 3
                  INTERNAL_ERROR     = 4
                  PARAMETER_ERROR    = 5
                  OTHERS             = 6.
        IF SY-SUBRC <> 0.
          RETCODE = SY-SUBRC.
          SYST-MSGTY = 'E'.
          PERFORM PROTOCOL_UPDATE.
        ENDIF.
    ENDIF.
       LVS_COMM_TYPE = 'INT'.
      CLEAR LVS_COMM_VALUES-ADSMTP-SMTP_ADDR.
      CLEAR LVS_SNAST.
            LVS_COMM_VALUES-ADSMTP-SMTP_ADDR = V_CUST_EMAIL.
    convert communication data
       MOVE-CORRESPONDING NAST TO LVS_SNAST.
            LVS_SNAST-ANZAL = 1.
            LVS_TITLE = 'Mail Header Title'.
      MOVE LVS_TITLE TO LVS_SNAST-TDCOVTITLE.
       MOVE SY-REPID TO LVF_PROGRAM.
      CALL FUNCTION 'CONVERT_COMM_TYPE_DATA'
           EXPORTING
                PI_COMM_TYPE              = 'INT'
                PI_COMM_VALUES            = LVS_COMM_VALUES
                PI_SCREEN                 = XSCREEN
              PI_NEWID                  =
                PI_COUNTRY                = ADRC-COUNTRY
                PI_REPID                  = SY-REPID
                PI_SNAST                  = LVS_SNAST
                PI_MAIL_SENDER            = SY-UNAME
           IMPORTING
                PE_ITCPO                  = ITCPO_LS
                PE_DEVICE                 = LVF_DEVICE
                PE_MAIL_RECIPIENT         = LVS_RECIPIENT
                PE_MAIL_SENDER            = LVS_SENDER
           EXCEPTIONS
                COMM_TYPE_NOT_SUPPORTED   = 1
                RECIPIENT_CREATION_FAILED = 2
                SENDER_CREATION_FAILED    = 3
                OTHERS                    = 4.
      IF SY-SUBRC <> 0.
        RETCODE = SY-SUBRC.
        SYST-MSGTY = 'E'.
        PERFORM PROTOCOL_UPDATE.
      ENDIF.
      CHECK RETCODE EQ 0.
    fill structure itcpo
      ITCPO = ITCPO_LS.
    open form
      CALL FUNCTION 'OPEN_FORM'
           EXPORTING
              APPLICATION        = 'TX'
               ARCHIVE_INDEX      = TOA_DARA
               ARCHIVE_PARAMS     = ARC_PARAMS
                DEVICE             = 'MAIL'
                DIALOG             = 'X'
                FORM               = 'ZSDLS003'
                LANGUAGE           = SY-LANGU
                OPTIONS            = ITCPO_LS
                MAIL_SENDER        = LVS_SENDER
                MAIL_RECIPIENT     = LVS_RECIPIENT
              MAIL_APPL_OBJECT   = ' '
              RAW_DATA_INTERFACE = '*'
         IMPORTING
              LANGUAGE           =
              NEW_ARCHIVE_PARAMS =
              RESULT             =
           EXCEPTIONS
                CANCELED           = 1
                DEVICE             = 2
                FORM               = 3
                OPTIONS            = 4
                UNCLOSED           = 5
                MAIL_OPTIONS       = 6
                ARCHIVE_ERROR      = 7
                OTHERS             = 8.
      IF SY-SUBRC NE 0.
        CASE SY-SUBRC.
          WHEN 7.
            RETCODE = SY-SUBRC.
            SYST-MSGID = 'VN'.
            SYST-MSGNO = '096'.
            SYST-MSGTY = 'E'.
            SYST-MSGV1 = NAST-KSCHL.
            SYST-MSGV2 = NAST-KAPPL.
            PERFORM PROTOCOL_UPDATE.
          WHEN OTHERS.
            RETCODE = SY-SUBRC.
            PERFORM PROTOCOL_UPDATE.
        ENDCASE.
      ENDIF.
      SET COUNTRY ADRC-COUNTRY.
    ENDFORM.

  • Clarifications in picklist output type EK00 for transaction VL02N

    Hi evryone,
                      Can anyone please help me to generate a smartform for picklist output type EK00 for Tcode VL02N. In application V2 the standard program is  RVADEK01 and the form SD_PICK_SINGLE,
              what is the best way to create smartform and driver program , can I use the Standard Program or write the new driver program..
    with regards,
    Mittu

    I dont think this is the right forum to post such question.  This should have been posted in ABAP forum
    thanks
    G. Lakshmipathi

  • Output type problem for transaction MRKO

    Hi,
    Transaction mrko should create invoice & post invoive document to spool.
    When i execute the transaction with mat doc i can see invoice document created but can’t see layourtin spool.
    But i can  see layout when i execute mr91 output message types with processing mode  1 (processed without error).
    Layout is processed without error but not in spool why?.
    Similar transactions mrrl, mris when i execute i can see layout in spool but not mrko.
    Pls suggest guys what to do to see layout in spool.
    Thanks for all your help in advance.

    Hi,
    Can any one tell me whats the use of MR90 MR91 Transaction?
    Also in that processing mode..
    Much  Awaited for your answer.
    Thanks

  • Output type settings; print pdf from on the printer defined in user profile

    Hi
    I have a requirement where i should print the pdf form in the printer defined in user profile when i select save in MB1A transaction;  I know this can be done by changing the output type cofiguratioin in the NACE transaction
    Could any one please let me know step by step process on how to make changes in the nace transaction to print the form in the printer defined in user profile
    Right now we are using a custom output type i tried changing the print parameter to 'S'   and followed the sap documentation
    in the sap help doc at last it says to check the table TNADR for the entries
    but when i saw the table TNADR i couldnt find any entries related to ME application
    It would be great if any one can explain in details regarding the changes in output type configuration , TNADR table and related stuff
    thanks

    Hi,
    Just maintain the condition records in NACE transaction.
    Just follow the steps...
    1.Goto NACE transaction
    2.Select the application for example for sales order 'V1' and then click on 'Condidtion Record' button
    3.Double click on your Zoutput type.
    4.U will may get radio button dialogbox/key combination.select anyone and click on ok button
    5.U can see a selection screen..Fill all the filed/fileds.
    6.Click on F8
    7.A tabular control appers..fill it. select the mediem as 1(print output).U can see a  'communication' button over there..click on it.
    8.Maintain ur own printer settings and click on SAVE button..
    Actuallly Condition records contain the actual data against which the business rules are checked to propose an output. Using condition records, we can define Output types, transmission medium for the document type. So that we need not to give all the output parameters every time the document is to be printed. We use the condition records for automatic printing of Invoices when we save it.
    It maintains a key combination to process the output automatically whenever a system finds the entry/entries with that key combination. We maintain the values in the condition records only.
    Hope it is useful...
    Regards
    Kiran

  • PO Output type with Option 5 External Send (&EKKO-EBELN&)

    Dear Friends,
    We have come across and interesting issue.
    We want PO output to be send to vendor via email and the email subject should be "New Purchase Order <po document no>". To achieve this requirement we have set the Output type NEU --> Mail title and Text as NEW PURCHASE ORDER &EKKO-EBELN&.
    When PO is created and before saving the PO user select the option 5 External Send in Message and further go to the communication tab. he can see the 'NEW PURCHASE ORDER &EKKO-EBELN&.' in Cover Page Text.
    But the movement user saves the PO, Message --> communication is replaced with 'NEW PURCHASE ORDER".
    And finally when the mail is sent with no PO document number and subject as "NEW PURCHASE ORDER".
    Has any one has come across this issue before?
    Or is there any OSS note for this?
    Please Help!!
    Sandeep

    dear sandeep
    you can follow below mention steps or reffer OSS
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check out the OSS note :191470
    Hope this will help.
    reward points if helpful
    thanks and regards
    ravikant dewangan

  • 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

  • Output type assign to VF02

    Hi All,
    I created Output type through NACE transaction.
    When i was trying to assign that in tranx VF02>billing #->enter->goto>header--->output.
    Here i was trying to assigning my output type.
    I am getting error that 'Output type is not defined'.
    But when I go to NACE tranx there it exists.
    please suggest what went wrong or am i missing some thing.
    Thanks in advance,
    Deepak.

    Hi deepak,
    After creating OUTPUT TYPE in NACE ,
    U have to assign the output type in SPRO transcation
    SPRO - > SD - BILLING -> detemine output type
    this is done by SD consultants.Please get their help.
    regards,
    Prabhu
    reward if it is helful

Maybe you are looking for

  • Report developement Requirement.

    Dear Experts, I want know detaily about the reoprting in materials management. a) What is the difference between Script, Forms and Report. b) What is ABAP query, which functional consultant can use. Is it permanent report which can be used by users f

  • Tools for validate HTML and CSS Error in DW?

    Hello Guys, Want to know any addon or menu tool in Dreamweaver to validate HTML and CSS error. Because every time i have to check in w3c validation. If DW having in this options it wouldbe great to develop website with out error. Please let me know y

  • SharePoint 2013 Most Popular Items Requirements

    Hi all, I have a General question regarding Usage Data and "Most Popular Items" functionality. Can anyone provide a list of requirements for this Feature? Currently the Problem is following we have Setup an Environment with latest CU, configured Sear

  • Virtual server and Firewall

    Hi all, Sorry if this is a too basic question. I'm trying to understand how our system works as I'm not the one that set it up in the first place. The Firewall crashed today and needed rebooted. When connected to the the server it says "Kernel-Power"

  • Activating Confirmation Tab in Return Purchase Order

    Hello, My problem is when I am creating a return in me21n, in the item header when I cliked in the confirmation tab it is not active. How can I activate this ?