Default two ouput types while printing Purchase order

Hi,
In MN04 - Create Condition Records I am not able to enter two output types - print and email for the same vendor in Purchasing Output Determination: Doc.Type/Purch.Org/Vendor.
I can default one output type and add the other one when doing the purchase order. But
is there a way to default two purchase output types?
Sincerely,
Ketan

Hi Jurgen
I had deselected the 'Exclusive indicator' but still it does not work. The PO message screen shows up NEU but does not show NEU2. Though in the outout determination analysis for both the output types: NEU & NEU2, it shows output found.
My configuration is as follows:
Procedure RMBEF1:
10     1     NEU
20     1     MAHN
30     0     NEU2
Access Sequence (Exclusive Indicator not selected)
5     27     Purchasing Output Determination: Purch. Org./Vendor for EDI
11     25     Purchasing Output Determination: Doc.Type/Purch.Org/Vendor
20     26     Purchasing Output Determination: Document Type
Both NEU & NEU2 is assigned to Access 11: Doc.Type/Purch.Org/Vendor
Hi Kiran,
SAP would not allow me to enter the same output type 'NEU' twice in the the same access "Purchasing Output Determination: Doc.Type/Purch.Org/Vendor"
Sincerely,
Ketan

Similar Messages

Restricting ouput type for a purchase order

Hi,
I don't want an ouput type to be selected for a purchase order ( specific to vendor and plant combination ) by default.
But, in my case a default message 'print output' is displayed. Please help how this can be disabled.
Thanks
Sravan

Hope you know good etiquette in replying to the messages
I don't know from where etiquette came into picture for this. For sure I haven't stated anything which is personal or derogatory in nature. I have simply stated the facts, which if you re-read again would become clear.
Anyway if you still think that anything I have said has offended you or this forum, do let me know what is that you found which is out-of-context & I would be only glad to correct myself.

How to print sales order acknowledgement while printing purchase order

how to print sales order acknowledgement while printing corresponding purchase order
in me22n

in print program of Purchase order.. try to trigger output for Order Ack. as well...
Order acknowledgement

Deleated Valuation Type --Need Error Message while creating Purchase Order

Hi,
In our scenario , i need a message should flash , if enduser by mistake select the deleated valuation type while creating Purchase Order.
In current configuration , it's not there.
Await your expert opinion.
Regards
Shyam Kogta

I investigated this recently in our company and gave this answer:
A deletion flag does not restrict anything. It is just an indicator to tell SAP that you want this record to be deleted with the next archiving run.
The archiving run then checks if a deletion is possible or not.
So you can set such deletion flags long time in advance, even at a moment where you still have inventory.
To block materials from beeing used in business transactions, usually the material and sales status are used. But these statuses can only be set at overall, plant and sales organisation level.
In some transactions SAP issues warning messages if a material has a deletion flag. This messages could be customized to be an error and prevent any business. However, this type of restriction is not designed for our machine, as we use the material and sales status.
Anyhow, there is no message for valuation types that have a deletion flag in procurement area.
There is one for goods receipts (but only for a certain industry solution that is not used by us)
There is one for deliveries ( VL 211 ).
The valuation types are defaulted from customizing to the transaction e.g. purchase order. Or from info record to the PO. So a standard purchase order gets valuation type ABC , while an internal order (production) gets the DEF. Usually there should not be a need to change this valuation type manually.
So the only solution is to archive the material master at valuation type level.
But I guess, you already have POs with that wrong valuation type, which means you have to archive the POs first. It you have already batches with wrong valuation type, then thy have to be archived as well before a material can be archived.
And finally if you had stock in current year, then you can archive your material in year after next year, as SAP archives only materials that have no stock in current and previous year.

Mass display or print Purchase Order History

Instead of checking your Purchase Order History one at a time, you can now mass display or print them with this customized abap report.
Mass display or print Purchase Order History
You can request report by :
1. Change date
2. User Name
3. Purchase Order Number
4. Vendor Code
Written by : SAP Basis, ABAP Programming and Other IMG Stuff
             http://www.sap-img.com
REPORT ZPOCHANGE LINE-SIZE 132 NO STANDARD PAGE HEADING
                 LINE-COUNT 065(001)
                 MESSAGE-ID VR.
TABLES: DD04T,
        CDHDR,
        CDPOS,
        DD03L,
        DD41V,
        T685T,
        VBPA,
        TPART,
        KONVC,
        EKKO.
SELECT-OPTIONS: XUDATE FOR CDHDR-UDATE,
                XNAME FOR CDHDR-USERNAME,
                XEBELN FOR EKKO-EBELN,
                XLIFNR FOR EKKO-LIFNR.
SELECTION-SCREEN SKIP.
TEXT-001 - Sorting Sequence
SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001.
PARAMETERS: SUDATE RADIOBUTTON GROUP R1,
            SNAME RADIOBUTTON GROUP R1,
            SOBID RADIOBUTTON GROUP R1.
SELECTION-SCREEN END OF BLOCK BLK1.
DATA: WFLAG,
      WCHANGENR LIKE CDHDR-CHANGENR.
DATA: INDTEXT(60) TYPE C.
DATA: BEGIN OF ICDHDR OCCURS 50.
        INCLUDE STRUCTURE CDHDR.
DATA: END OF ICDHDR.
DATA: BEGIN OF ICDSHW OCCURS 50.
        INCLUDE STRUCTURE CDSHW.
DATA: END OF ICDSHW.
DATA: BEGIN OF EKKEY,
        EBELN LIKE EKET-EBELN,
        EBELP LIKE EKET-EBELP,
        ETENR LIKE EKET-ETENR,
      END OF EKKEY.
DATA: BEGIN OF ITAB OCCURS 50,
        BEGIN OF EKKEY,
          EBELN LIKE EKET-EBELN,
          EBELP LIKE EKET-EBELP,
          ETENR LIKE EKET-ETENR,
        END OF EKKEY,
        CHANGENR LIKE CDHDR-CHANGENR,
        UDATE    LIKE CDHDR-UDATE,
        UTIME    LIKE CDHDR-UTIME,
        USERNAME LIKE CDHDR-USERNAME,
        CHNGIND LIKE CDSHW-CHNGIND,
        FTEXT    LIKE CDSHW-FTEXT,
        OUTLEN   LIKE CDSHW-OUTLEN,
        F_OLD    LIKE CDSHW-F_OLD,
        F_NEW    LIKE CDSHW-F_NEW,
      END OF ITAB.
DATA: OLD_OBJECTID LIKE CDHDR-OBJECTID.
FIELD-SYMBOLS: <F_OLD>, <F_NEW>.
SELECT * FROM EKKO WHERE EBELN IN XEBELN AND
                         LIFNR IN XLIFNR.
CLEAR CDHDR.
CLEAR CDPOS.
CDHDR-OBJECTCLAS = 'EINKBELEG'.
CDHDR-OBJECTID   = EKKO-EBELN.
PERFORM GETCHGDOCS.
ENDSELECT.
IF SUDATE = 'X'.
SORT ITAB BY UDATE EKKEY-EBELN CHANGENR EKKEY-EBELP
               EKKEY-ETENR.
ELSEIF SNAME = 'X'.
SORT ITAB BY USERNAME EKKEY-EBELN CHANGENR EKKEY-EBELP
               EKKEY-ETENR.
ELSE.
SORT ITAB BY EKKEY-EBELN CHANGENR EKKEY-EBELP EKKEY-ETENR.
ENDIF.
LOOP AT ITAB.
CLEAR: INDTEXT, EKKEY.
CASE ITAB-CHNGIND.
    WHEN 'U'.
        INDTEXT(50) = ITAB-FTEXT.
        INDTEXT+51 = TEXT-020.
        CONDENSE INDTEXT.
    WHEN 'D'.
        INDTEXT = TEXT-021.
    WHEN 'E'.
        INDTEXT(5) = ITAB-FTEXT.
        INDTEXT+51 = TEXT-021.
        CONDENSE INDTEXT.
      WHEN 'I'.
        INDTEXT = TEXT-022.
    ENDCASE.
    RESERVE 4 LINES.
    IF WCHANGENR NE ITAB-CHANGENR.
      WCHANGENR = ITAB-CHANGENR.
      EKKEY = ITAB-EKKEY.
      WRITE:/ ITAB-UDATE UNDER 'Change Date',
              ITAB-UTIME UNDER 'Time',
              ITAB-USERNAME UNDER 'User Name',
              ITAB-EKKEY-EBELN UNDER 'PO No',
              ITAB-EKKEY-EBELP UNDER 'Item',
              ITAB-EKKEY-ETENR UNDER 'Sch No',
              INDTEXT     UNDER 'Changes'.
    ELSEIF ITAB-EKKEY NE EKKEY.
      WRITE:/ ITAB-EKKEY-EBELP UNDER 'Item',
              ITAB-EKKEY-ETENR UNDER 'Sch No',
              INDTEXT     UNDER 'Changes'.
    ENDIF.
    CASE ITAB-CHNGIND.
      WHEN 'U'.
        ASSIGN ITAB-F_OLD(ITAB-OUTLEN) TO <F_OLD>.
        ASSIGN ITAB-F_NEW(ITAB-OUTLEN) TO <F_NEW>.
        WRITE: / TEXT-023 UNDER 'Changes',
                 <F_OLD>.
        WRITE: / TEXT-024 UNDER 'Changes',
                 <F_NEW>.
      WHEN 'E'.
        ASSIGN ITAB-F_OLD(ITAB-OUTLEN) TO <F_OLD>.
        WRITE: TEXT-023 UNDER 'Changes',
               <F_OLD>.
    ENDCASE.
    SKIP.
ENDLOOP.
TOP-OF-PAGE.
WRITE:/ SY-DATUM,SY-UZEIT,
       50 'P U R C H A S E O R D E R   H I S T O R Y',
      120 'Page', SY-PAGNO.
WRITE: / SY-REPID,
         60 'Purchase Orders Changes'.
SKIP.
ULINE.
IF SUDATE = 'X'.
WRITE:/001 'Change Date',
         014 'Time',
         024 'User Name',
         038 'PO No',
         050 'Item',
         057 'Sch No',
         065 'Changes'.
ELSEIF SOBID = 'X'.
WRITE:/001 'PO No',
         013 'Item',
         020 'Sch No',
         028 'Change Date',
         041 'Time',
         051 'User Name',
         065 'Changes'.
ELSE.
WRITE:/001 'User Name',
         015 'Change Date',
         028 'Time',
         038 'PO No',
         050 'Item',
         057 'Sch No',
         065 'Changes'.
ENDIF.
ULINE.
FORM GETCHGDOCS.
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
       EXPORTING
            DATE_OF_CHANGE    = CDHDR-UDATE
            OBJECTCLASS       = CDHDR-OBJECTCLAS
            OBJECTID          = CDHDR-OBJECTID
            TIME_OF_CHANGE    = CDHDR-UTIME
            USERNAME          = CDHDR-USERNAME
       TABLES
            I_CDHDR           = ICDHDR
       EXCEPTIONS
            NO_POSITION_FOUND = 1
            OTHERS            = 2.
CHECK SY-SUBRC EQ 0.
DELETE ICDHDR WHERE CHANGE_IND EQ 'I'.
CHECK NOT ICDHDR[] IS INITIAL.
LOOP AT ICDHDR.
    CHECK ICDHDR-UDATE IN XUDATE.
    CHECK ICDHDR-USERNAME IN XNAME.
    CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
                 EXPORTING CHANGENUMBER       = ICDHDR-CHANGENR
                 IMPORTING HEADER             = CDHDR
                 TABLES     EDITPOS            = ICDSHW
                 EXCEPTIONS NO_POSITION_FOUND = 1
                            OTHERS             = 2.
    CHECK SY-SUBRC EQ 0.
    LOOP AT ICDSHW.
      CHECK ICDSHW-TEXT_CASE EQ SPACE.
      MOVE-CORRESPONDING ICDSHW TO ITAB.
      MOVE-CORRESPONDING ICDHDR TO ITAB.
      MOVE ICDSHW-TABKEY+3 TO ITAB-EKKEY.
      APPEND ITAB.
    ENDLOOP.
ENDLOOP.
ENDFORM.
END OF PROGRAM

Hi,
copied from          http://www.sap-img.com/mm001.htm

Issues with printing purchase order

Dear friends,
I'm having some issues with printing purchase orders.
Normally when I create a purchase order via ME21N and then when I save the purchase order it then gets automatically printed.
Suddenly it is not anymore working. I have created a purchase order this morning and it did not get printed. I get the message "frontend is not available"when i check the spool in SP01
The funny think is if i call up the spool nr via SP01and then do a reprint then i'm able to reprint.
What can be possibly the issue that I can't print the purchase order when I create the purchase order via ME21 when I save the purchase order? Can you help me with any guide on where I need to check why the PO is not printing immediatelly when i create the PO via ME21N?
kind regards,
Camilla

hello all,
thanks so far for your reply.
i have checked today my user settings and that shows that my prints should go to LOCL (local default printer)
The output conditions fpr purchase order have also LOCL (local printer)
The weird thing is that I can print other reports to the default printer without any issues. The issue arise when I create a purchase order via ME21N. Normally when I save the PO it automatically prints. So no manual print instructions are required from my side. Because if I give manual instructions then I'm able to print the purchase order.
Is it possible that the automatic printing is switched off and that it only prints when I hit manually the print button?
Is the automatic printing something that is maintained in SPAD?
kind regards and thanks for your help sofar

Issue while creating Purchase order (ME21N)

Hi Friends,
Hope U Have a Good Day...
My issue is while creating purchase order , I enter vendor and in org.data tab I enter Pur.Org,company code and purchase group. After entering these values if I check in communication tab, the sales person and telephone fields are filled with corresponding data.
Now my requirement is after entering Pur.Org, Company code and purchase group, and if I go and check in Communication tab, these two fields ( sales person, telephone ) should be blank.
Please help me in this issue...
Thanks & Regards
Ganesh Reddy

Hi Ganesh,
This is being fetched frm the vendor master and if u wan this field to be blank
Then u hav to remove those data frm the vendor master .
Put tat vendor, comp code n purchase org
Then select pur org data alon - >chk in purch data
u can find tat sales person n telp no being appeared in the PO
lemme know if u hav any prob in getting tat .

Printing purchase order 'in release' !

Hello,
we need to add a second printing document for purchase order. I think it's possible with a new message. But i've read that message works only if the purchase order is not 'in realease'.
Is it possible to print purchase order document when the purchase is 'in release' ?
Thank's

hi,
AS per my knowledge it shd be possible after full release only...because then only it make sense of the printing and sending to the vendor...
If it would be possible before or within release only, and if the changes are made in between while the release by any officer, then it'll not get reflected....
Regards
Priyanka.P

What is the BADI while SAVING purchase order using me22n?

what is the BADI while SAVING purchase order using me22n?
while i will save purchase order through me22n, badi should be fire what is badi for that?
regards,
dushyant.

Dushyant,
Hopefully you know how to implement the BADI ME_PROCESS_PO_CUST now.
The following are the codes that you can put in the method "Post".
DATA: LW_HEADER        TYPE MEPOHEADER,
        LW_POSTED_HEADER TYPE MEPOHEADER,
        LW_VALID         TYPE MMPUR_BOOL,
        ITAB_ITEM        TYPE PURCHASE_ORDER_ITEMS,
        LW_ITEM          TYPE MEPOITEM,
        ITEM_INTERFACE   TYPE PURCHASE_ORDER_ITEM,
        ITAB_ACCT        TYPE PURCHASE_ORDER_ACCOUNTINGS,
        ACCT_INTERFACE   TYPE PURCHASE_ORDER_ACCOUNTING,
        LW_ACCT          TYPE MEPOACCOUNTING,
        LW_POSTED_ACCT   TYPE MEPOACCOUNTING,
        W_ACCT_CHANGED TYPE C,
        W_GRANT_AMT      TYPE EKPO-NETWR,
        W_FINANCE_AMT    TYPE EKPO-NETWR,
        W_FLAG           TYPE C.
Check if PO header data is valid
CLEAR LW_VALID.
CALL METHOD IM_HEADER->IS_VALID
    RECEIVING
      RE_VALID = LW_VALID.
CHECK LW_VALID = 'X'.
PO header data is valid
Get the newly updated PO header data
CLEAR LW_HEADER.
CALL METHOD IM_HEADER->GET_DATA
    RECEIVING
      RE_DATA = LW_HEADER.
Get the posted PO header data
CLEAR LW_POSTED_HEADER.
CALL METHOD IM_HEADER->GET_PERSISTENT_DATA
    IMPORTING
      EX_DATA = LW_POSTED_HEADER
    EXCEPTIONS
      NO_DATA = 1.
IF SY-SUBRC <> 0.
    CLEAR LW_POSTED_HEADER.
ENDIF.
Get PO line items
REFRESH ITAB_ITEM.
CALL METHOD IM_HEADER->GET_ITEMS
    RECEIVING
      RE_ITEMS = ITAB_ITEM.
LOOP AT ITAB_ITEM INTO ITEM_INTERFACE.
Check if PO line item is valid
    CLEAR LW_VALID.
    CALL METHOD ITEM_INTERFACE-ITEM->IS_VALID
      RECEIVING
        RE_VALID = LW_VALID.
    IF LW_VALID <> 'X'.
This PO line item is not valid
      CLEAR W_ACCT_CHANGED.
      EXIT.
    ENDIF.
    CLEAR LW_ITEM.
    CALL METHOD ITEM_INTERFACE-ITEM->GET_DATA
      RECEIVING
        RE_DATA = LW_ITEM.
Get the account interface
    REFRESH ITAB_ACCT.
    CALL METHOD ITEM_INTERFACE-ITEM->GET_ACCOUNTINGS
      RECEIVING
        RE_ACCOUNTINGS = ITAB_ACCT.
    LOOP AT ITAB_ACCT INTO ACCT_INTERFACE.
      CLEAR LW_ACCT.
Get the newly updated PO item data
      CALL METHOD ACCT_INTERFACE-ACCOUNTING->GET_DATA
        RECEIVING
          RE_DATA = LW_ACCT.
      CLEAR LW_POSTED_ACCT.
Get the posted PO item data
      CALL METHOD ACCT_INTERFACE-ACCOUNTING->GET_PERSISTENT_DATA
        IMPORTING
          EX_DATA = LW_POSTED_ACCT
        EXCEPTIONS
          NO_DATA = 1.
      IF SY-SUBRC > 0.
        CLEAR LW_POSTED_ACCT.
      ENDIF.
      IF LW_ACCT-LOEKZ <> LW_POSTED_ACCT-LOEKZ OR
         LW_ACCT-KOSTL <> LW_POSTED_ACCT-KOSTL OR
         LW_ACCT-PRCTR <> LW_POSTED_ACCT-PRCTR OR
         LW_ACCT-PS_PSP_PNR <> LW_POSTED_ACCT-PS_PSP_PNR.
Account assignment was changed
We will force this PO to go through workflow
        W_ACCT_CHANGED = 'Y'.
      ENDIF.
    ENDLOOP.
ENDLOOP.

Print purchase Order

Hi All,
We have an issue when printing purchase orders.
When the purchas eorder goes on to two page we get a blank page inbetween.
Does anyone know what could be causing this?
The SAP Script looks OK so I imagine that it must be a setting in config somewhere?
Thanks
Stuart

Hi,
It is the issue related to the Form layout..
Are you using the SAP STD Driver program and Form Layout.
If yes..you will not get such issue.
If you are using Custom Form,please check with your ABAP developer..
Thanks,
Kumar Arcot

Problem with Delivery Type Determination in Purchase Order

Dear All,
We are working on a IS-Retail Scenario where we are dealing with generic articles. While creating a PO, we have encountered an error which says:"Also specify a delivery type in case of shipping data relevance". The error message number is MEPO 099. We have checked that Delivery type NL is attached to the document type under the supplying site customizing, and supplying site is attached to the receiving site with the correct document type. Can anybody throw some light on what we might be missing out in this scenario?
Thanks and Sincere Regards,
Amitabha

Hi
I suppose you are creating a retuns PO ,
Please maintain the customizing of the same in SPRO-> MM -> Purchasing-> Purchase Order-> Returns Order-> Store Return / Return Plant to Plant
here you need to maintain the delivery type for returns.
This message is trigerred only in case of Returns order
In SAP Retail, plants are referred to as distribution centers or stores. With store returns, you can map the return delivery of goods from
a store to a distribution center (this is the most common case),
from one distribution center to another distribution center,
from one store to another store,
from a distribution center to a store (although this is not very common).
Requirements
For the return delivery types, you have to make settings for the item category determination.
Partner schema must be assigned to the return delivery types.
The relevant goods movement types must be assigned to the schedule line categories (for the returns in Sales). The following schedule line categories are also available in the system:
NR - Replenishment Returns and
NS - Replenishment Cross Company Returns
Activities
Assign the required return delivery type to
purchasing document category F (purchase order),
purchasing document type (NB - standard purchase order, UB - stock transport order),
the supplying plant (the one to which the goods are being returned)
The following return delivery types are available in the system:
NLR - intra-company-code store returns (purchasing document type UB for replenishment and return orders, delivery type NL for the replenishment delivery)
NCR - cross-company-code store returns (purchasing document type NB for replenishment and return orders, delivery type NLCC for the replenishment delivery)
Please maintain the required customizing
Thanks & Regards
Kishore

New order type for a purchase order similar tu UB.

Hi,
I would like to know if it is possible to create a new order type for a purchase order. This new order type should work as a UB order type but "plant" and "storage location" should be indicated by default and shouldn't be changed.
How should I proceed?
Thanks in advance.
Luis.

The problem is that If I specify default values for each user (plant and storage location) It will always propose these values when using different order types. This can't be.
Isn't there any other solution in standard sap?
Edited by: LUIS ÁLVAREZ on Apr 26, 2010 11:25 AM

While creating Purchase order the system is showing error: vendor 200001145

Hi experts,
while creating Purchase order the system is showing error: vendor 200001145 on line 00010 for ctype ZB12 not defined as head office vendor.
Plz give solution for this.
Thanks&Regards
sreenivas

Hi,
Please check vendor schema maintained in the vendor master,. through this condition type arepicking from system
Aboue condition type not mainatained inthe caluation schame ,which you assigend to vendorand purchasing organization
regards
Channa
Edited by: channadodawad on Dec 3, 2009 9:22 AM

Price not picking while creating purchase order

hi all,
i have created a pricing procedure and assigned to the vedor, but while creating purchase order the material price is not picking up.if i use the standard one the price is picking up. can anyone explaing any setting iam missing.
regards
thyagarajan

Hi
In your pricing procedure
For the condition type Automatic Gross price PB00, you have assigned am Access sequence.
<b>Access sequence</b>: An access sequence is a search strategy by means of which the system searches for valid records in various condition tables. It consists of one or more accesses. The sequence of accesses controls the priority of the individual condition records among each other. Through the accesses, the system is told where to look first and where to look next for a valid condition record in each case.
Once the pricing procedure triggers, System looks for the valid condition recorrd for the condition type PB00 as per the priority listed in Access sequence.
Example: If purchase info record is the first priority and you maintained the Info record then system picks the price from Info record into PO.
If no valid condition record found then it will trigger PBXX Manual Gross price condition in PO and ask to enter the price manually.This is called condition technique.
So check whether you maintained the Condition record for PB00 or not?
Regards
Ramakrishna

Plants / Excise Group / Series while preparing Purchase Orders, Sales Orde

Dear all,
sap gurus plz do need ful
Presently we are making some mistakes by selecting wrong Plants / Excise Group / Series while preparing Purchase Orders, Sales Orders, GRIR and Invoices. We need to make it mandatory to select respective Plant / Excise Group / Series only, so that no-body can select other plant except the respective document.
full points awarded,
regards
deepa

Hi,
For a particular user, you can set the user parameters in transaction in SU3 wherin you can set the default values.
Regards

Default two ouput types while printing Purchase order

Similar Messages

Maybe you are looking for