Issue with Purchase Requisition Release strategy

Hi Gurus,
We are using ECC 6.0.For the approvals of purchase requisitions, we are using standard SAP functionality of release procedure. There were some 52 release strategies configured for the PR .The release strategy was based on value of the following fields that is below were characteristics grouped together for class for PR:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group
3.     Value of the PR
As a result of PM module implementation, there is requirement of additional 30 release strategies.
We configured them but one more field of doc type was added in the characteristics fields.
Now the release strategy was based upon following fields:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group-(Configured against new purchasing groups )
3.     Value of the PR
4.     Document type of purchase requisitions.
Classification data was accordingly maintained that is for older release strategies,
Old PR doc. Type: NB was maintained where as other values were same. For new release strategies, new PR document types:NB1-NB6 for Doc type have been maintained .
The above set up worked fine for some time. But suddenly, none of the PR release strategies are working. I checked all the related configuration settings and all look fine. I also checked my release strategies in tcode: OMGQCK. But no error was there.
Could any body help in finding the reason why PR release strategy stopped working all of a sudden? What could be the probable reasons? What should be the approach to resolve it?
We are in testing phase. Many of the test scripts failed due to this issue.
Quick response will be appreciated!!!
Thanks & Regards,
Niti

Dear Niti,
Please check if your "overall release" indicator is consistent for document type and release group:
a)SPRO:MM-PUR-PR-Define Document Type
"overall release" indicator
b)SPRO: MM-PUR-PR-Release Procedure-Set Up Procedure with Classification
->Release group
"overall release" indicator
Regards,
ian,Wong Loke Foong

Similar Messages

Issue with Purchase Requisition Release Strategy (Approval)

Hi There,
I am facing an isssue with the PR Release Strategy. Please read the description below.
When a PR is created the PR Release Strategy is getting determined correctly. But the problem is that for example, if the Strategy has found a two level approval, the system is allowing level 1 user to approve both the levels, which should not be the case. User 1 should be allowed to approve only Level 1.
Though the system is currently allowing the same user to approve both the levels. If User 1 approves only Level 1 and saves the PR then the PR approval notification goes to User 2. So there is nothing wrong with the workflow or notification.
It is just that system is allowing the User to approve both the levels.
Any help is appreciated and rewarded.
Thanks,
Chan

Hi,
I believed releases strategy correctly designed with release prerequisites.
Now need to check following in basis side by having a purchase order release matrix.
Lets say you have following release codes
C1 & C2
AND
Having following users
U1 & U2
Now give authorization to user U1 to release with release code C1 and user U2 to release with release code C2 ONLY.
Regards,
Biju K

Issue in Purchase Requisition Release Strategy

Hi guru,
I've got an issue in the release strategy;
I have a PR with 3 lines. After Relase I've deleted the last line and system doesn't allow me to release it by ME55 transaction; I'm able to do it only by ME54N.
Thank you for your help.
M.

Hi Marco,
I had a problem with ME55 and i wrote to SAP OSS.
The first OSS answer was:
Can it be that your requisition has some deleted items?. If yes, then
take into account the following:
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 menu 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.
I hope this is useful to you.
Ciao
Alberto

Tranposrt - Purchase Requisition Release Strategy with Classification

Gurus!
Tell me if I want to Transport the Purchase Requisition release strategy with classification. The Data in each charisteristics in each PR Strategy that I have set in Dev is not getting transported to Quality.
Do I have to enter the data in characteristics again in Quality and the same procedure I have to apply for Production.
If yes, in this scenario, Can I make Production modifiable.
Regards
Sajid

Hello,
Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
Cheers !

Purchase requisition release strategy tab missing

Hi all
I configured purchase requisition release strategy and ME51N is working issuing no error but it is not displaying Release Strategy Tab , please help me where i am wrong.

hi,
check few reasons:
1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
2. check the release strategy OMGSCK, is there any problem with your release strategy...
3. Check whether you have maintained all the classified field in the document or not..
4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
regards
Priyanka.P

Badi for Purchase Requisition Release Strategy

Can any help me to know about the BADI for Purchase Requisition Release Strategy .Is their any BADI to control the PO Price for a PR release strategy
Thanks for your help

This badi is for schedule agreement ?
BAdI: Release Creation for Scheduling Agreements with Release Documentation
Use
You can use this Business Add-In (BAdI) to influence release creation.
This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).
This BAdI includes the following methods:
Change Data Before Release Creation (BEFORE_CREATION)
Change Data After Release Creation (AFTER_CREATION)
This BAdI is called during manual and automatic release creation.

Overall Purchase requisition Release strategy : Changed after Rejected

Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.

Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev

Purchase Requisition Release Strategy wont trigger

All:
I have set up what i thought was a simple purchase requisition release strategy. Parameters are as follows:
1.) Doc Type = NB set up as CEBAN-BSART
2.) Acct Assn Category = k set up as CEBAN-KNTTP
3.) Purch Org = 300 set up as CEBAN-EKORG
4.) Overall Value = 0-1000, 1000-10000, 10000-50000, >50000 set up as CEBAN-GFWRT
Release group is set for overall release, i've checked the release strategy with OMGQCK and everything was good to go, checked CL30N and everything was triggering, checked table T16FS and there weren't any fishy entries. Oh also, i've tried deleting and recreating the entire release strategy at least 3 times.
Whenever i create a purchase requisition, i get no release tab. Not sure what else i'm missing here.
Any help is appreciated!

I created 4 characteristic with the above mentioned criteria (doc type, purch org, net value, & account assignment category). I assigned all 4 of these characteristics to a class.
Matrix is as follows:
0-1000, doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01
1000-10000 doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01 & 02
10000-50000 doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01, 02, & 03
>50000 doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01, 02, 03, & 04

Problem with purchase order release strategy

Hi Guru's
    i am dealing with problem of service purchase order release strategy , when i making the service po , i am not giving any over fulfillment tolerance , after release & making Service entry sheet of PO ,   when i go to the change mode and change
over fulfillment tolerance say 90% , system allow me to make , and not applying release strategy again , so there can be a miss use of this Scenario , so is there any possibility that release strategy , will appear again when change the tolerance ,
0r any other idea from your side , to avoid this ,
your suggestions are really always helpful to me , please guide me for this also
Thanks & regards
Neha

Hi Neha,
A reset of the release strategy only takes place if
- the changeability of the release indicator is set to '4' in
   case of a purchase requisition and '4' or '6' in case of
   another purchasing document (purchase order, request for
   quotation, contract, scheduling agreement),
- the document is still subject to the previous release
   strategy,
- the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

Release Purchase Requisition - "Release strategy"

Hi there,
I am trying to release a purchase requisition. I looked in the table "EBAN" and i can see the entry or in other words, the requisition i created. In the Release indicator, Release status and Release strategy fields, these are empty. How do i add information to these fields which appear to have missing data?
Speedy repsponse would be very much appreciated.
Thanks
Motolani Fatuga

Hi Motolani
spro>Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Release strategy
Select release strategy> Go to details>classification
here check what are the charactaristic and what are the values maintained for it
Check this for all release strategy
Mostly PR release strategy is based on Document type and PR Value
Check whether UR PR fits in release strategy criteria
Suppose Total value of requisition is maintained as 1000-2000
If UR PR value is less than 1000 Then PR will not subject to release
Vishal...

User Exit for getting Purchase Requisition Release Strategy

Hi Experts,
When a user creates a PR I need to know the user exit I need to implement so that the First Approver (Processor) text in the Release Strategy is populated from a custom table. I have seen that the field is MEREL_S_GRID1-STEXT. I also need to know if I can implement a user exit so that it pulls the release strategy for a PR for assets (Acct Category A) since it is pulling for Acct Category K (Cost Centre) and the Release Strategy tab is appearing in this case.
Kind Regards,
Darlington

Hi Meenakshi,
Thanks for the very useful answer. It has given clues on how to resolve this issue. I have resolved this issue for the Asset item category using the following thread: user exit for requisition release strategy, and also SAP Note 365604.
However, I have another issue, the release strategy for Stock Items, (item category blank) is not pulling through. I need to use the same method above but would like to know how it determines the funds centre for a specific stock item. I couldn't find where that is implemented in the material master and I need info on how to determine the account assignment for stock items based on the funds centre.
Regards and Thanks.

Workflow for purchase requisition release strategy

Hi all,
I need an urgent help on Workflow for Purchase Requisition Release. The requirement is that when a purchase requisition with a given combination (Purchasing Group, Material Group and Account Assignment Category) is created and saved, it should trigger a workflow for approval of release or rejection to one specific business manager. If he dont responds in 2 days, it should be sent to other business manager. If any one of them releases the requisition, it should send a mail to the requestor that the requisition is released. And if it is rejected, then also a mail to be sent to the requester informing that his requisition is rejected...
Can anyone take some pain and guide me step by step procedure to implement this or to use any existing one.... I know its BUS2009 thats used in this but really dont know how to implement it properly.
Its urgent...
Edited by: Hima on Apr 11, 2008 12:45 PM

Check this link
http://help.sap.com/saphelp_47x200/helpdata/en/04/92762546f311d189470000e829fbbd/frameset.htm
Thanks
Arghadip

Purchase Requisition Release strategy for MRP based Requisition

Hello Gurus
We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
Thanks
Nick

Hi,
If you want include the MRP related PR in Release strategy.
You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
But it will not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
I think first one is best suited.
rgds
Chidanand

Purchase Requisition Release Strategy with classification

Hi there,
Please help,
I have the release strategy and workflow working. (Overall Release)
Problem is that Org Structure is not updated so workflow has been configure going to (US) user. As i am using workflow option 1 which is resolved via Group, Code & Plant, I have to have a code for every region and manager to resolve the workflow. I am not using plant as business requirement is overall release.
Scenario is that there are 8 regions with 1 senior region manager and 1 executive.
The region managers can each release up to 20k. Senior region manager must release from 20k - 50k. Executive must release from 50k -250k.
Release Codes:
Regions = L1 - L8
Senior Region Manager = SR
Executive = X1
Characteristics are:
DocType = NB
AccAsingment = K (Cost Centre requisitions)
Purchasing Group = (Each region has own group)
TotValue = 0k -20k, 20k - 50k, 50k - 250k.
Now the release strategies.
Even though it is the same senior manager and executive why do i have to create a new strategy for every region's escalation above 20k taking into account that the business requirement is that the correct region manager has to release before the senior manager can release? It just seems so pedantic when i would rather just add the correct Purchasing Group everytime.
This is only one leg of the Org Structure there are over 40 depts, and managers that will create and release. Do i really need a strategy for every single scenario?
Thanks for taking the time to read.

Hello,
Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
Cheers !

Purchase requisition release strategy issue

I have created release strategy in development, it was working fine with work flow. When I try to import the TR's I found that the document types in development are not in quality so I changed the document type. then I tried to create a PR and when I clicked on messages its not triggering the release strategy don't know why. In total there are 2 characteristic plant and document type.I even tried to delete the plant characteristic and tried again creating PR but still no use. let me put some screen shots comparing the development and quality. Please do help.

Thanks for the quick reply, I just checked that the over all indicator for the development and quality, I found that in development its not activated while its activated in quality will that be of any issue.
In development
In Quality

Issue with Purchase Requisition Release strategy

Similar Messages

Maybe you are looking for