ME54N and ME55

Hi all,
I have 1 questions:
When we release the PR using ME54N or ME55, if we want to pop-up a window to remind user to get the off-line approvel, how should I do? I mean what are the user exits for the two transaction code?

The user exit is not OK.
If i click the cancel button of the pop-up window, I want the PR will not be released.
I am looking for the SAP implicit enhancement. If anyone know the place of hte enhancement, please let me know, thanks.
Edited by: yu huali on Sep 18, 2009 2:44 PM

Similar Messages

Save on user-exit for ME54 and ME55

I am stuck in ME54 and Me55. I have to find a save on user exit while releasing through this transaction.
The requirement is to validate the release code and its corresponding approver.
When save and release button is pressed then this exit should trigger.

I have created one project and assigned the user exit that you suggested, and activated the project and exit.
I have put a break point in the exit to ensure that it works or not.When trying to execute the release and save button(me54) it does not stop at that break point.
Can you please tell me in detail that how to achieve it?. Is there any configuration to be maintained?.
Since it suggests that against that release code the workflow indicator should be 9.Please suggest.
If there is any other way round then also let me know.

ME54 and ME55 user-exit

Hi all,
we are on R/3 4.6C. We need to insert a custom authority-check in ME54 and/or ME55.
This because we need that each user can release only PR created by him.
With user-exit MEREQ001 we were able to reach our goal in ME52N and ME53N. Unfortunately MEREQ001 is not working for old (not enjoy) tcodes (ME52 and ME53).
Since ME54 is an old tcode, probably it works as ME52 and ME53: MEREQ001 is not relevant for them. In 4.6C ME54N does not exist.
Any idea for insert an authority-check in ME54 anr/or ME55 ?
Thanks in advance
Andrea Cavalleri

Hey,
Did you find any solution to the problem? I am facing a similar situation in 4.6C and cannot find a user exit/BADi that gets triggered for ME54.

Badi/user exit in tcodes me54n,me55,me28 and me29n

hi all,
1.which is the badi/user exits that is there in me54n and me55...for saving and releasing purchase requisation(s) .
2.which is the badi/user exits that is there in me28 and me29n...for saving and releasing purchase order(s) .
points will be rewarded.
regards,
johnson

Transaction Code - ME54N                    Release Purchase Requisition
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
Transaction Code - ME55                     Collective Release of Purchase Reqs.
Enhancement
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
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
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
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.
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
M06B0003                                Number range and document number
Business Add-in
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
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_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
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_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
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_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
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)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
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
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation

Report on PR Release Strategy

is there a list/report of all PR released and by who is SAP?

Hi,
If you want the release ID, then you may check AUT10 transaction. Go to AUT10, press F9 and then enter the following:
Transaction code: ME54N and ME55
Table Name: EBAN
Table Field: FRGZU
Enter the date range if required and execute:
Output:
Regards,
AKPT

PR release refused for 7 lines out of 8 line item for header level released

Hi Gurus,
please help me how to resolve this issue.
i have purchase requestion with 8 line items,out of 8 line items line 5 gets relesed and other lines relese refuded mode.
i have checked the complete procedure,authorisations and tried through ME54N and ME55 also.
please help me , thanks in advavnce.
Regards,
Babu

hi
please check the line items whether its blocked or deleted or value and quantity fields are updated.

Approvers name to appear at PR release strategy

Dear gurus,
I have configured the PR release strategy. In customizing, I assigned the Release Codes to the '(S) Position' Agent ID's. Everything is working fine.
Here is the issue, my client would like to see the name of the person who is supposed to release the PR. The client understands that the customizing wasnt done by assigning the Release Codes to the 'User' Agent ID's. However, the client would still like to see the name of the person who is supposed to do the release.
Is there any way I can bring the Users name at the PR release strategy at transactions ME53N, ME54N and ME55 ?
Thanks in advance.

The idea of changing the Release Code to the name of the person assigned to a Position will work if you have a very stable organisation and only ever have one person assigned to a Position.
Do you have that situation ?
Otherwise it's a development e.g. speak to an ABAPer.
Regards,
Nick

Entire Result of MRP in one screen

Hi,
We need to see the entire result of MRP (Purchase Requisition, Planned Order, etc.) with Material no. after carrying out MRP for whole plant in MD01.
Can any one suggest how to check this?
Thanks in advance

The result of the MRP-run will be visible in SAP as planned purchase-requisitions, planned production-orders and action-messages in T-code MD06. For larger organizations it will be inefficient (and rather unusual) to have their MRP-results in a one-screen overview. Through their relation with a material-record, the planned purchase requistions, planned production-orders and the exception-report-messages will also be tagged with the MRP-controller code (The MRP-controller is the responsible for the follow-up actions on the outcome of the MRP-run for a group of materials).
The MD06 exception-report shows traffic lights and "exception group-codes" per mrp-group/plant/material/mrp-controller/vendor to indicate which action need to be taken (other selection-restrictions are also available in MD06). A drill-down on the materialnumber will bring the information of MD04 and will give access to stock-information / purchase-requisitions / open purchase-orders / planned orders / production-orders. T-code MD06 provides an action-list for the MRP-controllers / procurement-officers / production-planners. The MRP-Controller will decide to release the planned requisitions (for purchase-items)/ release planned production orders (for production-items) and will take action upon the information in T-code MD06 to expedite, postpone, change or cancel material-requirements. SAP allows an individual release of planned purchase-requisitions with T-code MD14; T-codes ME54N and ME55 support collective releases of the purchase-requisitions.
The release of individual planned production-orders can be done in T-code CO02 (or as a drill-down from report CO26 to CO02 )
A collective planned production-order release can be made with T-codes COHV and COOIS.

View user who released Purchase Requisition

Hi,
Where can one view the name of the user who released a purchase requisition?

Hi,
If you have item wise release strategy, then select the particular line item and then click Environment in the menu tab, then select item changes. You will find the name of the person who had released the PR at all levels.
If you have overall release strategy, then select the first line item and proceed as above.
If you want to make any report for this, then use the table CDHDR, where field value OBJECTCLAS should always be BANF, field value OBJECTID should be your PR number and field value TCODE should be ME54, ME54N and ME55. If PR release will happen through workflow, then combine the tables CDHDR and CDPOS with respect to the change in field FRGZU
Regards,

Problem in ME55 in SAP ECC 6.0

Dear All,
I am facing a problem in ME55. If I specify the Purchase requisition no in ME55, then Release can be possible for 1st Release Code. But when I remove Purchase Requisition no from ME55, then system shows "No Record found" for same release code. Any explaination for this.

hi,
1. check your variant settings
2. check whether that PR has been already released by the release code for which you want to process.
pl go to ME54N and check rightnow status of PR for release.
Arul

Batch Release of PO and PR

Hi,
I have created workflows for PO and PR release. I used the method Single Release for both.
Is there a way that my workflow will go directly to tcode me28 instead of me29n, and me55 instead of me54n? We would like to do this for collective release of PR and PO.
Appreciate your help..
Regards,
Paula

you can use Release method which is avilable in BUS2012 and for PR also you have this method.

Budget compromise by releasing requisition purchase order (ME54N)

hello Experts, please a consultant
It is possible to configure in FM for the budget compromise at the time of the release of the requisition (ME54N) and not when creating the purchase requisition (ME51N)?
greetings and thanks for the suggestions
Augusto

Hi,
Do you mean consume the budget at the time of release and not on the creation? It won't be possible, due to prudence policy in PSM-FM. Imagine, creating a lot of PRs, which won't have effect at the budget and the lack or resources will be discovered only at their release.
Of course, by modifying standard code, in theory, you can force this kind of logic, but I won't recommend it both from technical and functional reasons.
Regards,
Eli

Error in the strategy of Liberation, ME51N - ME54N

A request becomes of order, with transaction ME51N, mounts correctly a liberation strategy.
Soon, one would go away to the ME54N, to release it individually, and it unfolds the error to me (Purchase requisition XXXXXXXX cannot sees released, Message no. MEPO822)
That it could be happening ?
Edited by: Nacu on Feb 5, 2009 9:25 PM
Edited by: Nacu on Feb 5, 2009 9:52 PM

One has tried on with user SAP-ALL, reason why discards a permission subject or profile, also has been written one to SAP, which responded that the last version of note 939371 was applied, which this applied, the certain thing is that the strategy is mounted, works in simulation in the SPRO, but it allows me to make the order of purchase WITHOUT RELEASING IT, it does not allow to release it me by transaction ME54N and if it allows to release it me by transaction ME54 ????
Thanksu2026

Authorization check for ME54N v/s Authorization check for ME54

Hi,
We have created th PR and release it, with reference to PR we have created the PO. When we try to revoke the PR releas using the t-code ME54 systems gives me a error message, that PO is already created for this PR.
however, if i try to revoke this pr using ME54N system allows me to revoke it.
My requirement is that the user should not revoke the Pr once the PO is created against this using t-code ME54N. is there any authorization check or object to control the t-code ME54N.
Regards
Ajit

>
Alex Ayers wrote:
> Why do you not remove access to ME54N if they are supposed to use ME54?
I apologise, Alex - but I do not think that is a good advise. ME54 N is there for a reason. It will one day substitute ME54 and anyway, changes bugfixes etc may no longer be developed for the 'old' transaction.
Futhermore: compensating lacking functionality or a bug with withdrawing authorisations to the new functionality is -if any- a temporary option only. The OP's phenomenon has to be solved sooner or later.
So my advise would be:
First check in SMP whether one of the several notes on ME54N and 'release' applies to your system/version/process.
Consider opening a call with SAP.

Running ME54N transaction through shortcut.sap file

Hello All
I need to start transaction ME54N running *.sap logon file.
I do use here parameter - command=*ME54N.
The problem is that I have to run it with specific requisition number according business process.
I mean that one time I have to run it with requisition 1111 and next time with requisition 222 and so on.
If it will be program code I should run command like set parameter id 'BAN' field 1111 and
then call transaction ME54N and it will work.
But here in *.sap command parameter I can't find the option or right syntax how to run in with a parameter.
I tried some think like
command=*ME54N set parameter id 'BAN' 1111
    command=*ME54N mepo_select-banfn=1111
and so on, but nothing helps.
Could anyone to help me, please ?

Hi Daniel,
I forgot to say that you need a Z-transaction Code for the Report then you could do the command as you discribed with the parameter:
Command=*/ICSOFT/ME54N PA_BANFN=450017
this would work. (I did it some years ago)
If you create emails with cl_bcs though I would suggest another solution that i did with quotations, but should work for requisitions as well:
data: ls_bor          TYPE soxobj,
         lt_bor          TYPE soli_tab.
* Business Objekt anfügen
       ls_bor-objtype = 'BUS2031'.
       ls_bor-objkey = salesact_data-vbelv_sd
       ls_bor-describe = 'Anhang'.
       APPEND ls_bor TO lt_bor.
       CONCATENATE 'Angebot: ' salesact_data-vbelv_sd INTO lv_subject.
       document->add_attachment( i_attachment_type = 'OBJ' i_attachment_subject = lv_subject i_attachment_header = lt_bor i_attachment_language = sy-langu ).
* Absenden
       send_request->send( ).
This is not as much work for you and much more convenient for your client.
He can open the link in the mail from swbp or he could open it as a webgui transaction from any other email client ( outlook etc.)
hope this helps
Werner

ME54N and ME55

Similar Messages

Maybe you are looking for