Purchase Requistion : Overall Release Problem
Hi everybody,
Have a peculiar problem where Item Level release seems to be working fine. And the first time we want to use release at header level and its not working.
The OverReqRel (overall requisition release) is 'checked' [at release group level].
There is just one class, one characteristic within that class (document type).
There is just one group, release code, release indicator and release strategy.
The classification has 'NB' as the document type to be controlled.
The simulation works fine.
The 'Check Release Strategies' shows 'all green' with no errors.
But when we create a PR (txn ME51N) for document type NB, this procedure does not kick in (hence i dont see a new tab at the header level asking for a release).
We have been using item wise release before and are testing the viability of release at header level.
FYI. This is a test system (sandbox) where we have NO configuration for release procedure. This is the first strategy that has been created for testing.
Any help in getting this to work is most welcome.
Hi,
For the document type NB, did you flaged as PR header level release.
Regards,
Ramakrishna
Similar Messages
-
Purchase Requisition Overall Release problem with several CostCenter
Hello Gurus!!
I need your comments!!!
I define the Purchase requisition as Overall Release, and woks !! but I have a Issue.
I have an entry in the CL24N txn as follow:
AccAssgCat = K
Plant = CC01
CostCenters = 10001
10002
10003
totalAmt = 1USD to 1000US
So when I create my purchase requisition with only 1 Cost Center the release strategy is called and PR can be released.
But When I create the purchase requisition with CC 10001 and 10003, the requisition is not subjet to release!!! (note TotalAmt = 15usd)
I assume that as both are into the release strategy the system will take both CC and ask for release!!
What I can do to fix this situation??Dear Marco Antonio,
I have never faced your issue, but have an idea of what you can do.
Activate Enhancement M06B0005 EXIT_SAPLEBND_004
Then in the program zxm06u31 put the following code line:
e_ceban = i_ceban.
and also a breakpoint so that it stops automatically upon PR verification or saving.
Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
Well, tell me what happens
Best Regards,
Sebastián Ligueros -
Purchase Requisition Overall release amount
Hi,
I am working on PR overall release amount workflow.
How can i find the overall release amount in the tables of PR while entering into the workflow.
Depending on this amount we need to further proceed for approval process.
Regards,
Gopinath Addepalli.Dear Marco Antonio,
I have never faced your issue, but have an idea of what you can do.
Activate Enhancement M06B0005 EXIT_SAPLEBND_004
Then in the program zxm06u31 put the following code line:
e_ceban = i_ceban.
and also a breakpoint so that it stops automatically upon PR verification or saving.
Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
Well, tell me what happens
Best Regards,
Sebastián Ligueros -
Purchase Requisition, overall release
Hi All,
I am using the overall release for my release groups. The releasing strategy depends on the cost center.
The releasing is workling fine so far, after I created a PR, the release tab appears in the header. BUT if I enter several items in one PR with different cost centers, the release tab does not appear. This also happens, if I enter 2 items with different cost centers in the PR and both of them are assigned to the same release strategy.
Are there any configuration in SAP to prevent this or do I have to use the itemwise release for that?
Thank you!Use userexit
Enhancement : M06B0005
Component : EXIT_SAPLEBND_004
CR : RDAK903063 SPOREDDY 04/05/07 changes to pick the release
strategy if all the cost centers are same for all
line items. Since the user Exit is activated the
program is forcing the data to go through import and*
field I_CEBAN-KOSTL is not blank the user exit is
filling blank values to E_CEBAN during export. -
Release of purchase requistion
Hi friends,
We have made our purchase requistion can't be released without Fixed vendor. We have made this for ME54N(Individual release of PR).
Users are smart enough to release them by using ME55(collective release of PR) without any fixed vendor assign to PR. How can we control this. PR can be released without fixed vendor.
We controlled it in MM54N.
How to control this in ME55.
Please any help ??
Thanks,
Bhairavhi,
just check by making the screen selection for PR Fixed vendor field mandatory.
I have checked without release strategy and in MRP system is not suggesting for Fixed vendor,(but with some other problem i am not able to activate the release strategy in my system) while ur going to change the PR then system is asking for the Fixed vendor and iam assuming that after the release strategy activating for PR that generated through MRP and while releasing in ME54 or ME 55 system will ask for the fixed vendor, then he can save that PR.
please check from ur end and please let me know.
Regards,
batchu -
Release Strategy - Purchase requistion go back to unreleased
Hi Friends,
I am facing two problem in release strategy in our client system.
Problem. 1:- Purchase Requisition changes( Other then the characteristics maintained) causing PReq go back to Unreleased.
Current System Settings;-
Release Procedure:- Procedure with classification ( Also setting available for setup procedure without classification maintained )
Characteristic maintained in class :- ( Plant, Value , Creation Indicator)
Value maintained in CL24N for plant , Creation indicator.
Release Indicator:- 1 Stage:- X. Blocked
2 Nd Stage:- 4.RFQ/PO no changes
Scenario :- When PR is created and released , If any one changes the Purchase Group in any line item which is not part of the release Strategy. Release strategy gets retriggered and the relase staus goes Blank for some case and for some case release strategy retrigger. My Question is if Purchase Group is not part of my release Characteristic then why release strategy gets retriggerd.( I used only purchase group here for Example, Any other changes also effect the release strategy to retrigger)
I checked all the system setting and it seems to be correct except when i use transaction OMGQCK to check PR release strategies, the log shows 3 errors of type:
Checks re requisns. with item-wise release 3
-> Checks re release group and release class 2
-> No release group exists 1
Problem. 2:- Purchase Requisition not triggering when PR is created from other source linked to SAP.
Please suggest the solution for the above problem.Hello Kunal,
A few thoughts and questions on your problem:
You generally can't have both release procedure without classification and release procedure with classification working at the same time.
To get the system with classification working, you have to have several things in place and consistent: You need a release group. It should have a class. That class should have all the characteristics you need to assign a strategy to every requisition (or item, if you're doing item-based release). You should use CL20N (or CL24N) assign values to strategies so that you have no possible cases where a requisition (or item) doesn't get assigned to a strategy.
You have to choose item-based or overall release for each requisition document type. You mark this on the document type. You must also choose the same option for the release groups that the document type will be assigned to. Example: document type NB is item-based. Document type ZB is overall. Document type will be a characteristic. CL20N will assign requisitions with document type NB to strategies in release group NN and requisitions with document type ZB to strategies in release group ZZ. Release group NN will be marked as item-based. Release group ZB will be marked as overall-based. Usually, I think, you will just use one or the other, and it will be less complicated, but the release group must match the document type.
The indicators themselves have some configuration, including a field for changeability. Your configuration defines the indicator assigned after a release, and that changeability field will determine whether the requisition can be changed and whether that determines a new release.
As Prasoon mentioned, if there's an enhancement active, that could affect things beyond configuration.
If you are using workflow, there might be custom events related to the business objects involved that can change things, as well.
Are you using workflow?
Are you using overall or item-based release?
Good luck,
- Jeff -
Problem in Purchase Requistion.
Hi Friends,
we have used the two BAPI' s for release the purchase requistion ME53N.
The frist bapi 'BAPI_REQUISITION_DELETE' delete the item of the purchase requistion , this one is working correctly.
the second bapi "BAPI_REQUISITION_RELEASE_GEN",
in debug mode the 2nd bapi successfully release the purchase requistion but it normal mode(with out the debug mode) it's not release the purchase requistion, we are putted the wait statement upto 2 seconds but still i am getting the same problem,
Can you please help me.
Thanks & Regards
CHARAN.Hai Please read given below Information and please read status in table requisitionItems.
This method enables you to list all purchase requisitions that have tobe released with a certain release code and group (collective release).
Notes
The authorization object M_EINK_FRG is checked.
Transfer
The release code must be passed on in the parameter RelCode and the release group in the parameter RelGroup.
The parameter ItemsForRelease determines whether only thoserequisitions awaiting release are listed, or only those that have
already been released. The latter is useful if you wish to have a listfor the purposes of cancelling releases that have already been effected.
Return
The result is returned in the table RequisitionItems.
Return messages
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. . -
Overall release strategy in purchase requisition
hi,
how do i configure overall release in case of purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics? is their required two seperate classes for item and overall release? i've allready chosen the field BSART and GSWRT for item wise release,
plz help me in details
regards
AniruddhaHi
For PRs, there are two types of release procedures available
With classification
With this we can release the PRs both items wise and in their entirety
Without classification
With this we can release only at item level
When you create the Release Group under the release procedure with classification
you check the box " ov Rel P Req (Overall release of purchase requisitions
This Determines that the items in a purchase requisition are all released at
the same time (rather than individually).
This should help to relsove your problem.
Regards
Vikrant -
PR Overall Release Strategy Problem
Hi Expert,
I have set the following
Characterisrtic Name:
1) ZPR_Release_Plant, Char : CEBAN-WERKS (Char format : 4)
2) ZPR_Release_DOC_Type , char : CEBAN-BSART (Char format : 4)
3) ZPR_Release_Pur_Grp, Char: CEBAN_EKGRP (Char format : 3)
4) ZPR_Release_Total_Value, Char: CEBAN-GFWRT (Curr format : 15 and EUR)
I assign the above to Class : ZPR_Overall_Rel
I created Release Grp R1 and assign the class and tick "Overall Release" checkbox. There is only one class, no others in the list
I created two Release codes, F1 - Senior Finance Manager, C2, CEO
I created two purchasing group, LLL and LYL
I used the standard indicators for S - block 2 - RFQ/PO and I created two release strategies A1 and A2 for Rel grp R1.
A1 - release Code: F1, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LLL
A2 - release Code: C2, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LYL
The problem is when I tried to created the PR, it doesn't work at all. No trigger whether I click the "check" button at the toolbar of the PR (i.e., the release strategy tab not appearing at the header). I also tried saved and display the PR and see if the Release strategy appears at the header but still not triggering.
Can you folks advise?
Thanks
LoForgot to check the box "Overall Release" forthe Nb doc Type. The problem is now solved.
-
Dear Expert
we are facing one problem in release procedure of PR previously we are having line item wise release of the purchase requisition now we have change it to overall release , but in that if there is a line item which have deletion indicator then we are not able to release the PR by ME55 , where as we can do the same PR by ME54N , i.e if there is a deletion indicator system is not able to release PR by ME55 . how can we sought the same problem
Regards
Edited by: usmfarhan on Nov 2, 2009 10:05 AMDear Expert
why collective release of PR not possible for overall release of PR if there is deletion indicator exist at item level
Regards
Edited by: usmfarhan on Nov 2, 2009 12:05 PM -
Why can we only use 1 release class for overall Release of Purchase Req?
Hi,
After realizing that it would be beneficial to use more than one release class for overall release of Purchase Requisition with classification, in use with release groups for overall release, I now ask if someone knows why SAP has chosen to only allow 1 release class for overall release of Purchase Requisition?
In my scenario I would like Release group US, used for release strategies for US-plant to be able to use 1 release class with a specific set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_USD including a characteristic PR_TOTVAL_USD looking at CEBAN-GFWRT. The chosen currency for this characteristic would be USD.
I would then like to allow Release group FR, used for release strategies for FRANCE-plant to use another release class with another set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_EUR including a characteristic PR_TOTVAL_EUR looking at CEBAN-GFWRT. The chosen currency for this characteristic would be EUR.
In this way the release strategies for the respective release groups US and FR, could maintain their overall limit values in their respective release strategies in their own currencies.
1. Observe that I do not want to use the same Release class for both release groups for overall release, even though I know that this is currently the only allowed option, as far as I've understood.
2. Observe that I do not want to specify the two characteristics PR_TOTVAL_USD and PR_TOTVAL_EUR for overall value in the same release class, as this would lead to double maintenance for a large number of release strategies. Also consider the maintenance when new countries with new currencies want release strategies.
3. Observe that I only want to use overall release.
What I'm trying to avoid is having to continuously translate local business USD overall value limits to limits in the currency chosen for the overall value characteristic. If this for example is specified in DKK, this would lead to a need to adjust the overall value limits as soon as the exchange rate between USD and DKK changes in the system.
Please consider this simple example:
Local requirement is that USD purchase requisitions should be blocked when the USD value is above 1000 USD. However in my release strategy I would have to maintain a value of >5365 DDK, if DKK is chosen as the currency for overall characteristic.(e.g exchange rate 5,365).
Next month the currency exchange rate in the system between USD and DKK has changed, and therefore I would have to go into CL24N and maintain the value to reflect the new exchange rate between USD and DKK. Lets say it has gone up to 5,435. I would now have to maintain a value of > 5435 DKK in my release strategy to correctly reflect the local business requirement of 1000 USD.
So if anyone could please explain why SAP has taken the decision to make the Release class for overall release client specific that would be much appreciated and awarded accordingly. Also if you have any suggestion on how I could obtain the above scenario on maintaning overall value limits in different currencies than that would be awarded to.
BR Jakob F. SkottYou can give feed back to Apple from the iTunes drop-down menu in the iTunes menu bar..
You can also contact the iTS Customer Service from the links on this page - http://www.apple.com/support/itunes/store/
MJ -
Purchase Requisition Release Problem
Hi All,
I have a release procedure set up, and the strategy pulls up correctly when a PR is made. When I view collective release from ME55, the PR's show up, and I am able to release line items from that screen. However, when viewing the PR from ME53N, in the Release Procedure tab there is no green check next to the release code with which to release the line. Also, if I do release the PR from ME55, I cannot go to ME53N and cancel the release from the Release Procedure tab.
I am a user with all security access, so it is not an authorization role problem. The release group is also configured to release by line item, so that is not the problem. I have set up other release procedures which allow the release/cancel release function from ME53N before... what could be the problem this time?
Thanks,
Jhi.
There are two ways of releasing purchase requisitions:
Individual release (Tcode - ME54)
You release items of an individual purchase requisition or - if the requisition has to be released in total - by releasing one item you simultaneously release all the others.
Collective release (Tcode- ME55)
You release all requisition items or complete requisitions that are awaiting processing by your release code. This is the preferred method if you frequently have to effect release.
Display PR -with release status (Tcode-ME53N)
One can only see release status in ME53N & can not change release.
hope it helps to you.
Regards,
Rahul -
Purchase Requistion release procedure
Hi,
Purchase requistion header level approval procedure activated. We required two level of approvals procedure based on total PR value range. Eventhrough i have maintained relase strategy its pulls always single stragey.
Do the needful.
Regards
MohanDear,
Have a look at:
http://www.scribd.com/doc/548510/SAP-Release-Strategy
Regards,
Syed Hussain. -
Purchase Requistion Release Stratergy
Hi,
I have a situation where I need to get the details of the classification Net total in purchase Requistion for the particluar Release Stratergy and Release Group from the relevant table for raising an event manually in work flow, which I am uable to trace out.Please help in this regard for identifying the tables which holds the data of the Net value for the same.
Thanks in Advance for your Help
Regards,
Krishna MukthineniHi Krishna,
the classifications of the release strategy is best read via the API (interfaces) for the class system. To get quick results and to check, if your designed process could be working at all, you could hard-code the class' name and it's characteristics. Later on -- to be more precisely -- you should read the class name from the customizing and the characteristic definition from the class system.
To get an example of how SAP determines the release strategy from the classification (which is kinda the other way round), you may consult the following function modules/coding sections:
Function module ME_REL_COM_STRATEGY_EBAN
--> Form strategie_neu
->-> Function module CLSC_SELECT_OBJECTS
To see the usage of this function module within your system, you could set a break-point there and create/change a requisition in your system.
The internal table iausp holds the values of the characteristics.
The referenced characteristic you'll be possibly looking for is based on CEKKO-GNETW
Best regards,
Florin -
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
Maybe you are looking for
-
How do you trap bad request exceptions
Hi, Can anyone tell me how to catch an exception from the page flow request processor. I'd like to be able to trap requests to invalid .do and .jpf urls. I have exception handling in my Global.app, but that only seems to apply to exceptions generated
-
I'm going to have to get my iPod fixed at a retailer store, but I don't know if I got the warranty. Does it come automatically or did you have to buy it when you got the iPod? And if you don't have the warranty, how much is it to get the iPod replace
-
HI i have iPhone 4s with iOS 8.1.3 , since 2 days I'm facing a problem that the ring tone,lock button sound,password sound,volume buttons,slide volume and incoming call flash, all these not working properly , sometimes it will work and sometimes it w
-
Text Messages Rebooting system
I am having problems with receiving text messages. Any incoming messages reboot my system. I saw the posting and solutions for other models, but wanted to be sure I am fixing it correctly for a 700P. I am trying to hotsync contacts and calendar wi
-
Formula for working out costs by hourly rates...
I have a formula currently which adds up all my hours in a column... I also want to have another formula that adds up all my hours and then multiplies the figure by 80 and gives me a result in dollar value... Any ideas anyone?