ME51N: Print out for Purchase Requisition

Hi ABAP-developer,
I looked within the forum for a customer solution to print out a purchase requisition (no export to Excel or list printing!). Because the PRs are internal documents there's no standard solution for this. Do I need to copy the formular MEDRUCK and the driver print program SAPFM06P? Could anyone help me with the source code and further information to this topic? Thanks in advance!

Dear K.K. Chiluka,
I was conscious about creating a new driver program, but your answer isn't as clear as I exspected. It's clear that I have to program the source code for selecting the EBANs and that I need a new formular (smart form) for printing. But how does the source code look like, what kind of 'CALL FUNCTION's do I need (WRITE_FORM for printing the textelements within the formular and others)? It's similiar to ME9F but could you please give me a more detailed answer. Thanks a lot!

Similar Messages

Print Out of Purchase Requisition

Dear SAP Experts,
Is there any way to take print out of Purchase Requisition.
Thanks in Advance.
Ishu

Hi,
In standard SAP, there is no option for printing Purchase Requisiiton. This is because, PR is treated as an internal document.
You may do customization for this. Consult your ABAPer for this.
Regards,
Prashant

Restrict print out of Purchase order only for Production system

Hi,
I want to restrict print out of Purchase order only for Production system, don't want to take it in devep or quality.
is there any identifier to find the system is production or development.
can anyone tell me how to restrict it,
is there any function module, not based on client system.
Thanx in advance
Kesav

Hi Kesavarathinam Vaidyalingam ,
yes, I also use thomas' suggestion using
t000-cccategory = 'P'.
to determine productive client.
Just one small hint: I found this condition as true in a test system: The admin had done a system copy to create a fresh test client - but forgot (or did not see a good reason) to change t000-cccategory = 'P. to t000-cccategory = 'T'.
Regards,
Clemens

Customer Subscreen for Purchase Requisition

Hello All,
I need a custom subscreen on requisition at <b>HEADER</b> level. 'MEREQ001' adds a screen at item level. Is there any Screen Exit / BADI to add a custom screen at header level? Any kind of help is really appreciated.
Thank you all,
Chandni

Hi Chandi Reddy,
The t.code is ME51 For this available exits are :
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
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., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
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 P
MM06E008 Monitoring of contr. target value in case of release or
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 proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
For t.code we51n the available exits and badi are :
Enhancement/ Business Add-in            Description
Enhancement
MEREQ001                                Customers' Own Data in Purchase Requisition
Business Add-in
ME_COMMITMNT_PARKING                    BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING                        BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT                      Copy Header Text: Enjoy Purchase Requisition
o.of Exits:          1
o.of BADis:          3
Rewards some points.
Rgds,
P.Naganjana Reddy

User exit/BADI for Purchase requisition through release of Process order

Hi ,
i need to add some text to the Pur Req.
The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
regards

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
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
MM06E011                                Activate PReq Block
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
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
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
Business Add-in
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED                      Purchasing Document Posted
SMOD_MRFLB001                           Control Items for Contract Release Order
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
Reward points if useful
Regards
Anji

Regarding report for purchase requisition

Hi gurus,
      I am preparing a report for purchase requisitions using SQVI. I am almost done with it but I was stuck at one thing. Our client criteria is to see it by name like they wanted users to view only purchase requisitions they created. They dont want all users to see purchase requisition created by other users. I dont know how to do that. Can anyone help me out with that.
     let me know if I am not clear about anything.
Thanks in advance.
Ravi Teja Boppana

Hi,
      I added the field ERNAM from table EBAN. But the problem I am facing with it is any user can enter any user name in that field. Either I need that feild to be filled automatically with the username who logged in so that I can hide that field if that can be changed or filled automatically and cannot be change by user. Is there any option I can do like that. If I create a report in SQVI no one else except me can see that report, so I need this report in that manner.
      Let me know if i am not clear,
Thanks in advance,
Ravi Teja Boppana

AME for Purchase Requisitions

Hello All
I am in the process of setting up AME in R12.1.2 for purchase requisitions and got struck with an issue
My requirement is to route the requisition to a particular job based on the item category and the requisition total. I setup conditions, action types and approval groups and then the rule.
When I used static in my Approval Group setup it works fine with out issues however we do not want to use static as employees keep changing and want my approval driven out of the job hence updated the approval group to use Dynamic usage type and used the below query to pick the name of the employee based on the job.
select papf.full_name from per_all_assignments_f paaf, per_all_people_f papf, per_jobs pej where
paaf.person_id = papf.person_id
and sysdate between paaf.effective_start_date and paaf.effective_end_date
and paaf.job_id = pej.job_id
and pej.name like 'IT.Group IT Operations Manager.Staff'
Now when trying to create a requisition it shows up a message that "Approval List could not be generated. Please contact your System Administrator to review AME rules setup."
When validated the above query it says query is valid but still not working. I even tried with person_id but still no luck
Thanks a ton in advance
Regards
Dilip

Hi Dilip,
Pl. visit following links.
AME for iProcurement requisitions
Re: AME-Hierarchy Deciding Feature ?
HTH
Sanjay

BADI for Customer's own screen for Purchase Requisition.

Hi All,
I have a requirement where I need to create a BADI implementation for creating addition screens in the Purchase Requisition Transaction (ME51n/ME52n/ME53n).
I know there are User exits but we donu2019t want to implement them. Now in case of PO there is a standard SAP given BADI -> ME_GUI_PO_CUST for Customeru2019s own screen but as far as my understanding goes there are no such BADIs for Purchase Requisition.
Could anyone please advice if I can create a Custom BADI similar to ME_GUI_PO_CUST for PR for adding the screen and throw some light on it like how can this be achieved?
Thanks,
Ameesha

Thanks Darek for replying back and the BADI ME_BAPI_PR_CUST looks helpful but could you please help me in understanding how can i create my own custom screens within ME51N / ME52N / ME53N tcode using the BADI , ME_BAPI_PR_CUST.
For example in PO, we have the BADI ME_GUI_PO_CUST, with several methods like SUBSCRIBE and others which we can make use of for creating screen exits but what in the case of PR fpr BADI ME_BAPI_PR_CUST. i couldn't find any sample code for implementing this.
Any help is greatly appreciated.
Thanks,
Ameesha

Budget Approver for Purchase Requisition

Hi,
In MM setup for purchase requisition, 4 levels has been setup for approving based on amount. The person who will approve is configured to be determined based on user exit (value - 9) in TCode OMGQ.
My question here is where is this user exit and how can we know to whom this PR will actually reach for approval.
Please help me out.
Regards,
Binay Agarwal

That you have to check in the Workflow settings based on the organization defined in PPOME
User exit M06B0001
you ca check the logic of user exit in SMOD
enter the above user eixt and display the component logic

Header Noe for purchase requisition

Hi,
Can anyone help me for maintaining the header note as default,so that the note will come whenever someone enters into ME51N.
How to maintain the header note for purchase requisition as default for a client.
Thanks in Advance.

hi,
Check this BADI...may be useful to you
ME_REQ_HEADER_TEXT "Copy Header Text: Enjoy Purchase Requisition
Thanks & Regards

What is the standard print prg for Purchase Order

Hi,
I am working on forms, what is the standard print program for purchase order.
Already i have gone to nace and found that the program assigned to the customized print prg, so i am not able to find out the print program, so can u tell me how to solve it.
Regards,
clara

Here are the default entries in the configuration
NEU     Purchase order     1     SAPFM06P     ENTRY_NEU     MEDRUCK
NEU     Purchase order     2     SAPFM06P     ENTRY_NEU     MEDRUCK
NEU     Purchase order     6     RSNASTED     EDI_PROCESSING
NEU     Purchase order     A     RSNASTED     ALE_PROCESSING
Regards,f
Ravi
Note : Please mark the helpful answers

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

Is it possible to define a seperate number range for purchase requisitions

Hi Experts,
Is it possible to define a seperate number range for purchase requisitions that come from Forecast vs normal MRP requisitions so that our purchasing department can identify the origin of the document?
Thanks
for the thoughts
Sreeni

You'd need to figure out manually how forecast PR's are different from MRP PR's (the field from PR tables ) and then in the user exit I mentioned the program looks at the table T161 and field NUMKI, and if the PR getting created is from forecast change that NUMKI in the program to a different one else keep it as it is. If you're know abap programming it won't take long to figure out the logic else work with your developer to implement it.

HT204088 how do i print out my purchase history in itunes?

how do i print out my purchase history in itunes?
i can get it up on the screen but I cannot copy and paste it and it wont print (only as a blank) etc....
how can I do it..I do not want to print out 10 emails instead of one full purchase history
thanks!!!
julian

You should have received emailed receipts for each item that you bought from the store. If you haven't got them then all that you can do is take screenshots of your purchase history.

HT204088 How do I print out my purchase receipts from iTunes?

How do I print out my purchase receipts from iTunes? I have some things that are tax deductable.

You should have received emailed receipts for each item that you bought from the store. If you haven't got them then all that you can do is take screenshots of your purchase history.

ME51N: Print out for Purchase Requisition

Similar Messages

Maybe you are looking for