On base output type

Hi all,
I have configured on base output type for 5 new output types.
The  output type for one on base output type is not triggering in VF03.
I have configured in OAC0,OAC2 and OAC3. Please let me know the what could be the reason.
Thanks in advance.

Hi Praveen,
Have you created the required record in VV31?
Regards,
MT

Similar Messages

  • OUTPUT TYPE  in Nace!

    What is the meaning of output type in NACE ?

    Check out these threads on NACE
    SAP Script   -    NACE
    TNAPR vs NACE
    Condition records in NACE?
    NACE is used to create output type while creating the output type you will mention forms, and driver program.
    that will be maintained in the table TNAPR.if you create the output type using NACE then it will be automatically visible in table NAST and TNAPR.
    so check in NAST, TNAPR table
    Output types are added basically by BASIS people
    contact ur basis
    Output types are represent how you want to output information. In SAP Script context it links the print program with SAP script. Output types are part of Output determination procedure which is linked to the application (e.g. Purchsing). Output types are also linked to Access sequence, which allows you to create condition records so that output types can be processed automatically.
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/19884743b111d1896f0000e8322d00/frameset.htm
    By using NACE transaction we will assign Sap script and driver program to O/P type in an aplication for different mediums (like print/fax , mail) .
    Example :
    NACE--> Application EA --> means for PO > check O/P "NEU" (SAP standard)> Medium "Print" --> You can find the Driver program and Sap script associated to it.
    If you have your Own o/p, Script and program. Then you will assign the by using T/code NACE. Then this will appear when you want to print PO or other.
    NACE transaction
    In this transaction you can attached your Form ad your driver program .
    As you know you have got a Form say ZForm
    and a driver program say ZDriver.
    In NACE you assign an output type say ZOUT in which you attached these two so that you can identify which form is attached to which layout (Very important steps).
    **how otput typpe will help you
    say in the transaction say IW32 , if you want to hava a preview of ur output , then it will ask for ur output type . then u can select ur output type ZOUT which u had created in NACE transaction and then u will be able to view ur layout preview.
    Few tables are also important in thisaspect.
    TNAPR
    **where can we get the print program for that exising form
    Say if ur using any standar transaction then u can go to
    System --> status
    there you can find the driver of print program

  • EDI - 753Routing Request and 754 Routing Instructions transactions- what SAP ECC6 EDI output type, msg type, msg code, basis idoc is best practice to generate the idoc?

    One of our Trading Partner wishes to implement the 753 Routing Request and 754 Routing Instructions.  Can anyone give me best practice answer the following Questions?  We are on SAP ECC6 R3
    What Application? i.e. V2, V7?
    What output condition to use?  i..e. LALE, LAT2, SEDI????
    What Message type?  i.e SHPADV?
    What Basic Idoc Type? i.e SHPMNT05?
    What Message Code?  i.e. SHPM?
    What Process Code?  i.e. SHPM??
    What Function Module? i.e. IDOC_OUTPUT_SHPMNT??
    Does the SAP Transpotation Module have to be configured for this to be implemented?
    Your comments are greatly appreciated, we have until Nov 1 to be compliant?

    Good Morning,
    While I did not get any responses from my question, yes, I was able to determine what needed to be configured.   I hope the below will help you: This is for SAP ECC6
    The output application for the 753 Routing Request is "V7"
    The output type is "SEDI"
    Transmission medium is "6"
    The Basic Idoc type is "Shipmnt05"
    when setting up your Partner Profile (WE20) add:Message Partner Role "SP" with Message type "SHPADV', Message coed "753", Basic Type "SHPMNT05", Message Control add Application "V7", Message type "SEDI", Process Code "SHPM".
    also http://scn.sap.com/thread/698368 pages 14 and 15 were helpful.
    I have not configured the Inbound 754.  For now the inbound 754 Routing Instructions will be emailed to our traffic department.
    Thank you,
    Have a great day,
    jane

  • Partner profile of output type equal LS (To a delivery)

    Hi,
    I want to generate an idoc every time that a delivery is created on the basis of the condition (Shipping point=xxx,delivery type = yyy, loading point = zzz)
    So I'm trying to define a logical system (One logical system by default) as partner profile to my output type.
    So in transaction V/34, I put that the output type has to be a LS via EDI.
    And in transaction VV21 I defined that the LS 'LSYS' has to be my partner by default.
    But in my delivery. In the output type header, It's saying that my logical system 'LSYS' isn't a Partner.
    What should I do in order to have a logical system as a partner in my delivery.
    Thanks in advance

    You cannot have a LS as partner in a SD document.
    You have to define a partenr definition for each ship-to you use in WE20, and set the right output message in it.
    reward points if helpful, pls.
    regards
    Roberto

  • Output type not created for outbound delivery while using SHMNT05 idoc type

    Hi Experts,
    Please help me to solve the below issue.
    Problem:- I want to to generate an IDOC(using type SHPMNT06) once the PGI is done for an outbound delivery.
    Already it is working fine when used DESADV.DESADV01 or DESADV.DELVRY07. But now the output type is not getting created when used SHMNT.SHPMNT06. I have created a separate output type ZPJ7 just as a mirror copy of the earlier output type(ZPJ6) used for DESADV.DELVRY07.
    Question:- Is it possible to use idoc SHPMNT06 instead for DESADV01 or DELVRY07? If yes then what are steps to be followed?
    The reason why SHPMNT06 idoc is planned:- We have a scenario to send outbound delivery to 3rd party system via XI. If the outbound delivery is for National(Not for Export) and PGI is completed then send the idoc straight forward to XI otherwise DO NOT generate the idoc, but just create the delivery. Collect all the deliveries in a transport and send it in a shipment. The shipment details can be sent using SHPMNT idoc. Now from XI perspective, if we can utlitze the same SHPMNT idoc for the National delivery(1st case) then perhaps this will require less effort. Hence shipment idoc is required to be generated when the delivery is created and PGI is done.
    Also it would be great if you can advice some better way to solve above mentioned scenario.
    Many Thanks,
    Sanjay

    There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
    If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
    If thats done already then check whether you have maintianed the condition record.
    If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
    regds
    Jude

  • PO output type NEU message deactivated

    Dear All,
    The output type and messages have been configured for purchase order printout.
    When I create a PO it automatically picks up the NEU for the vendor in messages.
    But when PO is saved the output type will drops off immediately. That means I can not print . This happens only for some  purchasing groups but others it works fine.
    I have looked at transaction  MNO4, MNO5..NACE..and in config for "ASSIGNING OUT PUT DEVISES FOR PURCHASING GROUP and assigned PRINTER for that group but it still does not work . When I looked at NAST TABLE the message has been created but it has been flagged as 'DEACTIVE'.
    Could you please through light on this one...!!
    I appreciate your help and time.
    Many thanks in advance.
    cheers
    chandra

    Hi Sudhi,
    Since message output will not save, hence the print preview is not available
    in ME23N OR ME22N. The interesting point the messages will be saved for other purchasing groups. I do not understand why it works for some purchasing and not for other groups.
    I 've contacted Basis every thing looks good regarding printer setup as it works fine for other purchasing groups.
    This is very tricky ....!!! could you please find me a solution.
    I appreciate your time and inancipation  of your reply.
    cheers
    chandra

  • PO Output Type / Processing Routine Problem

    Hello everyone,
    I cannot seem to find any reference to the problem described below.
    I have encountered a problem by migrating from SAPFM06P to SAPLMEDRUCK during an ECC 5.0 upgrade, at a client where I am under contract as an ABAP Developer.
    Here is some background to the situation.  The client is currently migrating from version 4.6C to 5.0 and thought it was a good idea to upgrade their purchase order messaging  programs from the outdated SAPFM06P, which was utilized in version 3.x, to the newer program SAPLMEDRUCK implemented for use in version 4.6.
    Specifically, Message Output (ME9F) controls the output of purchase order messages in foreground, when the purchase order message is saved and the "further Data option" of the PO message contains "requested processing" equal to the value of "send with application own transaction".  This way, the actual messaging can be controlled in foreground and "breakpoints" can be set to display tables and fields.  Behind the scenes, the message status program RSNAST00 is executed by ME9F program RM06ENDR_ALV.  During this execution, it locates the message (NAST) record from the purchase order and the (TNAPR) configuration, which links the output type to the ABAP print program and SAPscript layout set.  The specific problem is: in RSNAST00, the external call perform "PERFORM (TNAPR-RONAM) in PROGRAM (TNAPR-PGNAM) USING RETURNCODE US_SCREEN IF FOUND" does not pass NAST information to the called program (TNAPR-PGNAM).  I know no NAST table information is passed because I set a break-point on the perform and single step to the print program.  Therefore, the purchase order is unknown by the print program (TNAPR-PGNAM) and results in an error and no purchase order print is provided.  Needless to say, this was tested with a new "Z" version of SAPLMEDRUCK.  So, I changed the program name (output type processing routine) in configuration to SAPLMEDRUCK, but there again the NAST information is not passed to the print program from RSNAST00.  Ironically, I reverted back to the older "z" version of SAPFM06P and NAST and TNAPR information is passed to the print program thru the external call perform quoted above.  I prefer to not modify the SAP original code for RSNAST00, which is used in many other applications.
    One other note, I had previously performed this maneuver on one different occasion with very successful results.
    Has anyone ever encountered this problem in a 5.0 environment (running Windows NT and MSSQL and SAP BASIS 6.4).
    I know this is long winded, but I wanted to explain the background of the entire situation.
    Any and all help would be appreciated.  Thanks in advance,

    Dave,
    Your entry points (like form ENTRY_NEU) should remain in your current version of SAPFM06P.  Change that form to reflect the function calls in the new SAPLMEDRUCK form (ENTRY_NEU) (calls to ME_READ_PO_FOR_PRINTING and ME_PO_PRINT.
    Look at the example below:
    Here is the form in your old (Z) version of SAPFM06P:
    FORM ENTRY_NEU USING ENT_RETCO ENT_SCREEN.
    XSCREEN = ENT_SCREEN.
    IF NAST-AENDE EQ SPACE.
       XDRUVO = '1'.
    ELSE.
       XDRUVO = '2'.
    ENDIF.
    CLEAR: XFZ, XOFFEN, XLMAHN, XLPET.
    *- Anstoß Verarbeitung -
    CLEAR ENT_RETCO.
    PERFORM LESEN USING NAST.
    MOVE RETCO TO ENT_RETCO.
    ENDFORM.
    Here is form entry_neu in your new (Z) version of SAPFM06P:
      INCLUDE FM06PE02                                                   *
    form entry_neu using ent_retco ent_screen.
      data: l_druvo like t166k-druvo,
            l_nast  like nast,
            l_from_memory,
            l_doc   type meein_purchase_doc_print.
      clear ent_retco.
      if nast-aende eq space.
        l_druvo = '1'.
      else.
        l_druvo = '2'.
      endif.
      call function 'ME_READ_PO_FOR_PRINTING'
           exporting
                ix_nast        = nast
                ix_screen      = ent_screen
           importing
                ex_retco       = ent_retco
                ex_nast        = l_nast
                doc            = l_doc
           changing
                cx_druvo       = l_druvo
                cx_from_memory = l_from_memory.
      check ent_retco eq 0.
      call function 'ME_PRINT_PO'
           exporting
                ix_nast        = l_nast
                ix_druvo       = l_druvo
                doc            = l_doc
                ix_screen      = ent_screen
                ix_from_memory = l_from_memory
                ix_toa_dara    = toa_dara
                ix_arc_params  = arc_params
                ix_fonam       = tnapr-fonam          "HW 214570
           importing
                ex_retco       = ent_retco.
    endform.
    Remember, the form should be in the Z version of SAPFM06P - not the Z version of SAPLMEDRUCK.  Make sure the configuration (TNAPR) has the SAPFM06P program name and entry point.
    It should work.  Let me know how it goes.
    Rick

  • Prevent Output type creation as Sales order save

    Hi,
    I have a requirement in which i have to chek certain conditions and on that basis i need to stop the creation of output type for Sales order. My code is written in Sales order user exit(Form SAVE_DOCUMENT). Please let me know how can i achieve this.
    The requirement routines are called before the user exit is called...so it does not seem to be possible to call routine afterwards.
    Is there a way in which we can calll the requirement routine again?? Or please suggest some other way
    Thanks
    Saurabh

    hello, friend.
    what are the conditions you are checking for?  and what would be your reasons for not creating an output type?
    not being an ABAPer, i cannot claim to be an expert.  but i think it is possible that instead of the user exit, you could program that the condition check be conducted from within the requirement itself.  the standard requirement "2" for output type BA00 checks for order confirmation, for example.  of course, the use of the requirement assumes the output type has been created, but will not be printed or be issued if the requirement conditions are not satisfied (the output indicator color will remain red).
    regards.

  • Default Output type for Invoice

    Hi Friends,
    I need to get the defualt condition record for an output type when I create an Invoice. When I go through menu GOTO -> HEADER -> OUTPUT, I have to see the defualt output type there. Somebody please help me out in this regard.
    Thanx in advace,
    Ram

    In the field for the output, check F4 help to check if any outputs are assigned to the Invoice.
    Also, check the output determination attached to the billing document.
    IMG-SD-Basis function-Output control-Output determination-Output Determination Using the Condition Technique-Maintain Output Determination for Billing Documents.
    1. Check the transaction V/25 for the Output procedure attached to the Billing document.
    2. In the output determination procedure, check the output types attached along with if any requirement.
    3. In t-code, V/40: check the condition type details.
    Regards,
    Gauravjit.
    Reward points if helpful

  • Output types

    i want to send purchase order data from sap toxi ..how to configure output types in nace transaction

    Hii Chandra
    NACE is used to create output type while creating the output type you will mention forms, and driver program.
    that will be maintained in the table TNAPR.if you create the output type using NACE then it will be automatically visible in table NAST and TNAPR.
    so check in NAST, TNAPR table
    Output types are added basically by BASIS people
    contact ur basis team
    Output types are represent how you want to output information. In SAP Script context it links the print program with SAP script. Output types are part of Output determination procedure which is linked to the application (e.g. Purchsing). Output types are also linked to Access sequence, which allows you to create condition records so that output types can be processed automatically.
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/19884743b111d1896f0000e8322d00/frameset.htm
    By using NACE transaction we will assign Sap script and driver program to O/P type in an aplication for different mediums (like print/fax , mail) .
    Example :
    NACE--> Application EA --> means for PO > check O/P "NEU" (SAP standard)> Medium "Print" --> You can find the Driver program and Sap script associated to it.
    If you have your Own o/p, Script and program. Then you will assign the by using T/code NACE. Then this will appear when you want to print PO or other.
    it is from the link
    Re: about NACE and output types
    also chk this links
    <b>SAP Script   -    NACE
    TNAPR vs NACE
    Condition records in NACE?
    Reward points if helpful
    Regards
    Naresh

  • Attaching output type automatically

    Hi all,
          i have developed an invoice form for my client.The output type for that form is maintained correctly and even condition records are maintained properly,but still the output type is not getting attached automatically.Can any one help.
    Thanks & regards,
    Anjana rao

    Hi,
    How about checking the printer assignment associated with the condition record.
    If the printer specified is not found in the system (which may have been modified by Basis team), then it may not appeared at all.
    I guess output device is not maintained in Communication strategy in condition record. Please maintain it properly.
    For your [Reference|No automatic output for invoice;.
    May it helps you.
    DS

  • WMTA output type not determining in outbound delivery

    Hi,
    Im in is-retail we are using lean WM for automatic transfer order creation, recently we made immediate delivery also, after this auto TO is not creating and  WMTA output  type also not determining in delivery.
    pls help me any body why out put type is not determining and what is the solution?
    Regards,
    MMReddy.

    There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
    If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
    If thats done already then check whether you have maintianed the condition record.
    If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
    regds
    Jude

  • PO Print Error  ---- Using output Types+

    Dear Experts
    we hv defined output type to take  PO Print. When We taking the print for service order,
    getting the dump.
    "ShrtText
        &INCLUDE INCL_INSTALLATION_ERROR
    What happened?
        The current program had to be terminated because of an
        error when installing the R/3 System.
        The program had already requested 226785696 bytes from the operating
        system with 'malloc' when the operating system reported after a
        further memory request that there was no more memory space
        available."
    Cany anyone hv idea about this.
    With Best Regards,
    Jaspal Kumar

    Hi,
    It seems it is a memory allocation problem delete old spool request using the report RSPO1041,
    if problem still persists check printer setting in t-code SPAD also have a talk with basis guys.
    Hope this solve your problem.
    Regards
    Bikas

  • Two modifiable invoice output types to be generated

    Hi experts,
    One of my customer has requested us that he need modifiable output types. the first invoice will be like a normal one which he want to keep it for company internal purpose and posting to FI will be done on that basis.
    the second invoice is based on first and is splited into two parts which he want to send to customer it can be anything llike 80-20, 90-10, 40-60, 50-50, 20-30 and many more as per user requirement.  the field on which the invoice is to be splitted is on material price. in part A  suppose it will be 80% of material price + 100% taxes and in part B it will be remaining 20% of the amount left. Everywhere in first part 100% of taxes are charged.
    can i use proforma invooice concept or any other or  a complete Z program is to be written.
    please suggest
    with regards
    SANTOSH GOSWAMI

    hi,
    i think you can achieve it
    but, its a huge task for an abaper to understand your requriment
    as per your requriment you have to align that many logics in the smart form from smart form point of view.
    then i think so that many condition types in outside condition records.
    happy new year
    please check with your abaper and confirm
    balajia

  • Output Type based on Region

    Dear All
    We are using ZINV Output type for Billing doc. And the access sequence 0001 with one table active i.e. 08 - Billing type.
    Now i want to change the title of the Invoice output from Tax Invoice to Retail Invoice based on the Region of the Delivering site and region of the customer.If the Region is same then output should be with title - Retail Invoice and if the Region is different it should be Tax Invoice. Can we maintain condition record on the basis of Region and output will come according to that.
    Kindly guide me on the same.
    Regards

    Hi
    Copy table 08 and create a new table, with fields, billing type and sales district.
    Now maintain condition records based on customer sales district. Based on that in condiiton records you can edit COVER PAGE description by double click on condiiton record.
    else second way is, hard code the text in ABAP print program of ZINV.
    try and revert.

Maybe you are looking for

  • The iPod could not be updated because the firmware file was corrupt.

    So i kept having this problem in this thread here: http://discussions.apple.com/thread.jspa?threadID=1226490&tstart=255 I decided that maybe doing a Restore on my iPod would maybe sort it out however i got that message "The iPod could not be updated

  • Best Practice for setting up an office with an extreme

    I am looking for some great info for setting up a Business Network using Comcast Business Highspeed. I rencently purchased an Airport Extreme and an Airport Express for a network extender and I am trying to understand what the optimal setup is for th

  • Connecting Ipad to a Monitor?

    Are you able to connect Ipad to a LED monitor with a DVI plug?  We have an Apple digital AV adapter which does not provide the correct fitting for a DVI.  And a DVI adapter which does not fit the Ipad2.  Any ideas?

  • Zen Micro photo.....HELP?

    <FONT color=#6666ff>ok sooo.... i am an idiot..............one night after coming home i was running to catch a ride with my friend and on the way.....my zen micro photo fell outta my pocket and into the grass..............well the next morning i obv

  • "Get info" (command I) shortcut not working

    When using Finder (MacBookPro 10.5.5), if I try to use the keyboard shortcut of command-I to get info on a file, it doesn't work. Nothing happens. If I go through the menu, then it works fine. Other shortcuts, like open (command-O) still work. I've a