Me54 vs me54n
hi.
we have a purchase requisition release strategy and our 1st release is pre-requisit and any of the rest 7level/release code can release once initial release done.
(Once the release is effected by initial release code, any one from rest release code can final release the Purchase requisition)
my problem is like this.
Once the PR is raised & release by 1st release code and final released by 7th release code, PR is released for PO.
and in between if the requsitioner wants to change the PR qty, after final release, in me54n, he has to again approach to the person who has effected the final release for un releasing the PR. means he cant directly unrelease the PR using his release code.(initial 1st release code)
but if he usses the same in ME54, it is allowing to unrelease the whole PR by inital release code, even though the same is released by 7th release code.
can the same functionality beeing used in ME54N.
Hi,
Please check your release stratezy changebility & related authorization
Thanx
Reward if useful.
Similar Messages
-
hi all,
we are having a issue in pr , our user creats a pr and then due to
any reason close that pr but after the pr is closed we are able
to release it by me54 , we want to block this pr for release ,
is there any settings in customization we required to do for this,
i know abt the exit me_req_posted , but want to know abt any
customization settings.
thanks
regards
sarabjitHi Sarabjit,
I have found some very useful information regarding release strategy and deleted items, I hope it helps you:
Please consider the definition of ME55 "Collective release":
You release ALL requisition ITEMS or COMPLETE requisitions that are
awaiting processing by your release code.
And also the definition of "the field overall release of PReq":
Determines that the items in a purchase requisition are ALL released at
at the same time (rather than individually).
That means:
If there are some items which can't be released (may be they are
deleted), the transaction ME55 can't be used - so you have to release
over the individual release (and that's why you get this
message in ME55).
If you get such a message for a purchase req. in ME55 you can go over
the menue to release this item(so you don't have to call ME54 directly):
Select the item and choose Goto -> Individual release.
There is a difference between overall release and collective release.
Overall release means that a purchase requisition is released on
header level and not on item level. Collective release means that
several purchase requisitions can be released at the same time.
When one line of a requisition subject to overall release is deleted
you are asked to use the "single release" functionality in transaction
ME54.
Once you delete a line item you MUST work with ME54 to release each
item. By deleting a line you effect the whole purchase requisition
hence collective cannot be used. This is standard SAP functionality.
In this case, you have to individually release each requisition item
through transaction ME54.
Please also consider
1.Once an item is deleted in a purchase requisition which uses an
overall release strategy this document can't be released anymore
using ME55. But ME54 or ME54N could release it.
If the PR only contains the deleted item, it can not be released in
ME54 either. But it could be released in ME54N.
2.If the requisition is flagged closed before the release is performed
the requisition does not appear on transaction ME55. The system does
not display the closed Purchase Requisition in overall release ME55.
But it could be released in ME54 or ME54N.
Best Regards,
Arminda Jack -
ME55 error - Release via individual release
Hi I have a question,..
We are using overall release strategy.
Now I have 2 line item in a same purchase requisition, and when run ME55 it show me the message "Release Possible".
Then after that, using ME52N we change the requisition and cancel 1 of those items, of couse a new release strategy was defined by the amount we defined.
But now, when go to ME55 now the messahe said "Release via individual release"... ann with ME55 cannot be release.. I need to go to ME54 and ME54N.
Do you know why SAP do that? what is the reason of this?Dear,
As available in SAP NOTES 668940
Program error.
This problem occurs after deleting one item of a purchase requisition. The consequence is that all documents created afterwards will no longer be releasable via ME55.
Check the corrective information.
Please also check: Note 69792 - ME55->ME54 Changes from ind.release updated wrongly
Note 92315 - Call individual release - call transaction
Note 72100 - Individual release - only allowed items
Regards,
Syed Hussain. -
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. -
Purchase Requistion Release Reset by ME54n & ME54
Dear all
Once PR is created, then Released by ME54n or ME54, then RFQ is processed wrt PR, then after if user want to reset release by ME54, the system prompts error message and not allowed reset release. BUt if user use T-code ME54n, the system allows to reset release.
we need, the system should not also allow to reset release for T-code ME54n.
Please suggest solution
Thanks
RSDear Vivek,
I raised this to SAP and got reply from SAP.
===========================================================================
ME54N allows the user to unrelease a purchase requisition linked to a
purchase order or a request for quotation. Please see following
attached note 686022 which explains this behavior.
Symptom
You create a purchase order (or a request for quotation) with reference
to a released purchase requisition.
If you use ME54N to unrelease the purchase requisition, the error
message ME110 (or ME109) is not processed.
Reason and Prerequisites
ME54N allows the user to unrelease a purchase requisition linked to a
purchase order or a request for quotation. This is correct behaviour andconstitutes a new design.
The following modification keeps the old functionality (ME54) available.You have to customize message ME110 (or ME109) as an error message.
After pressing the cancel release button, the system will process an
information message (ME110 or ME109) and the release will not be
cancelled.
If you want to use the old functionality in ME54, you can implement the
modification as note 686022.
Hope this informatoin will be helpful.
===========================================================================
Can you suggest, the error settings is already there and its trigger only for ME54, and not for ME54n
AS per the reply from SAP, can advice me on this
As per your previous reply, i got basis team and authorization team, to whom i need to ask to set M_EINK_FRG for ME54n?
Thanks
RS
Edited by: Ramapuram Saravanan on Feb 16, 2009 6:05 AM
Edited by: Ramapuram Saravanan on Feb 16, 2009 6:06 AM -
ME54/ME54N Conditional check for Release of PR
Hi Gurus,
My requirement is to put a check on the release of the PR with respect to the cost center present in the PR. The user who is authorized for that cost center can only release the PR.
For the above requirement. I have implemented the user exit MEREQ001->EXIT_SAPLMEREQ_005.
This is working fine for ME54N transaction, however it is not working for transaction ME54. Please suggest any user exit which I can use for the above scenario.
Thanks!
AshuUsed this exit, Restricted the user access for PR release to ME54N only.
-
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 PMOne 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 -
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 CavalleriHey,
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. -
How to call smartform in me54n
Hai All,
Iam developing a smartform for PR print with ztcode,the user asked me that,he dont want seperate tcode,in me54n tcode itself he want
print.I have tried in the enhancement spot but it is not firing.
Regards,
Siva jyothi.Hi ,
The print button creates a spool number through which you can get ALV output of the ITEM details but cannot call smartform from that.
PR is just an internal document.There is no other way to do it(As far as i know).
You now have only two options to go for:
1) Create a subscreen with a pushbutton , and then call the driver program to print the smartform.
2) A Z transaction to print the PR , which you have already done.
Let me know if you find any other way to do it.
Br.
Giri -
Authorization object to control plant code in ME54N
Dear All,
Problem: Restrict user "PURAUTALL" userid to release PR's in ME54N for plants "5350" & "5360" only but should be allowed to create/change/display PR's for all other plants including 5350 & 5360.
Analysis: Object M_BANF_FRG is used to control releasing PR's using release codes but how to link up plant codes
Setup:
PURAUTALL userid has access to create/change/display PR's for all plants - M_BANF_WRK is *
PURAUTALL userid has role same as user id but does not contain object M_BANF_FRG in PFCG
Kindly provide suitable solution &/or process to create object M_BANF_FRG in PFCG.
Thx & Reg
BhushanHi Julius,
Thx for replying, actually we havent tried any options because it seems to be a release strategy issue. As of now, thinking to create the object M_BANF_FRG in PFCG and then linking release codes.
But before that business needs to decide to create new release strategies / codes based on plant as characteristics.
If this correct, if any other way out pls help.
Thx
Bhushan -
Error at the time if cancellation of PR release thorugh ME54N
Hi,
While cancelling the release thorugh ME54N transaction we got following error;
"No new release indicator can be determined"
Message No: ME108
Please advise.
Thanks
shpHave, in the meanwile, you changed the previous release strategy? so the system cannot determine any
-
Default Screen Selection for ME54N to Account assignement tab
HI, gurus
I am creating a PR with acct assignement category as 'N'.
after creating PR when i goto ME54N (release) , the PR is automatically to going to the item details of contact person but the user wants account assignement to be considered .
so pls can u guide me in this regard.
regards,
rajashekarHi Venkat,
Thank you for your reply!
I've checked note 1308330 and we've implemented it. But it didn't help unfortunately.
I've tried to find variable gv_initial_category but there is no such variable in class ZL_BP_HEAD__MAINSEARCHSHU_CN00 (resp. CL_....).
I did find a variable called gv_category in class CL_BP_HEAD__MAINSEARCH_IMPL. But it's protected. And to be honest, I wouldn't know how to set that variable from GET_CATEGORY of class ZL_BP_HEAD__MAINSEARCHSHU_CN00.
However I did find out what messes up my result, thanks to your hint.
It happens in method DO_CONFIG_DETERMINATION of class CL_BP_HEAD__MAINSEARCH_IMPL. There it checks if the global attribute gv_category is different from the category from the "shuffler" object.
It does this when the page is loaded resp. reloaded (so before searching and after every search).
And after the very first search I will end up in this method and gv_category will be initial and the shuffler category will be set to '2'. And in that case, all search terms and the result lists gets cleared.
So now I know where it happens. But I still don't know how to fix this.
I've tried to change in method IF_BSP_MODEL~INIT to set the collection_wrapper with category = '2' but that still didn't help. For some reason, when the method DO_CONFIG_DETERMINATION reads the shuffler collection, that one returns an empty category. If I would get '2' there, then gv_category would also become '2', before I even searched. And that would work... But no matter what I do, I don't get '2' from the shuffler object.
Anyone got ideas?
Best regards,
Melanie -
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,
johnsonTransaction 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 -
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
AugustoHi,
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 -
ME54N :How to block/disable/remove the "PO" indicator
Hi,
In the PR release screen (T code: ME54N) we want to block / disable the "PO" indicator in other purchase requisition icon (Shift + F5)
How this can be done?
Regards,
SumitHi
check this
Enhancement
MEREQ001 Customers' Own Data in Purchase Requisition with help of ABAP consultant
or Take a help of ABAPER for stander program changes If possible
but why you want block / disable the "PO " indicator in other purchase requisition icon ?
Regards
Kailas Ugale
Maybe you are looking for
-
Task rule resolution not working
Hi Experts, I have a created a rule in PFAC to determine possible agents for a task. I have assigned the same under "default rules" tab of task configuration. Rule container, binding between task container & rule container is also correct & in place
-
HT1977 How do I transfer my purchased iTunes apps and media to a new computer?
I bought a new computer, and I wanted to download iTunes and start using it to manage my library. Do I have to transfer all purchased apps to the new computer, or will iTunes do that automatically for me when I sign into my account on the new comput
-
Wrong taxes while issueing credit note to customer
Hi, We are using FB75 to create credit note to customer as we charged excess amount in original service tax bill through oversight. Invoice details are as below. Basic Cost 1,75,000.00 Service tax 10.3% - 18,025.00 Total
-
Question on Installing Reporting Services and its Databases ReportServer and ReportServerTempDB
Is it possible to have the Reporting Services installed on one server\machine and the databases ReportServer and ReportServerTempDB on a different server\machine? I have always installed both on the same machine but this architecture is being suggest
-
Can anyone explain "ignore previous" feature of Wait on Notification function?
Can anyone explain "ignore previous" feature of Wait on Notification function? I have read the help description and other material and I just don't get it. Reference to any good articles I can read will be appreciated. Thanks in advance.