Purchase Order Mass Printing

Hi Friends
Is there any transaction to Mass Print Purchase Orders? We dont want to repeat output, just want to print the hard copy of all purchase orders for a vendor in one go.
Thanks for any help on this.
Francis Tony

Hi Vabhaw
If the output is already processed, you cannot do it.
My requirement is, to take hard copy of all purchase orders against a vendor (which is already processed earlier). I dont want to have repeat output maintained on the PO or repeat output to go to vendor. Hope my requirement is clear.
Thanks
Francis

Similar Messages

Purchase order mass maintenance

Dear All..
Im using purchase order mass maintenence through MASS T-code with object BUS2012
i want to change field EKPO-MHDRZ it is wrongly maintained as 2 i want to remove this via mass maintainence.
at the time of saving the document its telling no error its telling green colour message as Change Rem.Shelflifetime could not be effected.
message no ME664.
But i want to change.. any possibilities is there.. or any other procedure is there to for PO Mass maintenence...
Regards
Anand.
Edited by: Anandhakumar Palanisamy on Jan 23, 2009 12:34 PM

the field is in purchase order detail on tab delivery
Why you like to remove a value from field you do not even know where it is?
if you dont see the field there, then check IMG > MM > purchasing > Purchase Order > Define Screen Layout at Document Level
select e.g ME21N and go into detail
then go into detail of Delivery monitoring
there you should see the field remaining shelf life and if it is a req. entry , optional entry or display only.
Because you want remove a value, it has to be optional.

PREREQUISITE FOR PURCHASE ORDER MASS MAINTENENCE

Dear Experts,
Please explain the prerequisite points for the purchase order Mass Maintenance.
i want to set Delivery completed indicator for the open purchase orders.
is it prerequisite for setting the deletion flag to the purchase order items.
if delivered quantity is more the PO order quantity, it is not allowing to set the deletion flag
also it issues the warning message of release PO - Release already affected.
Please explain the concept in brief.
Thanks in Advance

Hi,
When you set the "delivery completed" indicator, it considers a purchase order item to be closed. This means that no more goods receipts are expected for this item. If the "delivery completed" indicator is set, the open purchase order quantity becomes zero, even if the full quantity has not been delivered. It is still possible to post goods receipts for the remaining quantities.
When you set the "delivery completed" indicator:
The purchase order item is considered closed, even though the total quantity may not have been delivered.
Although a further delivery is not expected, it is still possible.
At the time of the next goods receipt, the system suggests the item as unselected in the item selection list.
The purchase order item can be deleted, even if the total quantity was not delivered..
Thanks and Regards,
Maheshwari

Printed XML Purchase Order Report - Printing blank Blanket PO page

Hi,
When printing the xml report of a Blanket PO Release, the release lines and headers print first but the last page is a page for the primary blanket PO (PO Num without any releases attached). This page does not contain any information in the header or line fields therefore it is a waste of paper. Looking into the XML code the blanket PO page is pulled in the same manner as the Release lines, against G_Headers. I'm going to look into the Reports Developer SQL to see if I can find something but I would rather not mess with the configuration of the SQL if I did not have to.
Any ideas on how to get rid of this extra unnecessary page?
Thanks,
-Steve

Hi,
RDBMS : 11.2.0.1.0
Oracle Applications : 11.5.10.2
OS: Unix
The issue can be reproduced.
The report in question has had customization but the blank page prints in the Printed Purchase Order Report(Portrait) seeded function as well. From what I see the SQL might be able to modified based off of the input paramet "Print Blanket PO". When this is selected "No" the Blanket header is printed with no lines (that's where the blank PO page is coming from). When selected Yes the blanket header with all the blanket lines are printed. So I may be able to go in and change how that input parameter changes the output, unless there is a better way.
-Steve

How to define a purchase order output print view as my element

Dear all :
I have created a purchase order and want to print,but i found the details of print doc is not my requirements.So,I want to change it .I don't know where the path is .THKS
Brian

Hello Jianfeng,
The purchase order layout can be changed using the SAP script/Form. You need to identify what you need to put on the purchase order output also you can include the client's logo and other standard and constant details (tax number / registration number etc).
You have to give this requirement to the technical person (ABAPer). (S)he will make the changes in the script program and you need to assign this form to the PO printing program.
In standard SAP version, Form MENDRUK is available for Purchase order printing.
Once form is developed by the developer, you need to assign this form in customization,
SPRO--> Mat Managmenet --> Purchasing --> Messages --> Forms Layouts for messages --> Assign form and output program for purchase order.
Hope this helps.
Regards
Arif Mansuri
Reward the points if answer is helpful.

Purchase order form printing is required in preprinted stationary format

Dear All,
I need one VERY URGENT HELP from you.
Client wants to do printing Purchase order form in preprinted stationary format i.e. using this format they want to print PO document only for certain variable fields each time in our Laser printer,but some fields (which are already) lying will not be printed. (But in the PDF Download of the form for each document number all the fields must appear).
Could you please guide me what are the sequential steps need to be followed, where & how in order to incorporate "preprinted stationary format" scenario in my
Purchase order form. Also, if possible, please tell me in brief what is the meaning of preprinted stationary format & why we are using it / purpose of it.
Awaiting your favorable reply at the earliest.
FYI. Anyways, I have convinced Client that we will provide PDF attachment of form only to them, not Excel attachment. Thanks very much for encouraging me.
Thanks & Regards
Sudipta

Hi,
Thank you for your valuable input.
Please tell me what should be my approach i.e. sequential steps need to be followed & where ( with the related configuration / settings changes, necessary coding changes & where, if possible, please send me one realtime scenario and its related documentation related to my concerned issues at the earliest as it will be very beneficial for mine. I have come across this scenario for the 1st time. Kindly guide me with your documents) in order the incorporate the below requirement:
After modication of standard Purchase order form using SAPSCRIPT I / Client want to download it into PDF attachment individually corresponding to each PO number. In this PDF attachment all the fields will appear.
But when I / Client will take Printout of this modified PO form (say for example ZMEDRUCK) only certain important information / certain field values will be getting printed, not all.
User will be able to give ranges of PO document numbers for printing at a time based on their requirement, here all documents as specified by the user will be getting printed at a time, but one document printout followed by another document printout , and so on.
We want to print PO sapscript form in "Print output" only. Also, please guide me how many & which output types, message type etc we need to configure & how for the above requirement ( i.e. download of the ZMEDRUCK form into PDF with its all the fields values + printing this ZMEDRUCK form for printing certain important information using "preprinted stationary format".)
FYI. We are using Laser Printer for printing SAPSCRIPT forms.
Awaiting your valuable fruitful feedback with necessary documents at the earliest.
Thanks a lot.
Have a very nice time ahead.
Thanks & Regards
Sudipta

Purchase Order form printing error.

Hi all experts,
I am not sure which category I should put this question to. Please guide me if I have raised the question in the wrong category, so that I can raise it at the right category. Sorry!
I am having some problems in printing Purchase Order form using Simple Mail, let's say I am using output type MAHN. Whenever the PO is generated in Simple Mail, a print preview screen with Output Device is pop up, and require me to key in the details like printer name in order to proceed to next step (which is not necessary for my case).
Whereas, in normal print preview, there is no such pop up display.
I am suspecting of it is caused of the setting. But I do not know how to solve it.
Anyone experienced this before? Please help.
Thanks in advance.

Hi Sachin D C,
I am sorry for the confusing query. Actually what I wanted to say is: -
1) printing the PO - maintain condition records for output type NEU (working fine)
2) printing Dunning Deliv Remind - output type MAHN (working fine in manual print out)
3) printing Dunning Deliv Remind - output type MAHN (not working in simple mail)
Whenever the Dunning Deliv Remind is generated in Simple Mail, a print preview screen with Output Device is pop up and following by another pop up screen Output Processing analysis.
Do you have better understanding now?
Please help.

Standard Purchase Order document printing

Hi All,
I need to modify the standard purchase order document and need to print a custom note in that based on the organization criteria.
i have downloaded the .xsl file and as i am not very familiar with that i cant understand the code.
1)could you please let me know, where to open that xsl file either in jdeveloper or some thing like notepad, textpad etc..
2)If possible please share the tags to print the custom message based on organization criteria
3) where to find the xml tags related to that to modify the xsl
Please help!!
Thanks!!

We need to investigate this XSL tags and need to do R&D. I finally did it.

Purchase order is printed in LOCL

Hi,
In "communication" i have put an output device ZZ01 different of LOCL. But when i print the purchase order, the document is printed in LOCL.
What's missing.
Thanks.

Hello,
Please go to...
System menu>> User profile>> Own data.
Under defaults tab, check if the output device is correctly defined. If not then correct it and clilck on save.
Now try to print and hope this should resolve the issue.
Regards,
Robin

Purchase order SAPFM06P print program

Dear all,
Does anyone know how this print program works? In standard I seems that there are only two includes and when I look inside it the ME_READ_PO_FOR_PRINTING function module is repeated several times. My goal is to add field at the item level but I did even not identified where the open_form FM is declared...
Best regards.
NC.

Hi Milind,
Hereafter is the code I find within FM06PF02 include.
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.
*eject
Umlagerungsbestellung, Hinweis 670912                               *
form entry_neu_sto 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,
        F_STO.                                              "670912
clear ent_retco.
if nast-aende eq space.
    l_druvo = '1'.
else.
    l_druvo = '2'.
endif.
F_STO = 'X'.                                              "670912
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
            ix_sto         = F_STO                          "670912
       IMPORTING
            ex_retco       = ent_retco.
endform.
*eject
Mahnung
form entry_mahn 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.
l_druvo = '3'.
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.
*eject
Auftragsbestätigungsmahnung
form entry_aufb 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.
l_druvo = '7'.
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.
*eject
Lieferabrufdruck für Formular MEDRUCK mit Fortschrittszahlen
form entry_lphe using ent_retco ent_screen.
data: l_druvo like t166k-druvo,
        l_nast like nast,
        l_from_memory,
        l_xfz,
        l_doc   type meein_purchase_doc_print.
clear ent_retco.
l_druvo = '9'.
l_xfz = 'X'.
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_xfz         = l_xfz
            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.
*eject
Lieferabrufdruck für Formular MEDRUCK ohne Fortschrittszahlen
form entry_lphe_cd 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.
l_druvo = '9'.
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.
*eject
Feinabrufdruck für Formular MEDRUCK mit Fortschrittszahlen
form entry_lpje using ent_retco ent_screen.
data: l_druvo like t166k-druvo,
        l_nast like nast,
        l_from_memory,
        l_xfz,
        l_doc   type meein_purchase_doc_print.
clear ent_retco.
l_druvo = 'A'.
l_xfz = 'X'.
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_xfz         = l_xfz
            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.
*eject
Feinabrufdruck für Formular MEDRUCK ohne Fortschrittszahlen
form entry_lpje_cd 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.
l_druvo = 'A'.
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.
*eject
INCLUDE FM06PE02                                                   *
form entry_neu_matrix 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_mflag       = 'X'
            ix_toa_dara    = toa_dara
            ix_arc_params = arc_params
            ix_fonam       = tnapr-fonam          "HW 214570
       importing
            ex_retco       = ent_retco.
endform.
*eject
Angebotsabsage
form entry_absa 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.
l_druvo = '4'.
clear ent_retco.
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.
*eject
Lieferplaneinteilung
form entry_lpet 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 = '5'.
else.
    l_druvo = '8'.
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.
*eject
Lieferplaneinteilung
form entry_lpfz 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 = '5'.
else.
    l_druvo = '8'.
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_xfz         = 'X'
            ix_toa_dara    = toa_dara
            ix_arc_params = arc_params
            ix_fonam       = tnapr-fonam          "HW 214570
       importing
            ex_retco       = ent_retco.
endform.
*eject
Mahnung
form entry_lpma 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.
l_druvo = '6'.
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.
Now I would like to know how does this get the purchase order title from transparent table t166u in order to copy the procedure within my client customized program.
Does this include refers to the MEDRUCK function module?
Regards.
NC.

Purchase Order Text Print ?

Hi
I have created 7 Purchase order Document Types copying Standard(NB).
when i go into print preview of Standard. i could see all the texts entered at header level.
However when i go to print preview of the newly created ones i cant see the texts maintained at header level .
Do i need to link the New purchase order document types to the text field. please help me on this .

Hello Archie,
Goto IMG->Materials Management->Purchasing->Messages->Text for Messages->Define Texts for Prchase Orders
Configure here for all the new document types you have created as per standard one.
I think this will help you.
Rgds,
S.Balaji.

PCO (Purchase Order Response) Print

Hi guys
Is there a standard way to print a PCO (Purchase Order Response) created directly in the SRM system?
I have tried to print it but i could not find the place to do this task...
As far i know we have just two transactions related to PCO only for creation....
Enter Purchase Order Response ->BBPPCO02
Process Purchase Order Response -> BBPPCO01
1 - How to check the details of a PCO? Is there a standard way to do it? (similar to BBPSC04)
2 - How to print an individual PCO or generate a list of PCO?
(E.g with SC if you go to BBPSC04 you can perform a SC print preview by clicking on the print icon.)
Any doubts just let me know.
Your help or suggestion is highly appreciated.
Thanks & regards
Alvaro

Hi
Ddi you check any standards SMATFORMS for this POR. i aware it is available for SC,PO.
If you get smart form, you can print them right.
regards
Muthu
Edited by: Muthuraman Govindasamy on Sep 5, 2008 7:35 AM

Change output - purchase order - stop print based on criteria

Hi,
In config (print relevant purchase order changes), we have he purchase order indicator turned on for a specific field, so every time we change that field in the purchase order its going to print , however, for some types of material (info is available in EKPO) i need to contol the print ( print or not to print) , please let me know the appropriate user exit or enhancement where i can control the print.
when the PO is approved in ME29N system generates a print and i need to control it. any suggestions are welcome
Thanks,
VY.

Hi,
Check BADI "ME_PROCESS_PO_CUST".
Best regards,
Prashant

Purchase Order: Mass modifications

Hello:
I'm using transaction MEMASSPO to change "delivery date" in purchase orders but I can't. OSS note 443777 says it is possible to do that since:
"... Transaction MEMASSPO can only change fields which are contained in the standard system of program SAPMM06E on the following screens:
0101 header data purchase order
0111 order item data purchase order
0120 purchase order item overview
and which can there be changed in transaction ME22
and "delivery date" in in screen 0120.
Can anyone help me, please?
Thanks,
Abel Grandal

Hi Abel,
If there are multiple schedules for a PO item then you can not change delivery date from item overview screen.
Cheers,
Sanjeev

Purchase order SAPFM06P print program to smartform

Purchase order SAPFM06P,
The above programs referes to PO script form. Now i have created PO smartform. I am looking for program to call smartform. But this program refers to script. So how can i find the smartform calling program.
Regards,
Vasudeva

You have to create a new program. You can copy SAPFM06P into Z program and should make some changes in new program.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
     EXPORTING
           formname = "write the formname you created
     IMPORTING
           fm_name = function_module_name.
CALL FUNCTION function_module_name
After writing this program, go to NACT transaction and set your Z program.

Purchase Order Mass Printing

Similar Messages

Maybe you are looking for