Output purchasing document

Hi ,
I am trying to change the certain output type for the order to trigger at time of saving only during change not during the creation but I could not find any std. setting. Please let me know how we can make it work.
--JOHN

Hi,
You can not assign different output types for creation and change. For both you can same output type only.
Regards.
Chinna

Similar Messages

Warning "No message generated for output of purchasing document" disabled

Hello Gurus
When a PO in ME21N is created and for some reason there was no output message determined the system should give a warning message "No message generated for output of purchasing document". It causes troubles because buyers don't know when they press SAVE whether output was made or not.
Please advise where to enable this feature.
Note: This happens not always and not for every user.
Great Thanks and Best Regards!

Hi Oibek,
This message is automatic , i have not seen any config driving this.
If there is no output message type maintained for document type or requirement is met , system by default issue the warning message 'No message generated for output of purchasing document' .
Check the user GUI setting , may be warning messages are ignored for display.
Logon to SAP -> Customization of Local Layout (ALT+F12)-> Options -> Options tab -> Dailog Box at warning Message ( tick the Check box).
After this try creating PO from user Login , it should display a dialog box even for warning.
Thanking You ,
Sudhakar

Purchase document, mail output type, name of the sender in title...

Hello everyone,
when a user send a purchase document by mail, the vendor, in the mail title, see the user ID instead if his First+LAST name (field "BNAME" instead of "NAME_TEXT" in the SUO1d, adress part). How can i change that?
Thanks a lot for answering.

Hi Friend,
I think mail is firing through output type.
Check the program name in NACE transaction. Consult with ABAPer that the program is sending with which header information and changed it accordingly.
Generaly SO_OBJECT_SEND_AP11 is used for sending.
Hope it will help you.
Regards
Krishnendu

Automatic output of purchasing documents

Hi
I want to send purchasing documents to vendor automatically when i save the documents.I have maintained all settings ( email in vendor master,communicatio startegy...etc).when i saving the PO document is not automatically ouputing.If go to preview i can able to see the send mail icon and if i click tht icon then document is ouputted.
how to send the document automatically.
-Prabu

Hi Prabu,
Please Check further with T-Code NACE-- Select Application EF Purchase Order. select button output types ,select your out put type and also check further all processing routines as well as partner function is all entries are there for external send.
Also check the T code SCOT that is your email is going out properly.
Also check the Smart for MEDRUCK is it OK. If it is all OK. Your PO output should work.
Please assign points if this info is helpful to you...!!!
Regards,
Rohit Guliani

Dear Guru kindly clear my confusion In Print Output of a Purchasing Document In SAP.

Dear Guru,
I am creating a RFQ AND want a printout for it from the standard SAP.
1= I given document no ,purchasing group and in message data given application as EA , Message Type as NEU Processing status 1.but found message
as no purchasing document found.
2=Checked NACE the standard output types
The program ,form routine are above and in partner function the standard partner function is there.
3=If i want a new smart forn then should i use the same program same form routine , same form or make a copy of it and attach a smart form
to the standard or any other process is there?

Hi
See these notes as a checklist
SAP Note 457497 - FAQ: Message processing in purchasing
SAP Note 61871 - Output of messages and release strategy
Check if the message exists in table NAST
I hope this helps you
Regards
Eduardo

Output of purchasing documents

Hi
Can anyone tell me how to send a purchasing document to the ordering address in the purchasing document without manual intervention nor condition record to maintain.
-prabu

By default system will pick the order address.when you are giving the print
regards
venkadesh

No value in Purchasing Document field in FBL1N Transaction

Hi All,
While executing a report RFITEMAP (Transaction FBL1N), Purchasing Document field is blank while I can see the corresponding Purchasing Document in BSEG table. I have a requirement to show the same in the output. Do we have some settings or ABAP code changes to achieve it?
Any kind of input would be helpful to me.
Rgds,
Khanshi

Hi,
Please read note 152335
You can achieve it via OSS note 112312, but you need to program the BTE as per your business requirements, as stated in the note there is no standard functionality for this.
You may refer to the following wiki page, it has an example, but in the example, another field was used, maybe it can be useful for you.
http://wiki.sdn.sap.com/wiki/x/fg3cCw
regards
Waman

Purchase Document not appearing on GL Line item report

Hi gurus: Please help me figure out why even though I have activated the purchase document field in the field status group I still cannot see it in the line item reports when I run FBL3n. Note the purchase document field is showing up as a field for selection but it comes thru blank.
Please help me
thanks
Brian

i wanted to get the same output, it doesnt work for some reason. I had to craete a query to achieve this

Send Purchasing Documents via email/fax to vendor

Hi all,
I have a customer requirement wherein Purchasing documents such as RFQ, PO etc need to be sent to vendors via email/fax. To cater to the customer's form requirements, we developed smartforms instead of using the standard MM purchasing smartforms. To call these smartforms in the print programs, we copied the standard print program SAPFM06P and commented out the function module ME_PRINT_PO in the routine ENTRY_NEU and added the our own code to call the custom smartform. The custom code segment in the print program is attached for reference.
Now, when we are trying to generate messages for the purchasing documents using output type External Send, the custom program does not pick up the email address maintained in the vendor master and instead picks up email address maintained in RFQ or PO initiator's user profile. We have made the required configuration for SCOT and SOST tcodes.
We tested the same scenario requirement using the standard print program and got the desired results i.e. the print program picked up the email address maintained in the vendor master. But with this approach, we cannot use our custom smartform.
Any help in this matter will be appreciated.
Regards,
Saad

Hi Biju !
Thanks for the response but I think you missed the point here. I am using different output types for RFQ and PO as well as different custom smart forms and we are using the same custom print program to generate output for both.
The issue is with the print program and not the output type as I mentioned that I have already got this thing working on our IDES using the standard print program and standard forms.
Tomas Talpa's response seems to be helpful. I'll get my technical consultant to amend the code accordingly and see if it works.
Regards,
SaaD Karim Mallick.

User exits when posting purchase document and goods movement (GR)

I want to update some custom tables when posting PO and goods movement (GR) .
Please suggest user exits for both posting.

Check the below exists
FOR PO
LMEDR001            Enhancements to print program
LMELA002            Adopt batch no. from shipping notification when posting a GR
LMELA010            Inbound shipping notification: Transfer item data from IDOC
LMEQR001            User exit for source determination
LMEXF001            Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001            Customer-Specific Source Determination in Retail
M06B0001            Role determination for purchase requisition release
M06B0002            Changes to comm. structure for purchase requisition release
M06B0003            Number range and document number
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
M06E0005            Role determination for release of purchasing documents
ME590001            Grouping of requsitions for PO split in ME59
MEETA001            Define schedule line type (backlog, immed. req., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1            Enhancement to Document Overview ME21N/ME51N
MEVME001            WE default quantity calc. and over/ underdelivery tolerance
MM06E001            User exits for EDI inbound and outbound purchasing documents
MM06E003            Number range and document number
MM06E004            Control import data screens in purchase order
MM06E005            Customer fields in purchasing document
MM06E007            Change document for requisitions upon conversion into PO
MM06E008            Monitoring of contr. target value in case of release orders
MM06E009            Relevant texts for "Texts exist" indicator
MM06E010            Field selection for vendor address
MMAL0001            ALE source list distribution: Outbound processing
MMAL0002            ALE source list distribution: Inbound processing
MMAL0003            ALE purcasing info record distribution: Outbound processing
MMAL0004            ALE purchasing info record distribution: Inbound processing
MMDA0001            Default delivery addresses
MMFAB001            User exit for generation of release order
MRFLB001            Control Items for Contract Release Order
AMPL0001            User subscreen for additional data on AMPL
For Goods Movement
LMR1M001            User exits in Logistics Invoice Verification
LMR1M002            Account grouping for GR/IR account maintenance
LMR1M003            Number assignment in Logistics Invoice Verification
LMR1M004            Logistics Invoice Verification: item text for follow-on docs
LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006            Logistics Invoice Verification: Process XML Invoice
MRMH0001            Logistics Invoice Verification: ERS procedure
MRMH0002            Logistics Invoice Verification: EDI inbound
MRMH0003            Logistics Invoice Verification: Revaluation/RAP
MRMN0001            Message output and creation: Logistics Invoice Verification

No sutable purchase document found but see in EKKO and Me23n

Hi expert,
Not getting Printout via ME9F.
No sutable purchase document found.
but i can se documnet no in EKKO and Me23n.
Regards,

Hi Vivek,
ME9F can only be used to display Purchase Orders where print relevant changes have been made after output.
See information in Note 450617:
If no print-relevant changes to the purchasing document exist, then it
only possible to display the change message again via the spool request
that was created or the optical archive (if available). For more
information, also consult Note 391637.
In addition, in the above-mentioned transactions bear in mind that you
can recognize a change message by the corresponding indicator on the
message list.
Regards,
Purnima.

Printing purchasing documents.

Hi,
how can I configure the system for printing purchasing documents,
what are the trx for configuring the system?
Best regards

Hi, for each purchase document you have one transaction.
You have to go to transaction SPRO -> Materials Management -> Purchasing -> Messages -> Output Control -> Message Types -> in this section you select what purchasing document you want.
You select output type with double click, on default values you put dispatch time with type 3 or 4, and transmissium medium.
If you want to change programa and form you double click on Processing routines tab.
Then you have to create condition record for this document, you go to Logistics -> Purchasing -> Master Data -> Messages -> in this section you select document that you want.
In this transaction you create by output type, condition record for each document type, etc...
I hope that this information help you
Rose

Maintain plant wise purchase document type

Hi,
I want to know that is there any way where I can able to maintain plant wise purchase document type.
Thanks.

Please make the following settings
Scenario:
Plant 0001 Should create only PO type NB and PR type NB
Plant 0002 Should create only PO type ZNB and PR type ZNB
TCode : OLME
Create new PR type by copying NB (all dependencies): ZNB <<<Separate number range can be used
Create new PO type by copying NB (all dependencies) : ZNB <<< Separate number range can be used
To avoid accidental assignment of (by users)
Remove linkage of NB PO type to ZNB PR type
Remove linkage of ZNB PO type to NB PR type
TCode: OMDT
Assign PR type per plant per MRP Group for MRP generated PR's
Once MRP is run for materials PRs are created as follows plant 0001 type NB and plant 0002 type ZNB, when they run ME57 to create POs from PRs, ZNB PO type will default to PR types ZNB and NB type to NB.
Authorization objects to be changed for each plant respectively (go to SU21 to look up)
Users of Plant 0001 can only create NB type PR and NB type PO
Purchase Order:
M_BEST_BSA   ACTVT=01; BSART=NB;
Purchase Requisition:
M_BANF_BSA   ACTVT=01;BSART= NB;
M_BANF_WRK ACTVT=01;WERKS= 0001 ;
Users of Plant 0002 can only create ZNB type PR and ZNB type PO
Purchase Order:
M_BEST_BSA   ACTVT=01; BSART=ZNB;
Purchase Requisition:
M_BANF_BSA   ACTVT=01;BSART= ZNB;
M_BANF_WRK ACTVT=01;WERKS= 0002 ;
Ofcourse you need to create output message config for each PO type.
Edited by: Jeevan Sagar on Feb 13, 2012 11:16 PM

User exit MM06E005 - Customer fields in purchasing document

Hi,
I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a tab (customer tab) in that the value should get displayed.
likewise for each and every line items the value should keep on changing.
And
I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
Regards
Manoj

Hi,
Indeed the exit which you have specified MM06E005 comprises the enhancement for customizing fields and screens associated with it. may be you might not have activated the screen associated with the exit. the screen might have been created but missed while activating.
Regards,
Jagath

MM06E005 - Customer fields in purchasing document

Hi,
I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a tab (customer tab) in that the value should get displayed.
likewise for each and every line items the value should keep on changing.
And
I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
Regards
Manoj

got my solution...

Output purchasing document

Similar Messages

Maybe you are looking for