Purchase order print procedure

Hi experts
i configured, purchase order form and program in NACE, after goto ME22N maintain outputtype in messages and give print preview it is working fine.
i open another purchase order, it not coming,
For every purchase order i need to maintain outputtype or not
please give the valuable suggestions.
thanks
sitaram

Hi
Addition to MxG..
For example, you want to create output type automatically in ME22N for Purchase Order Type NB.
Go to NACR.
Give you output type for example ZNEU -> Key Combination -> Order Type ( Third one ).
Inside, Create the condition records with Document Type as NB and  the medium as 1 ( Print Output ) with some partner number.

Similar Messages

  • Purchase Order  Print ..?

    Hi Experts,
    I created a po .i am trying to view the Print preview but i am not getting.
    because message is not created.  if i create a message manualley i can view print pre view.
    how to get the message automaticilley create.
    i did all the  settings in the NACE -  Condition records -  Purchasing Output  Determination :Document Type - pur doc.Type -
    Date/Time :-4  i am maintaining.
    but i am not getting the message automaticalley.
    Thanksin Advance,
    Anthyodaya.

    Hi
    Please find below the solution
    Messages can be transmitted both by the regular mail (postal service) and electronically. In the SAP System, the term "message" stands for both letters and suchlike (communications in the conventional sense) as well as other documents such as RFQs, purchase orders, contracts, and delivery schedules, all of which serve as a means of communicating information to other parties. A message control facility that depends on a number of different criteria allows you to process and transmit such messages under certain conditions, subject to predefined restrictions.
    Steps involved in configuration of Message types:  IMG u2013 MM u2013 Purchasing u2013 Messages
    Output Control:
    -     Create Condition Table (M/59) for ex. PO
    -     Create Access Sequences, copy the existing one i.e. 0001 and edit the same.
    -     Create Message types (M/34), copy the existing one i.e. NEU and edit the same then double click the O/P type assign the access sequence and save.
    -     Create Message Determination Schemas (M/36), copy the existing procedure i.e. RMBEF1 and edit the same, then go to new entries choose the condition type and save.
    -     Assign Schema to Purchase Order - Created Procedure to be assigned to PO and save.
    -     Create Partner Roles per Message Type - no input to be given.
    T.code : NACE
    Step 1 Condition records : NEU go for your possible combination and maintain records with vendor combination
    Step 2 : Condition Procedure :
    Create Procedure with different condition types
    Step 3 : Condition types
    Maintain Mail & text
    Maintain Processing routine
    Maintain Partner functions
    In Processing routine select medium , program , forms  & PDF  / Smart form.
    Thanks & Regards,
    mani

  • Purchase order print program error

    hi experts!
    am facing a problem in my purchase order print program. the problem is that when i am trying to see the print preview the following dump error is throughing, which am not able to understand.
    the P.O total amount should be change into words( like one million then thousand thirty three kuwait dinars)
    but the total amount is not converting into as mentioned, instead the dump is encountered.
    please give me solution,
    thnaks
    *DUMP*
    Runtime Errors         CONVT_NO_NUMBER                                                             
    Exception                CX_SY_CONVERSION_NO_NUMBER                                                  
    Date and Time          05.05.2008 19:04:43                                                         
    Short text                                                                               
    Unable to interpret "1760,778.71 " as a number.                                               
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "ZMM_SUBROUTINES" had to be terminated because it has                
        come across a statement that unfortunately cannot be executed.                                
    What can you do?                                                                               
    Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system                                        
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   
        at and manage termination messages, and you can also                                          
        keep them for a long time.                                                                    
    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                      
        The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not               
         caught in                                                                               
    procedure "GET_AMT_IN_WORDS" "(FORM)", nor was it propagated by a RAISING                     
         clause.                                                                               
    Since the caller of the procedure could not have anticipated that the                         
        exception would occur, the current program is terminated.                                     
        The reason for the exception is:                                                              
        The program attempted to interpret the value "1760,778.71 " as a number, but                  
        since the value contravenes the rules for correct number formats,                             
        this was not possible.                                                                        
    How to correct the error                                                                               
    Whole numbers are represented in ABAP as a sequence of numbers, possibly                      
         with an algebraic sign.                                                                      
        The following are the possibilities for the representation of floating                        
        point numbers:                                                                               
    [algebraic sign][mantissa]E[algebraic sign][exponent]                                       
          [algebraic sign][whole number part].[fraction part]                                         
        For example, -12E+34, +12E-34, 12E34, 12.34                                                   
        If the error occurred in your own ABAP program or in an SAP                                   
        program you modified, try to remove the error.                                                                               
    If the error occures in a non-modified SAP program, you may be able to                        
        find an interim solution in an SAP Note.                                                      
        If you have access to SAP Notes, carry out a search with the following                        
        keywords:                                                                               
    "CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"                                                
        "ZMM_SUBROUTINES" or "ZMM_SUBROUTINES"                                                        
        "GET_AMT_IN_WORDS"                                                                               
    If you cannot solve the problem yourself and want to send an error                            
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File                            
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                                        
           Restrict the time interval to 10 minutes before and five minutes                           
        after the short dump. Then choose "System->List->Save->Local File                             
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP                           
        program: The source code of the program                                                       
           In the editor, choose "Utilities->More                                                     
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which                       
        actions and input led to the error.                                                                               
    The exception must either be prevented, caught within proedure                                
        "GET_AMT_IN_WORDS" "(FORM)", or its possible occurrence must be declared in the               
        RAISING clause of the procedure.                                                              
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "EHPAP1"                                                                
        Network address...... "10.100.150.103"                                                        
        Operating system..... "AIX"                                                                   
        Release.............. "5.3"                                                                   
        Hardware type........ "00C3B3F04C00"                                                          
        Character length.... 16 Bits                                                                  
        Pointer length....... 64 Bits                                                                 
        Work process number.. 1                                                                       
        Shortdump setting.... "full"                                                                               
    Database server... "EHPDB"                                                                    
        Database type..... "DB6"                                                                      
        Database name..... "EHP"                                                                      
        Database user ID.. "SAPEHP"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                         
        created (date)... "Mar 19 2007 20:40:49"                                                      
        create on........ "AIX 2 5 005DD9CD4C00"                                                      
        Database version. "DB6_81 "                                                                               
    Patch level. 102                                                                               
    Patch text.. " "                                                                               
    Database............. "DB6 08.02., DB6 09."                                                 
        SAP database version. 700                                                                     
        Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 29328936                                                                               
    Heap.... 0                                                                               
    Page.... 1359872                                                                               
    MM Used. 19180992                                                                               
    MM Free. 1764848                                                                               
    User and Transaction                                                                               
    Client.............. 400                                                                      
        User................ "FADISULAIMAN"                                                           
        Language key........ "E"                                                                      
        Transaction......... "ME22N "                                                                 
        Program............. "ZMM_SUBROUTINES"                                                        
        Screen.............. "SAPLMEGUI 0014"                                                         
        Screen line......... 22                                                                       
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "ZMM_SUBROUTINES" - in                               
         "GET_AMT_IN_WORDS".                                                                               
    The main program was "RM_MEPO_GUI ".                                                                               
    In the source code you have the termination point in line 398                                 
        of the (Include) program "ZMM_SUBROUTINES".                                                   
        The termination is caused because exception "CX_SY_CONVERSION_NO_NUMBER"                      
         occurred in                                                                               
    procedure "GET_AMT_IN_WORDS" "(FORM)", but it was neither handled locally nor                 
         declared                                                                               
    in the RAISING clause of its signature.                                                                               
    The procedure is in program "ZMM_SUBROUTINES "; its source code begins in line                
        358 of the (Include program "ZMM_SUBROUTINES ".                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    368   DATA: lt_spell LIKE spell.                                                                
      369                                                                               
    370   READ TABLE in_tab WITH KEY 'CURR'.                                                        
      371   IF sy-subrc = 0.                                                                          
      372     lf_curr = in_tab-value.                                                                 
      373   ENDIF.                                                                               
    374                                                                               
    375   READ TABLE in_tab WITH KEY 'NETWR'.                                                       
      376   IF sy-subrc = 0.                                                                          
      377     lf_netpr_01 = in_tab-value.                                                             
      378     REPLACE ',' IN lf_netpr_01 WITH ' '.                                                    
      379     CONDENSE lf_netpr_01 NO-GAPS.                                                           
      380                                                                               
    381     IF lf_curr = 'KWD'.                                                                     
      382       lf_netpr_kwd = lf_netpr_01.                                                           
      383                                                                               
    384       CALL FUNCTION 'SPELL_AMOUNT'                                                          
      385         EXPORTING                                                                           
      386           amount    = lf_netpr_kwd                                                          
      387           currency  = lf_curr                                                               
      388           filler    = ''                                                                    
      389           language  = sy-langu                                                              
      390         IMPORTING                                                                           
      391           in_words  = lt_spell                                                              
      392         EXCEPTIONS                                                                          
      393           not_found = 1                                                                     
      394           too_large = 2                                                                     
      395           OTHERS    = 3.                                                                    
      396                                                                               
    397     ELSE.                                                                               
    >>>>>       lf_netpr = lf_netpr_01.                                                               
      399       CALL FUNCTION 'SPELL_AMOUNT'                                                          
      400         EXPORTING                                                                           
      401           amount    = lf_netpr                                                              
      402           currency  = lf_curr                                                               
      403           filler    = ''                                                                    
      404           language  = sy-langu                                                              
      405         IMPORTING                                                                           
      406           in_words  = lt_spell                                                              
      407         EXCEPTIONS                                                                          
      408           not_found = 1                                                                     
      409           too_large = 2                                                                     
      410           OTHERS    = 3.                                                                    
      411     ENDIF.                                                                               
    412     IF sy-subrc <> 0.                                                                       
      413 *          MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO                                
      414 *          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.                                        
      415                                                                               
    416     ELSE.                                                                               
    417                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 17                                                                               
    SY-TABIX 1                                                                               
    SY-DBCNT 18                                                                               
    SY-FDPOS 1                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY NORMAL                                                                               
    SY-UCOMM PREVOUTPUT                                                                               
    SY-TITLE Held Imp. Pur. O r - ESG 5000000021 Created by Fadi Sulaiman                             
    SY-MSGTY A                                                                               
    SY-MSGID TD                                                                               
    SY-MSGNO 426                                                                               
    SY-MSGV1 NEXTPAGE                                                                               
    SY-MSGV2 ZMEDRUCK_PO                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    SY-MODNO 0                                                                               
    SY-DATUM 20080505                                                                               
    SY-UZEIT 190441                                                                               
    SY-XPROG SAPCNVE                                                                               
    SY-XFORM CONVERSION_EXIT

    Hi Prasad,
    Check the FM's
    SPELL_AMOUNT --> for display in millions
    HR_IN_CHG_INR_WRDS --> for display in lakhs and crores

  • Purchase order print ID for  condition lines

    How to add / remove  condition types ie. freight rates, handling charges in purchase order print out ?.
    i want the values of these condition types to be /not to be in the purchase order print out.
    even when i m maintaining these values in P.0 conditions.

    hi
    in pricing procedure m/08 u can the condition types as print relevant.
    maintain it and check in print preview
    If this Hint had helped please reward points
    gibi

  • Purchase Order Print Report Compilation Error

    Hi,
    While compiling the report in Reports Builder Purchase Order Print Report , we get the following error:
    identifier GET_PRECISION must be declared.
    Where as this is a seeded function inbuild in the Program Units.
    Also while compiling on server we get the error.
    Cannot convert rdf to rep.
    Thanks,
    Angelica.

    Couldn't find how to copy the PO layout over using copy express.
    I did compare the RDOC fields for POR20002 in both databases and they are Identical. 
    In Crystal Reports, I did a formula search for N_Decimal_Places and it found nothing.  Then I did a search for 'length' in all formulas and it finds length in N_Decimal_Places.  When I double click on N_Decimal_Places it clears the screen and never shows the formula. This happens in both layouts for my test database and SBODemoUS.
    Again, SBODemoUS works correctly and AAA_TEST give the error.

  • Excise duty condition type and Purchase Order Print Issue

    Dear Friends,
    We have a issue related to Purchase order print out.
    We are maintaining TAXINN.
    We have implemented CIN and we are maintaining Excise Conditions i.e. Basic Excise in JMOP
    In FV11 we are maintaining values for JMOP with plant and material Group combination.
    In Purchase Order Tax calculation is happening correctly.
    But issue is to find the value of taxes for Purchase Order Print.
    We are using function module CALCULATE_TAX_FROM_NET_AMOUNT
    and passing values of Company Code, Country, Currency, and Base amount to get the entries in condition types.
    But we are not getting any entry even after passing the values.
    How we can get these values in JMOP.
    Regards
    Kant

    Why do you want to calculate the taxes during the PO Print when you are getting correct values in PO itself?
    Modify your print program with pulling values directly from EKPO/ EKKO Tables and display it to Spool.
    check with ur ABAP Person

  • I want to change Purchase Order Print

    I want to change Purchase Order Print. I want to add the name who has done last change in Purchase Order. Please help.

    You no need to add the changes, It can be shown in Environment menu. If u want to see the person who changed the PO in ur Print, ABAP work will be required..
    By the way what is the business requirement for this. B'cas PO is meant for vendor, Why do u want to print, whoever did the changes..This thing you can see from SAP itself at anytime.
    Cheers!
    ***Reward If useful (RIU)

  • Purchase Order release procedure

    Hi All,
    My client is having following requirement for Purchase Order release procedure.
    Plant 1                    -    1 Release code (Manager)
    Plant 2             -    2 Release Codes (Manager, Sr Manager)      
    Plant 3             -    3 Release Codes (Purchase Officer, Manager, Sr Manager)     
    All plants are assigned to one company code. Please advise me how I can map above requirement in sap.
    Thanks & Regards,
    Nagi

    Hi Nagi,
    In PO Realease startegy configuration, you need to decide and select the Release objects for which the system should trigger release for the document. you should work with Characteristics for each object (Your requirement is for 3plants) so in one of your characteristic WERKS should be your field along with other characteristics based on your requirements such as Total Net Value, Doc type etc.
    Create Characteristics in CT04 for the class type 032 and proceed maintaining the release Group and Release codes as per your requirement.
    Refer the following thread and revert if any confusions...
    http://**********************/2008/11/release-procedure-release-strategy-main.html
    Regards
    Shiva

  • SmartForms: Purchase order Print prog and SLIN

    Hi all,
    I am on 4.7 and Purchase Order Print Prog name is /SMB10/FM06P. When i am doing SLINE Check on this Prog. I am getting the following Message.
          Program:  /SMB10/FM06P  Row:      1
    The namespace of program /SMB10/FM06P has the setting "C" and cannot be tested.
    A possible cause for this is that an SAP program is being checked in a customer
    system.
    Note, the following rule applies after a change in the source code:
    For testing the namespace setting is ignored for one week
    (The message cannot be hidden using pseudo-comment "#EC .., or by using SET
    EXTENDED CHECK OFF/ON)
    Is any one have idea about this?
    Thanks in advnace.

    Thanks for your Reply,
    When i am doing Syntax check in SE38, I am getting the below error message.
    <b>"The Program "/SMB10/FM06P" is not Unicode-compatible, according to its program attributes."</b>
    I have found the OSS Note No: 751007
    Solution
    Copy the program into your own namespace (e.g "ZZsmbfm06p"), maintain the program attribute to make sure the flag "Unicode checks active" is selected. Then maintain the customizing for output control again.
    <b><u>
    GOD BLESS SAP, SAP asking to Create Custom Object.</u></b>
    Thanks
    Message was edited by: Vipin Nagpal
    Message was edited by: Vipin Nagpal

  • Purchase order print priview and spool print output are different.

    Hi Friends,
    there is problem with purchase order print priview and spool print output are different.
    mean : in me23n .. for a perticular po .. in po priview the TAX VALUES value is 120 coming..
    when i am giving print with spool.. the amount value is showing  TAX VALUE
    is 443..why it is showing wrong..
    this is for perticular output type.
    why TAX VALUES are showing different in print view and
    spool print.
    help me.
    regards,

    Hi Neil,
    thanks for your reply.
    but the valiadtions are happening in standard functional module PRICING.
    it is realted script(medruck)...but there is no code point for spool or printer side..
    and the issue is realted one PO OUTPUT TYPE..
    it is sap standard debugging... when i am debugging the functional module PRICING.
    the values are coming dynammically.
    help me.
    regards,

  • Purchase order Print-out in ME22N

    Hellow sir,
    I am getting an error while taking purchase order print-out in ME22N,system giving the error message Express document "Update was terminated"received from author "Abhishek".Please help me out
    Regards,
    Kirti

    Hi Kirti,
    Notes are seen on service.sap.com not R/3.  Please go to service.sap.com ->in SAP Support Portal click on link SAP Note search then in front of number, give the note number and  click on ">>" button.
    In R/3 you can see whether these notes are implement or not. Basis people see it in transaction SNOTE and the in note browser, you give note number and press F8. If this note is avl, it means it is already implemented.
    I still suggest to change config to standard to suspect your programs too. Notes would help to solve problem in standard objects only.
    - Sanjeev

  • Changed Purchase Order Print output

    Hi Gurus,
    what output type should i choose to get revised purchase order print output with only changes
    Regards
    Vivek

    Hi Vivek,
    You can very well use the same o/p type which is used for creation.
    The driver program need to be modified to print only the changes required.
    Contact ur ABAPer for further assistance.
    Regards
    Ramesh Ch

  • Purchase Order Pricing Procedure

    Can someone send me the path to maintain and enhance the purchase order pricing procedure.
    Will reward
    Thanks,
    Richard

    Spro -> Materials Management - >Purchasing -> Conditions -> Pricing conditions
    Thanks,
    MV

  • TWO CURRENCIES IN ONE Purchase Orders Release Procedure.

    TWO CURRENCIES IN ONE Purchase Orders Release Procedure.
    Please provide a solution if a release strategy is maintained for two currencies like USD and SGD for more clarification please Read the below Requirement.
    Requirement for Singapore:
    u2022          COMPANY Asia (Singapore) wants its own Purchase order release strategy is based on their local currency (SGD)
    u2022          Whereas COMPANY is using only USD as currency in Purchase order release strategy.
    u2022          Standard SAP works based on Character currency which is defining in Class of Purchase release strategy and converts with Local currency to compare with Character Currency.
    Required analysis:
    u2022          The value assigned in classification is based on Conversion from SGD to USD, Due to Exchange rate fluctuations the assigned value is differ by large amounts and hence system is either determining the higher release strategy or Lower release strategy
    u2022          But during Release Strategy Configuration the Net order Value is assigned as 3600 USD considering the Exchange as 1.388889.
    u2022          As per the exchange rate in the purchase order 1.3799 the system is calculation the PO Net order Value but the Strategy is Determined based on the value maintained according to exchange Rate 1.388889
    In the Purchase Order the system is 
    Ex:  Total Purchase Order Value is 4765.21 SGD and 3453.30 in USD
          For Level 1 the value limit is 5000 SGD if it exceeds 5000 SGD it has to go to his manager (Level 2) Exchange rate on 01.04.2008 is 1.3799.
    System Considerations:
    Possible Solution:
    1.        Create a new Class with Characteristic with Currency Value SGD System should determine the class based on the combination of Plant 6000 and Document Category F Purchase Order.
    2.        By using Enhancement spot with Function Module ME_RELEASE_STRATEGIE/ ME_RELEASE_STRATEGIE_EKKO
    Logic:
    1.        System will determine the class PUR_RELEASE from table T16FG if the system finds Plant as 6000 and Document Category as F Then replace PUR_RELEASE with New class as ZPUR _6000.
    2.        Maintain Z table for the combination of Plant and Class for future requirement
    Edited by: Mohammad Irfan on Jun 8, 2009 10:41 AM

    Hi Mohamed,
      You can create separate characteristics far all check points and assign those to class.
    Regards,
    Prasath

  • ME9F Purchase Order Printing.

    If authrorization of T-code ME9F is given to any SAP user ID then in t-code ME23N if we click on Print Preview system shows the Purchase order print preview, Printing options are available in this print preview.
    How I can restrict that user id to take printout of the purchase order. I want to give only print preview of the Purchase order.

    Hi Shekar ,
    Use the time spot as 3 in condition records ( MN04 ) so that printing can only happen using ME9F.
    Then in ME23N only preview can be seen but cannot be printed.
    Regards
    Ramesh Ch

Maybe you are looking for