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.

Similar Messages

  • Output Types and output determination procedure

    Hi All,
       What is the output type and output determination procedure for the following:
    1) Credit Memo Request
    2) Credit Memo
    3) Debit Memo Request
    4) Debit Memo
    Regards
    Ashis

    Hi Ashis,
    As per the standard
    1) Credit Memo Request-
    Procedure-V10000
    Output type-BA00
    2) Credit Memo
    Procedure-V10000
    Output type-RD00
    3) Debit Memo Request
    Procedure-V10000
    Output type-RD00
    4) Debit Memo
    Procedure-V10000
    Output type-BA00
    I hope it will help you,
    Regards,
    Murali.

  • Regarding output type and idoc trigger issue

    Hi
    i need to copy pgi quantity into sales order quantity for that i write a code into user exit MV50AFZ1. code is working fine but
    output type and idoc is not trigger due to this. In this exit to update sales order quantity i used bapi *BAPI_SALESORDER_CHANGE . can anyone tell me why o/p type and idoc not trigger ,what is the reason and what is the solution for this?
    Thanks
    Dinesh

    Hi Dinesh,
    Did you activate the enhancement for user exit ?
    Did you check if the output type is configured correctly ?
    Put a debugging point and see if control is coming there.
    Regards,
    Nisha Vengal.

  • What are the output type and Tcodes?+

    What are the output type and Tcodes?

    hi,
    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
    siva

  • Wrong output type and procedure

    I have a problem when i choose the output type for my billing document it does not allow me to choose RD00 . Instead it give me a list of different output types which are listed in a different procedure under V3 application . I have defined my own procedure for RD00. How can i make sure that it chooses my procedure and output type and not someone else procedure and output type .
    THANK YOU,
    Alisha

    Hi Alisha,
    I think you have not assigned your o/p type to your O/Pprocedure.
    Please check :
    Use T/Code :NACE> Application V3-> Procedure-->Select your procedure --> choose "control" ---> Add your O/P here.
    Hope this will work for you.
    Lanka

  • How to assign output type and trigger printing in ABAP

    hi all,
    i have create invoice by using BAPI_BILLINGDOC_CREATEMULTIPLE and create header/item text with CREATE_TEXT.
    please advise how to assign the output type and trigger immediate printing after this.
    thanks.

    Hi Reetha ,
    This is a functional setting  , and should be done by some functional guy. The setting can be done by NACE.
    Just follow the path : NACE - > Select V3 for Billing - > Press Output type Button Just above - > Assign Output Type and
    then Assign Output program and form in PROCESSING ROUTINE comes into left. Set this output type for immediate print.
    Whenever You create a billing document by BAPI with this document type , the print out will be fired immediately.
    Hope it will solve your problem.
    Thanks.

  • Finding output type and form for the transaction

    hi all,
       i have a problem finding output type and form for the transaction j1iv .actually i need to find the standard output type and form name for the transaction j1iv. how can we do it.

    Hi Abinash,
         Go through the following steps.
                     1 . Go to the transaction <b>NACE.</b>
                     2. You will be able to see the <b>Application and description</b> tab over  
                         there. Select the Application for which you need the output type.
                     3. After selecting the Application..on the top you can see the tab--
                        output types...click in that..here you will be able to see all the <b>output
                        types for that application.</b>
                    4. Now select a output type ..and on the left side u will be able to see
                       the tab for processing routines...double click on it...
                    5. Here you will be able to see the standard SAP program...the form
                       routine...the form..attached to it..
                Please Reward..if helpful..
    Regards,
    Himanshu.

  • Output type and Routine

    Hi All,
    I have created one Z* output type and attached it with Z* program. and it is having routine called ENTRY_N. Now when i execute a transaction which will trigger my output type, is giving me error saying "Processing routine ENTRY_N in program Z* does not exist".
    Can anyone help.
    Regards,
    Dharmesh

    > Hi,
    >
    > in the Driver Program have a routine with name ENTRY.
    > just paste it.
    >
    >
    FORM ENTRY USING RETURN_CODE US_SCREEN.
    >
    >   CLEAR RETCODE.
    >   XSCREEN = US_SCREEN.
    <i>>   PERFORM PROCESSING.</i>
    >   IF RETCODE NE 0.
    >     RETURN_CODE = 1.
    >    ELSE.
    >     RETURN_CODE = 0.
    >   ENDIF.
    >
    > ENDFORM.
    >
    > and put the aboce code in it.
    >
    in the above code Perform processing you need include all your open_forms and write_forms, close_form. the data you are trying to pass it to script. i hope it is clear.you need to put that logic in the <b>form ENTRY</b>.
    regards
    vijay

  • Output type and application for order cancellation

    What is the output type and application for the cancellation of a sales order

    Hi,
    Try This
    cancellation of sales order:
    go to va02 enter the sales order and click enter
    then sales document->delete
    Reward if usefull

  • Need Billing doc. number based on header Output type and also billing docum

    Hi
    I have header Output type and also billing document type.
    will you please help me to get the billing document no. based on above combination, any SAP table, i was aware about the same. but i forgot the table name.
    Thanks
    Vanraj

    Hi,
    Check the Table NAST for the Billing documents associated with the OUTPUT type.
    regards,
    santosh

  • Table relation between Output Type and Spool

    Hi all,
    Is there a way to determine the table's relation between an Output Type and a Spool table for a printout.
    Thanks
    William Wilstoth

    Hi,
    See the Table TSP01 to store spool requests.
    Regards,
    Ballack.
    Reward Points if helpful.

  • Link between output type and the email id in me22n ?

    Hi,
        Can anyone plz explain the link between the output type and the email id maintained in the address data in ME22n ?
    The output type is configured fo rsending Email .Whenever i maintain the email id in the address data the outptu type gets triggered automatically but if I leave it as plank the output type does not get triggered.
    Can any one explain this dependency?
    thanks in advance
    regards,
    Ashwin

    Hi,
    It depends on the output record that you have used, what is the key?
    It is no different that printed POs where the Printer Id is not specified in the communications tab of the output record. If the systen can't find where to send the output to it will not generate the record.
    If it did generate the record without the email address, what would you expect to happen? Where could it send it?
    It is far better to get the warning message "unable to determine ......" that to simply save the PO without the email addrerss.
    So I would simply see the warning message as an indication that the email address is missing and fill it in before saving.
    Steve B

  • Difference between "output type" and "output medium" in interface

    Can comebody kindly tell me the difference between "output type" and "output medium" with respect to interface?
    Thanks,
    Max

    Hi,
    Output medium means , how you wants to see the output like
    Printout, Fax, Mail, or EDI output etc
    Output type/Condition Type means for every Application document an Output type is create for the Output Message determination, this is linked with the Condition records, Medium, Program and the Output Script or smartform.
    reward points if useful
    regards,
    ANJI

  • Creation of new output type and its access sequence

    Hello Experts,
    Issue:-How to create a new o/p type and assigning it to access sequence.I also want to know if this is purely functional requirement or does it needs ABAP involvement aswell.This will take how much time will it be more then 1 man day.
    Regards,
    Dharmesh

    Hi friend,
    You can create a new output type using the path
    IMG->SALES AND DISTRIBTION->BASIC FUNCTIONS->OUTPUT CONTROL->OUTPUT DETERMINATION->OUTPUT DETERMINATION USING CONDITION TECHNIQUE->MAINTAIN OUTPUT FOR SALES DOCUMENTS--->
    There you can define the condition types and the access sequence
    Or else directly goto the transaction code NACE where you can define all at once , even the condition records.
    please refer this link for further clarificaion
    http://www.cogentibs.com/pdf/cogsap08/OCSD.pdf
    regards,
    santosh

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

Maybe you are looking for