Controls available in Output type

Hello Gurus,
Could you please tell me different controls available in Output types.
How different we configure the condition records for print and EDI output?
Points will be rewarded generously.
Thanks and Regards,
Pavan P.

well in con recs we can maitain wht are the medium and partner tht shld be sent output if u want to configure is through a mail
here is how it goes
1         Automatic e-Mail Confirmation
When a sales order that has been created on the web has been saved, this should trigger an automatic email confirmation to be sent out. The configuration is described below at a high level (primarily screen shots). In this example, a new output condition type is created, which will trigger the email confirmation for the order type(s) used for Internet orders.
<! This documentation does not cover the setup of the email server (Exchange, SendMail, etc.),RFCs, SAP Office, and development of the SAPscript form, since these are different at each site. This document covers the configuration required within the SD module of the R/3 system to trigger the generation of output via email. !>
1.1        Condition Type ZEXT
IMG menu path:
Sales and distribution > Basic functions > Output control > Output determination > Output determination using the condition technique > Maintain output determination for sales documents > Maintain output types
1.1.1       General data:
The access sequence ensures that this output will only be used for Internet orders. This assumes that one or more order types are used exclusively for Internet processing.
1.1.2       Default values:
The default values indicate that the output is triggered immediately when the order is successfully saved. Standard-delivered settings were used for the Internet mail.
1.1.3       Print:
1.1.4       Archiving:
1.2        Add Condition Type ZEXT to Output Procedure V10000
IMG menu path:
Sales and distribution > Basic functions > Output control > Output determination > Output determination using the condition technique > Maintain output determination for sales documents > Maintain output determination procedures
The new condition type is added to the order output procedure, with the requirement of order confirmation.
1.3        Assign Procedure/Condition to Sales Order Type
IMG menu path:
Sales and distribution > Basic functions > Output control > Output determination > Output determination using the condition technique > Maintain output determination for sales documents > Assign output determination procedures > Allocate sales document header
The output is assigned to the order type used for Internet orders. The new condition type is the default output.
1.4        Assign the Output Form to the Condition Type
IMG menu path:
Sales and distribution > Basic functions > Output control > Output determination > Process output and forms > Assign forms and programs > Assign to sales document
The SAPScript form that should be used for the output is assigned. The form used for email should normally be different from the output used for printing.
1.5        Create Master Data for Condition ZEXT
Menu path:
Logistics > Sales and distribution > Master data > Output > Sales document > Create
Select condition type ZEXT:

Similar Messages

  • Configure Routine of VL02N with output type

    Hi,
    I need to create a routine for VL02N for goods issue and configure it with an output type....can anybody please provide the config steps .
    How to link the routine with the output type.....
    I have created routine in tcode VOFM under output control with application area V2 (shipping).. Next what are the steps i need to follow
    Edited by: subhajit bhadra on May 12, 2010 7:53 AM

    Hi,
    Go to NACE -> Select application V2(for delivery) -> Click on Procedures -> Select the procedure -> click on controls -> Add the output type -> Assign the routine .  I think routine '1' will serve your requirement.
    Regards
    Vinod

  • Message Output Types Available in Purchase Orders

    Hello.
    When I create new purchase orders using transaction ME21N, I click message bottom to add message output type.
    Then I can see the output types available.   My question is;
    ¿How I can add or delete message output types?  I know is thru the configuration but I can't find exactly the place.
    I really appreciate your help.
    Regards.
    Hector

    HI hector,
    got to SPRO t-code,
    click on SAP Reference IMG button
    Material Management> Purchasing>Message-->Output Control  for MM output message configuaration.
    Also, try NACE  t-code and look for Area as EF, and you can traverse through all the Conditon types..
    Hope this helps,
    Tnx
    MJ

  • Output type not proposed in Message Control when PO is created

    Hi,
    DETAILS
    I have set up the system to send a IDOC when a PO is created. I have done the following settings in the system to send the IDOC using the message control functionality in the PO creation screen.
    1). Created a new output type ZNEU which is an exact copy of NEU output type provided by the SAP system.
    2). Assigned the new output type to the output determination procedure.
    3). Enabled the new output type ZNEU for ALE distribution.
    4). Maintained the condition records in the system for the output type ZNEU such that for the P org, endor and Docmuent type combination the output shall be proposed.
    5). Maintained a partner profile( Logical System ) and assigned the output type ZNEU to this partner profile.
    6). Created a Distribution model for Sender ~ Receiver for ORDERS message type.
    PROBLEM
    When i create a PO the new output type is not getting proposed by the system. I am not sure why it is not getting porposed in the message control.
    I tried to manually enter the ZNEU output type in the system to see if the system is accepting. I am getting an error
    Partner % does not exist for partner function LS
    Any idea what i am missing? Am i missing any configuration or am i doing something wrong?
    cheers

    The output is not being proposed automatically is becuase you are missing "Condition Records" for the output type ZNEU.
    Go to NACE.
    Select EF - Purchase Order
    Select "Condition Records"
    Select ZNEU and select condition records
    Now, system will bring the combinations of access sequence. Maintain appopriate record.
    This will enable you to get the output type automatically in the purchase order.
    Regards,
    Naimesh Patel

  • How to control the output types in PO MESSAGES

    Hi Friends,
    As per the requirement I need to control the message in Standard PO(ME22N). Scenario is like below.
    1.     I am modifying some field value in PO and saving it. Then clicking on MESSAGES tab. Now I am seeing some output types are adding in EDIT mode.
    2.     Requirement is , when ever user changed one particular filed(Order acknowledgement ) and saved it, then he doesnu2019t want to see the message in EDIT mode.
    Could you please suggest me the way? Any user exit is there to reach this? Please do the needful.
    Thanks,
    Kumar

    hi,
    its may be useful for u.
    In the release strategy,if the indicator changeablity is 1 the system will not allow you to take repeat out put.
    Solution is that you have to change the release indicator changeability to 6(SPRO>MM>Purchasing>Purchase order>Define release procedure for purchase order>Release indicator>Changeability).
    Another option is that in the message output of the PO in further data change despatch time to 3 and take a repeat out put.
    Also check,
    SPRO > MM > PO > Release Procedure for PO > Release indicator > Changeability of Purchasing Document During/After Release as 2 for Release ID - G and save
    And then Create go to chage mode of PO and repeat the messages
    Regards,
    venkat m

  • How to bind complex input/output types in web service data control

    Hi,
    I have created data control using external web service for simple input & output data type and its working fine.
    But I don't know how it can be done for complex data types.
    My external Web services have complex input & output types. Such as java object which contains another java object again it contains another java object or arry or java collection etc.
    Each my service has one complex input data type and for this no user input is require so how I can do it without using any component for it.
    I want to bind my page components with this input & output type.
    What is the best approach to do this and how to bind screen component.
    Regards,
    Devang

    Hi,
    Thanks frank.
    I already check this link before posting this so if you have any other link then kindly reply.
    Regards,
    Devang

  • User exist for controlling the OutPut type in sales order

    Hi
    Is their any exist which controls the output type based on header data of the order? VA01/02.
    Best regards
    Satish Kumar K

    Hi,
    IN the VOFM routine you can use the structure KOMKBV1 which will be populated with the sales org (VKORG), division (SPART) and order type (AUART).
    Example
    SY-SUBRC = 4.
    IF KOMKBV1-VKORG = '0001' AND
        KOMKBV1-SPART = '12' AND
        KOMKBV1-AUART = 'ZXXX'.
    SET THE return code to 0 to propose the output type.
      SY-SUBRC = 0.
    ENDIF.
    Hope this helps..
    Thanks,
    Naren

  • Quotaion output type control

    Dear Experts,
      i have used Requirement routine for output type to stop determining in at the time of creation if User status in quotation header is not approved for a requirement.
    But if user takes Extras-Output-Edit and manually and key in output type it is taking it.
    Coudl you please tell me is there any config where we can control this so that manual entry also will not be allowed
    Your quick response would be of great help
    Regards
    Siva

    In Transaction Code NACE, select your output type and go to details. Then under the tab "General Data" check the field "CannotBeChanged". Then the output type will not be allowed to process manually.
    Hope this helps
    Regards
    Sai

  • Controlling time of EDI dispatch in output type for invoice

    Hi Gurus,
    I am trying to change the setting for invoice dispatch through EDI
    Currently the system is set so that invoice is sent (EDI) upon saving - and the desire it to make a manual decision when to send invoice
    I have looked at output types in SPRO - but could not figure out how to change the setting - it is not allowing me to change. Am I missing something?
    Any tips / tircks / suggestions?
    Thanks. - this is urgent as YE closing nears

    Go to V/40 .
    select the output type that you are using for Invoicing.
    double click it.
    go to Default Values tab .
           Change the Dispatch time to 1. Send with periodically scheduled job. .
    Now the invoices will be posted only when you run the program RSNAS00.
    IF this doesn't work out, Change it at COndition record level.
    Regards,
    Ajai
    Don't forget to reward points if useful.

  • Workflow triggered twice. Triggered using Message Control/Output Types

    I created an output type for VA01. After creating (then saving) SO, workflow is immediately triggered which shouldn't be the case since I have to run program 'rsnast00' to trigger workflow. So workflow is triggered twice during the process. How do i fix this?
    DATA:
    dispatch time = 'send with periodically schreduled job'
    application = 'v1'
    transmission medium = 'events'
    processing 1
      program = 'RSWEMCO1'
      form routine = 'CREATE_EVENT'

    May be the workflow is triggered in such a way that when ever out put type is created then the workflow must be triggered.
    As the purpose of the report stated by the SAP is
    Purpose
    Issues output from all applications with send times 1 and 2.
    May be the output type is created twice but the output of the report is not Duplicated. ( mentioned by SAP ) check the documentation of the report.

  • Problem in using output type for purchase order

    Hi experts,
         I am using output type for first time so may be i have done wrong configuration for po output type.The steps i have done are :-
    1) Going to  tcode NACE->Selected  the row u201CEF Purchase Orderu201D and clicked on u201CProcedures".
    2) In procedures there are 2 procedures for the application EF (Purchase Order). To proceed further, we would need to find out the procedure that is currently active.Gone to transaction SPRO. In this, navigate as Materials management -> Purchasing ->Messages -> Output control -> Message Determination Schemas ->Define Message Schema for Purchase Order
    3) Clicking on u201CAssign Schema to Purchase Orderu201D. So, the procedure RMBEF1 is active for EF (Purchase Order) . 
    4) Go back to transaction NACE. Select u2018EFu2019 and click on u201COutput typesu201D.
    5)  Let us use the output type u201CNEU name purchase orderu201D for this purpose. Double-click on NEU.
    6) Ensured  that the checkboxes u201CAccess to conditionsu201D and u201Cmultiple issuingu201D are checked and the access sequence is 0001(DocType/PurchOrg/Vendor).Only 0001 and 0002 is available in f4 help for this.
    7) Now clicked on u201CProcessing Routinesu201D on the left hand side. Ensured that there is an entry for Medium u2018Au2019 (Distribution ALE).
    8) After that going back to the main screen of NACE. Select EF (Purchase Order) and clicked on u201CCondition Recordsu201D.
    Select NEU and clicked on u201CCondition recordsu201D. The pop-up box appears that gives three radio button option :-
      1) Purchasing output determination :purchasing org / vendor for EDI
      2) Purchasing output determination :doc. type / purchasing org /vendor
      3) Purchasing output determination :document type
          but it is not having option only for purchasing organisation through which we can send idoc for changes or creation of PO in that particular pur.org now if i choose 2) i have to give doc type and purchasing org both bcoz they are mandatory fields and value for vendor.
    9)  Also i  have done the necessary ALE configuration (not covered in this document). In the partner profiles, use the message type u201CORDERSu201D and the IDOC type u201CORDERS05u201D.In the tab u201CMessage Controlu201D, used the process codes u201CME10u201D and u201CME11u201D for u201CPO Createu201D and u201CPO Changeu201D respectively.
    but the idoc is not generated many times when po is changed and when once it is generated it is giving error
    Please suggest solution.
    Thanks in advance
    nehavt

    In me22n in messages tab after looking into  processing log it is giving->No recipient found for message type ORDCHG in the
    ALE model ,next time giving error as no idoc items belonging to purchasing document found,when i changed message type to ORDCHG the  status is green in messages tab it is giving-> error occured while idoc xyz is sent and in WE02 status is red 02
    error passing data to port(could not find code page for receiving system)

  • Purchase order output type NEU is not get assigned automatically

    Dear All,
    when i am creting purchase order the output type NEU is not get assigned automatically.
    I have maintained message condn record for NEU and for specific PO doc type NB.
    same problame i was facing for the inventory docuemnts but i was resolved by running one SAP std program so please guide me if any such program is available for Purchasing documents also or any other setting i am missing to make.
    Pl suggest
    Regards,
    Vimlesh

    Hi
    Please check the following in customization.Dont check in NACE you may miss something like fine tune control
    1) Check the Message determination procedure is having the NEU output type
    2) Check the std Message determination procedure is assigned to PO
    3) Check the output type for the Access sequence, default data for transmission medium and partner function VN, Language & Form assigned to it
    4) Check the Access sequence for the condition tables
    5) Check the condition record in MN04/MN05
    6) Check the purchasing group has printer assignement
    7) Check the fine tuen control for operation 1 & 2 for message type.
    Hope your problem now solved.
    Thanks /karthik
    Edited by: Karthik on Aug 13, 2009 5:29 PM

  • 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

  • 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

  • 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

Maybe you are looking for