Defaulting the Out put type in out put

Hi All,
I have an issue in output- I am having two out put types say AA00 & BB00 for say order confirmation and order acknowledgement. When I am issuing out put for print I am getting both the condition option but not able to select? I want to make the one of the condition as default condition, How can I do it?
Your help will be rewarded.
Manoj

Hey,
Check the Tcode V/43 where you can maintain the output Determination procedure and the default output type.
Regards,
Ajai.
Don't forget to reward points if useful.

Similar Messages

  • Is there a way to Default the Contractual User Type in Licence tab in SU01.

    Hi Guys,
    Is there any way to Default the Contractual User Type in Licence tab while creating users in SU01 to a specific value. Any help would be appreciated.
    Thanks,
    Naveen

    Naveen, though you marked the question as answered, there is another alternative (needs change mgmt involved)-
    1.Go to the field where you want the parameter ID to appear.
    2.Go to the technical help for the field.  In this case the Contractual User Type field.
    3.Double click on the Screen data screen number (0112).
    4.Click on the Element list tab and look for the screen field (from previous page).  It is important that you find the entry with a type of I/0 not Text (US930-USERTYP).
    5.When you find the entry click the special attributes tab.  There are two columns on the right hand side ‘GET Parameter’ and Parameter.  The GET column needs to be selected for the parameter ID to be active.
    6.Note if you change a field it is important to activate the change in addition to saving or the change will not take effect.
    7.Probably you would like to make this change in the development system and move transport to other systems.
    After this you have to set this parameter in your user master to the required value.

  • Default the storage unit type

    Hi Experts,
    Is it possible default the storage unit type in LT04 ?
    if yes, kindly advise how to configure in SPRO?
    Thanks.
    Regards,
    Steven

    Hi
    Not sure if you use HU and packing material. You can try through this config
    IMG-Logistics General - Handling Unit management - Basics - Warehouse Management  - Assign Storage Unit type to Packing Material Type.
    For every packing material you can maintain a default storage unit type
    Regards
    Jayaram

  • Can the stroke on type knock out specific layers but not others?

    I'm mainly an Id and Photshop person but I've been asked to do some maps for a publication we're putting together.
    I'm probably being fussy but I've come up against a question that I'm just unable to resolve with the knowledge I have. Searching on forums hasn't helped either.
    Anyway, this is what I've got:
    The grey background, type, stroke on type and the islands are all on different layers.
    What I want to end up with is the stroke on the type knocking out the black outline stroke on the islands but being invisible over the grey background, like so:
    Does anyone have any ideas?

    You can get that if you're willing to work with a duplicate of the country shapes.
    See:
    http://www.m-server.de/m_g/Knockout-cs5.ai
    All relevant appearances are applied at layer level. Target the layer in the layer panel and see appearance panel for the options.

  • F110 Default the Exchange rate Type

    Hi Experts,
    I have requirement for Setting up the Exchange rate type (Kurst) to defualt even on F110 transaction ( Tab :Paramter)
    (Even if user change it should not to be allowed)
    Can you please let me know if any Exit/Badi/ EnahancementSpot/ BTE which can fullfill my requirement.
    Thanks

    Hello 
    did you get answer ?
    I have problem same as you.

  • Application type  & out put type

    Hi ,
    For MI21 (Physical Inventory Documents) reprt what is the
    1)application type
    2)out put type
    Thanks & Regards
    Krishna

    Here are the standard ones for printing
    Output Types Mode (1= Printing)  Application
    ET01   1                                     ME
    J1IB    1                                      ME
    J1IF     1     ME
    WA01   1     ME
    WA02   1     ME
    WA03   1     ME
    WAE1   1     ME
    WAE2   1     ME
    WAE3   1     ME
    WE01   1     ME
    WE02   1     ME
    WE03   1     ME
    WEE1   1     ME
    WEE2   1     ME
    WEE3   1     ME
    WEK1   1     ME
    WF01   1     ME
    WF02   1     ME
    WLB1   1     ME
    WLB2   1     ME
    WLB3   1     ME
    Hope That Helps
    Anirban M.

  • Package with table data type as out parameter.

    Hi there, I managed to compile the package without error but when I am trying to test this package and
    I am keep facing this error message. 
    Am I using correctly for the table data type as out parameter.  I have no idea what is wrong with the package to fix. 
    Pls. help and advise me.  Thanks.
    Error starting at line 1 in command:
    DECLARE
    p_stmodel VARCHAR2(40):=null;
    p_item_number VARCHAR(40):='9BX158-300';
    p_item_id NUMBER:=0;
    l_attribute_out test_common_api.l_item_attr_tab:=test_common_api.l_item_attr_tab();
    BEGIN
    test_common_api.test_attribute(p_stmodel,p_item_number,p_item_id,l_attribute_out);
    END;
    Error report:
    ORA-06550: line 8, column 18:
    PLS-00302: component 'TEST_ATTRIBUTE' must be declared
    ORA-06550: line 8, column 2:
    PL/SQL: Statement ignored
    06550. 00000 -  "line %s, column %s:\n%s"
    *Cause:    Usually a PL/SQL compilation error.
    *Action:
    ---------Package.
    CREATE OR REPLACE PACKAGE test_common_api
    AS
    TYPE item_attr_rec IS RECORD (CONFIGURATION VARCHAR2(20),
                                   PRODUCTTYPE VARCHAR2(30),
                                   INTERNALPRODUCTNAME VARCHAR2(20),
                                   NUMBEROFHEADS VARCHAR2(2),
                                   NUMBEROFDISCS VARCHAR2(2),
                                   GENERATION  VARCHAR2(10),
                                   FACTORYAPPLICATION VARCHAR2(150),
                                   PRODUCTFAMILY  VARCHAR2(60),
                                   FORMFACTOR VARCHAR2(10),
                                   FORMATTEDCAPACITY NUMBER,
                                   FORMATTEDCAPACITY_UOM VARCHAR2(20),
                                   INTERFACE  VARCHAR2(30),
                                   SPINDLESPEEDRPM  NUMBER,
                                   PRODUCTCACHE VARCHAR2(10),
                                   WARRANTYMONTHS   VARCHAR2(2),
                                   PHYSICAL_SECTOR_SIZE  NUMBER,
                                   MODELHEIGHT  VARCHAR2(10),
                                   ENCRYPTION_TYPE VARCHAR2(40));
    TYPE l_item_attr_tab IS TABLE OF item_attr_rec;
    END test_common_api;
    show errors
    create or replace package body test_common_api
    AS
    PROCEDURE test_attribute (p_stmodel IN VARCHAR2,
                               p_item_number IN VARCHAR2,
                               p_item_id IN NUMBER,
                               l_item_attr_list OUT l_item_attr_tab)
    IS
    l_stmodel st.stmodelnumber%TYPE;
    l_market_segment VARCHAR2(10) ;
    l_sub_market_segment VARCHAR2(10) ;
    l_app_segment VARCHAR2(10);
    l_market_name VARCHAR2(40) ;
    l_ccitem seaeng_ccitemnumber.ccitemnumber%TYPE;
    l_query_item  VARCHAR2(1000);
    l_query_model VARCHAR2(1000);
    l_where VARCHAR2(1000);
    l_bind_var1      VARCHAR2(40);
    l_bind_var2      VARCHAR2(40);
    l_sql            NUMBER:=0;
    l_config VARCHAR2(40):=null;
    BEGIN
       IF p_stmodel is not null THEN
           l_where :='WHERE sc.ccmodel = sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber
                      AND sc.pricingdescriptor=''MODEL''
                      AND sc.ccdashnumber =''000''
                      AND sp.detailedproductname=''GENERIC''
                      AND st.stmodelnumber= :1';
                  IF p_item_number is null AND p_item_id is null THEN
                      l_config :='null';
                  ELSE
                      l_config :='sc.configuration';
                  END IF;
            l_bind_var1 :=p_stmodel;
            l_sql :=1;
        ELSE
            IF p_item_id is null and p_item_number is not null THEN
                l_where := 'WHERE sc.ccmodel = sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber and sc.ccitemnumber = :1';  
                l_bind_var1 :=p_item_number;
                l_sql:=2;
            ELSIF p_item_id is NOT null and p_item_number is null THEN
                l_where := 'WHERE sc.ccmodel= sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber and sc.ccitemnumber in ( select msi.segment1
                            from mtl_system_items msi
                            where msi.inventory_item_id = :1)';
                l_bind_var1 := p_item_id;
                l_sql:=2;
            ELSIF p_item_id is not null and p_item_number is not null THEN
                l_where :='WHERE sc.ccmodel = sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber and sc.ccitemnumber in (select msi.segment1
                           from mtl_system_items msi
                           where msi.inventory_item_id = :1
                           AND msi.segment1=:2)';
                l_sql:=3;
                l_bind_var1 := p_item_id ;
                l_bind_var2 :=p_item_number;
            END IF;
        END IF;
    l_query_item :='SELECT sc.configuration,st.producttype, sp.internalproductname, sp.numberofheads , sp.numberofdiscs,
      sp.generation,sp.factoryapplication, st.productfamily,st.formfactor , st.formattedcapacity , st.formattedcapacity_uom,
      st.interface,st.spindlespeedrpm,st.productcache,st.warrantymonths, st.physical_sector_size, st.modelheight, st.encryption_type
       FROM  pm sp , st st, seaeng_ccitemnumber sc ';
    l_query_model :='SELECT '|| l_config|| ' , st.producttype, null,null , null, null, sp.factoryapplication, null,st.formfactor, st.formattedcapacity,
      st.formattedcapacity_uom,st.interface , st.spindlespeedrpm, st.productcache, st.warrantymonths,st.physical_sector_size, st.modelheight,
      st.encryption_type
      FROM  pm sp , st st, seaeng_ccitemnumber sc ';
       IF l_sql = 1 THEN
          EXECUTE IMMEDIATE  l_query_model ||l_where
                             BULK COLLECT INTO l_item_attr_list
                             USING l_bind_var1 ;
                               dbms_output.put_line(l_query_model||l_where);
        ELSIF
             l_sql =2 THEN
               EXECUTE IMMEDIATE l_query_item || l_where
                                 BULK COLLECT INTO l_item_attr_list
                                 using l_bind_var1;
                                 dbms_output.put_line(l_query_item||l_where);
        ELSE
           EXECUTE IMMEDIATE  l_query_item ||l_where
                             BULK COLLECT INTO l_item_attr_list
                             USING l_bind_var1, l_bind_var2 ; 
                               dbms_output.put_line(l_query_item||l_where);
        END IF;
    END test_attribute;
    END test_common_api;
    show errors

    I think you forget to declare "PROCEDURE test_attribute" procedure in your package definition. like:
    CREATE OR REPLACE PACKAGE test_common_api
    AS
    TYPE item_attr_rec IS RECORD (CONFIGURATION VARCHAR2(20),
                                   PRODUCTTYPE VARCHAR2(30),
                                   INTERNALPRODUCTNAME VARCHAR2(20),
                                   NUMBEROFHEADS VARCHAR2(2),
                                   NUMBEROFDISCS VARCHAR2(2),
                                   GENERATION  VARCHAR2(10),
                                   FACTORYAPPLICATION VARCHAR2(150),
                                   PRODUCTFAMILY  VARCHAR2(60),
                                   FORMFACTOR VARCHAR2(10),
                                   FORMATTEDCAPACITY NUMBER,
                                   FORMATTEDCAPACITY_UOM VARCHAR2(20),
                                   INTERFACE  VARCHAR2(30),
                                   SPINDLESPEEDRPM  NUMBER,
                                   PRODUCTCACHE VARCHAR2(10),
                                   WARRANTYMONTHS   VARCHAR2(2),
                                   PHYSICAL_SECTOR_SIZE  NUMBER,
                                   MODELHEIGHT  VARCHAR2(10),
                                   ENCRYPTION_TYPE VARCHAR2(40));
    PROCEDURE test_attribute (p_stmodel IN VARCHAR2,
                               p_item_number IN VARCHAR2,
                               p_item_id IN NUMBER,
                               l_item_attr_list OUT l_item_attr_tab);
    TYPE l_item_attr_tab IS TABLE OF item_attr_rec;
    END test_common_api;
    show errors
    create or replace package body test_common_api
    AS
    PROCEDURE test_attribute (p_stmodel IN VARCHAR2,
                               p_item_number IN VARCHAR2,
                               p_item_id IN NUMBER,
                               l_item_attr_list OUT l_item_attr_tab)
    IS
    l_stmodel st.stmodelnumber%TYPE;
    l_market_segment VARCHAR2(10) ;
    l_sub_market_segment VARCHAR2(10) ;
    l_app_segment VARCHAR2(10);
    l_market_name VARCHAR2(40) ;
    l_ccitem seaeng_ccitemnumber.ccitemnumber%TYPE;
    l_query_item  VARCHAR2(1000);
    l_query_model VARCHAR2(1000);
    l_where VARCHAR2(1000);
    l_bind_var1      VARCHAR2(40);
    l_bind_var2      VARCHAR2(40);
    l_sql            NUMBER:=0;
    l_config VARCHAR2(40):=null;
    BEGIN
       IF p_stmodel is not null THEN
           l_where :='WHERE sc.ccmodel = sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber
                      AND sc.pricingdescriptor=''MODEL''
                      AND sc.ccdashnumber =''000''
                      AND sp.detailedproductname=''GENERIC''
                      AND st.stmodelnumber= :1';
                  IF p_item_number is null AND p_item_id is null THEN
                      l_config :='null';
                  ELSE
                      l_config :='sc.configuration';
                  END IF;
            l_bind_var1 :=p_stmodel;
            l_sql :=1;
        ELSE
            IF p_item_id is null and p_item_number is not null THEN
                l_where := 'WHERE sc.ccmodel = sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber and sc.ccitemnumber = :1';  
                l_bind_var1 :=p_item_number;
                l_sql:=2;
            ELSIF p_item_id is NOT null and p_item_number is null THEN
                l_where := 'WHERE sc.ccmodel= sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber and sc.ccitemnumber in ( select msi.segment1
                            from mtl_system_items msi
                            where msi.inventory_item_id = :1)';
                l_bind_var1 := p_item_id;
                l_sql:=2;
            ELSIF p_item_id is not null and p_item_number is not null THEN
                l_where :='WHERE sc.ccmodel = sp.productmodelnumber AND sp.stmodelnumber = st.stmodelnumber and sc.ccitemnumber in (select msi.segment1
                           from mtl_system_items msi
                           where msi.inventory_item_id = :1
                           AND msi.segment1=:2)';
                l_sql:=3;
                l_bind_var1 := p_item_id ;
                l_bind_var2 :=p_item_number;
            END IF;
        END IF;
    l_query_item :='SELECT sc.configuration,st.producttype, sp.internalproductname, sp.numberofheads , sp.numberofdiscs,
      sp.generation,sp.factoryapplication, st.productfamily,st.formfactor , st.formattedcapacity , st.formattedcapacity_uom,
      st.interface,st.spindlespeedrpm,st.productcache,st.warrantymonths, st.physical_sector_size, st.modelheight, st.encryption_type
       FROM  pm sp , st st, seaeng_ccitemnumber sc ';
    l_query_model :='SELECT '|| l_config|| ' , st.producttype, null,null , null, null, sp.factoryapplication, null,st.formfactor, st.formattedcapacity,
      st.formattedcapacity_uom,st.interface , st.spindlespeedrpm, st.productcache, st.warrantymonths,st.physical_sector_size, st.modelheight,
      st.encryption_type
      FROM  pm sp , st st, seaeng_ccitemnumber sc ';
       IF l_sql = 1 THEN
          EXECUTE IMMEDIATE  l_query_model ||l_where
                             BULK COLLECT INTO l_item_attr_list
                             USING l_bind_var1 ;
                               dbms_output.put_line(l_query_model||l_where);
        ELSIF
             l_sql =2 THEN
               EXECUTE IMMEDIATE l_query_item || l_where
                                 BULK COLLECT INTO l_item_attr_list
                                 using l_bind_var1;
                                 dbms_output.put_line(l_query_item||l_where);
        ELSE
           EXECUTE IMMEDIATE  l_query_item ||l_where
                             BULK COLLECT INTO l_item_attr_list
                             USING l_bind_var1, l_bind_var2 ; 
                               dbms_output.put_line(l_query_item||l_where);
        END IF;
    END test_attribute;
    END test_common_api;
    show errors

  • RMI tunneling: JNDI lookup fails with : Disconnected: Type code out of range, is -29

    9iAS Release 2
    When trying to tunnel through Apache to the OC4J_home instance using ...
    http:ormi://<host>:<HTTPport>/<application> <admin><password>
    and then looking up a JNDI name ...
    TopicConnectionFactory connectionFactory =
    (TopicConnectionFactory)new InitialContext(p).lookup("jms/myTopicConnectionFactory");
    I get a NamingException thrown, with the message: Disconnected: Type code out of range, is -29.
    The jms.xml file is correct. It works against a standalone OC4J instance (therefore no tunneling) ...
    ormi://<host>:23791/<application> <admin><password>
    I'm connecting from a standalone client and using the RMIInitialContextFactory, the tunneling is working (changing oc4j username/password gets a SecurityException). What's missing? Do you have to change the jndi name when tunneling? What does -29 mean in english?

    Tunneling through the Apache HTTP server to an OC4J instance from remote standalone clients works on Linux installations of 9iAS but not on NT installations, failing with a 'Type Code out of range, is -29' error, JVM versions on client and server are the same. Also works against a standalone version of oc4j on NT, what's happening?

  • How to pre-define the "save as type" using fileDialog or fileChooser?

    Hello everyone,
    I have a fileDialog. I now want to save a file by specified extensions i.e. docs,gif,etc. How can I do that? by default, the "save as type" box is "all files".
    thanks a lot
    SQ

    if you are using the java.awt.FileDialog,
    call its .setFilenameFilter() method, passing to it
    an instance of java.io.FilenameFilter, in which you override the
    .accept(File dir, String name) method
    to specify the file extensions you'd like. You'll have to do some pattern matching of the extended characters (*.___)...
    if you're using JFileChooser, do similar calling
    .setFileFilter(javax.swing.filechooser.FileFilter) setting an instance of FileFilter that overrides its
    .accept(File file) method.
    Hope that helps.

  • Invoice out put types

    Hi All
    We have TWO invoice out put types  ( ZLD1,& ZLD2) for invoice printing.
    when we use VF03 ------> issue output
    it is default showing only ZLD1, Manualy we have to Add ZLD2.
    is possible to set ZLD2 also in autoamticaly....
    RGds
    Pramod

    VF02, enter the invoice number, press enter
    press the "I" button
    If I double click on the first output type RD00, I will have this
    If I click on the ACCESS 06 (output found)
    I have the exact line of the VV31 trans 
    Fred

  • GR Print Out Put Types

    Hi
    Wats the diff between invidual slip and collective slip in MIGO screen
    Wats the std out put type for GR print out in mb90
    Vijay

    hi
    individual means single item per printout
    collective means all items in GR
    o   Individual slip (version 1)
         In this case, one GR/GI slip is printed out for each item.
    o   Individual slip with inspection text (version 2)
         In this case, one GR/GI slip is printed out for each item. In
         addition, a quality inspection text is printed if there is one in
         the material master record.
    o   Collective slip (version 3)
         In this case, a collective slip including all the items in a
         document is printed.
    WE01, WE02 and WE03,  are std output types
    regards
    kunal
    Edited by: kunal ingale on Dec 27, 2008 9:50 AM

  • How to generate idoc  PODRCH02 using out put type

    Hi All,
    I need to generate outbound idoc PORDCH02 and message type PORDCH using out put types (messages).But i unable to generated this idoc using message type. System is giving error as  *No recipient found for message type PORDCH in the ALE model*
    To do this , i have done the following steps.
    1. In BD64 i have configure the business object BUS2012, using add bapi. ( In cust.distn model it doesn't allowing the message type. so i have given BAPI )
    2. In partner profile (WE20), for sending logical sytems
    i have configure the message type in outbound parametes.
    3. In NACE for out put type NEU  i have given medium as Distribution (ALE),  Partner function as LS     
    Could you please help me out , what are the necessary steps i need to take care and what are the steps i missed out.
    Thanks and regards
    Praveen

    In distribution model, you have to configure both the sending system and receiving system. The Tcode of Distribution model is BD64.

  • Out put types not appearing for HUs

    Hello All,
    Can anyone help me in explaining how to make use of the button "F6PrHU" in LM18 screen for RF. I tried to use it to print my HUs, but I get message as "Print option is not activated".
    Moreover none of the out put types defined in print procedure in SPRO are getting populated in the out put screen of HU. When I see extras->output for any HU I see the section blank with no output types.
    Please provide your valuables inputs.
    Thanks,
    Amit G

    Hello,
    it can be activated in user-exit. For details refer to SAP help [Printing Using the User Exit  |http://help.sap.com/saphelp_erp60_sp/helpdata/en/7b/5371386afa2045e10000009b38f889/content.htm]
    Andrzej

  • Regarding out put type for ME22N

    Hi All,
    I have configured out put type in SPRO for Purchase Order. Like
    SPRO->Material Management->Purchasing->Messages->Output Control->Message Types->Define Message type for Purchase Order->Maintain Message types for PO's. Now I want to use this out put type to configure at ME22N to print smart form,But here, While selecting Output type in ME22N,It is saying as out put type is not defined. So how to get this here in ME22N.
    Thanks in advance

    Hi,
    It seems that you have not assigned o/p type to your procedure. Go to NACE (common transaction to maintain o/p s), select EF , go to procedures , doubleclick on the procedure and check if you message type is assigned . Please maintain your o/p type if not maintained.
    To check the procedure used for PO ,  use the path,
    SPRO-> Materials Management-> Purchasing -> Messages -> output control -> Message Determination Schema -> DEFINE MESSAGE SCHEMA FOR po.
    Please also maintain other settings like condition record (with communication method )for o/p type in NACE.
    Regards

  • Configure OUT PUT type for delivery to EDI

    HI
    how to set up the out put type as EDI  for Out Bound delivery .
    so when ever a delivery is processed via VL71 there has to be an idoc to be generated in the system

    hi
    check with the following steps...
    1) <b>Go to SPRO ,</b>
    2) <b>copy the existing output type,</b>
    3) <b>give your own name to outpur type</b>
    4) <b>associate the partner function like a print o/p edi o/p ale o/p</b>
    5) <b>then associate ur program with the o/p type.</b>
    Hope this solves ur problem....
    <b>do reward if useful....</b>
    regards
    dinesh

Maybe you are looking for