Purchase Requisition Realease Strategy without classification
Hi,
Request for detail process and configurations for Purchase Requisition Release Strategy without classification.
We have 5 authorities like A1 (Lowest) and A5 (Highest authority) in the organisation to release the PR.
The PR should be released according to value slabs.
Thanks a Lot.
Sachin
Hi Sachin,
IMG> Materials Management>Purchasing> Purchase Requistion> Set up procedure without classification
This process is similar to process of with classification
Go through the link below:
for this no need of creating characteristics and classes
http://www.sap123.com/showthread.php?t=59
http://help.sap.com/erp2005_ehp_03/helpdata/EN/75/ee150b55c811d189900000e8322d00/frameset.htm
If useful, reward me
Thanks & Regards,
Swathi
Similar Messages
-
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
SajidHello,
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 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 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 helpThis 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 in purchase requisition release strategy code
Hi
We are facing a problem in purchase requisition, a new release strategy was created and change request transported but when PR is displayed in release strategy chart a same user is showed in different release strategy code.
Note: new strategy was copied from other.
Thanks in advance.hi,
As you said tht you have copied the release stategy n created the new one...
If you do so, you would have copied the class also...to which the release group is attached...
If this is the case, then system doesn't recognise the new one, and inorder to solve it you have to define the new characteristic and class...then assign this class to the release group and make your release strategy again...
Once you do this check the release strategy at OMGSCK...and then try at PR...
You do all settings at :
SPRO >> IMG>> MM >> Purchasing >> PR >> define release strategy >> W/o classification >> here edit characteristics/class and all other link are provided...
Regards
Priyanka.P -
Creating Roles for Purchase Req. release strategy with classification
Hi friends,
Since I have created Purchase req rel strategy where I have four release strategy
1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
Now the manager will have 2 release code,if officer is absent he could release the requisition.
Same has to be done for plant 2
The release Group and code needs to be assigned to the Roles , could anybody tell me where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
1. For Plant 1 lower value of requisition 1 codeL1(Officer)
2 For higher value of requisition 2 code say Li and L2(Manager)
Manager should have 2 codes if officer is absent he could release
Same has to be done for Plant 2
Thanks N Regards
SiddharthaHii,
Steps:
1) Create a Role
2) Add the authorization Object M_EINK_FRG by taking the manual option
3) Assign Release Code and Release Grp
4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
Regards,
Kumar -
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,
NitiDear 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 -
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 FatugaHi 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... -
Purchase Requisition Release Strategy not to run when change to PGrp
We have buyers that are required to change the purchasing group on the purchase requisition before a PO is created. We would like to allow them to do this without triggering the release strategy. Any ideas?? Thanks.
release strategy will change only in the case if you cahnge value or oquntity other wise it will not retrggering.
If you change the Purcvhase group system will not tregger the release
let me know if oyu have any other problems -
Purchase Requisition Release Strategy - multiple account assignments
Hello,
We would like to be able to create a purchase requisition where each line item can have 1of 3 account assignments (KNTTP). These 3 account assignments all have the same Release Strategy. Our expectation was that the purchase requisition would have a release strategy but it doesn't. If we use 1 account assignment withmultiple line items we get a Release Strategy but if we mix them we get nothing.
Does anyone know how to make the Release Strategy show up for multiple account assignments that share the same Release Strategy?
Regards,
Corinne TaylorDear Corinne Taylor,
You may assign a BLANK value in the characteristic:
You can add also as " " and named it as BLANK so you can have your release strategy get trigger
for all MRP account assignment or multiple account assignment.
Example setup
Account assignment A
Account assignment K
Release group X1 strategy 01 classfication has blank in values.
Classification:
Value Description
A Account assignment A
K Account assignment K
BLANK
Test this and it will work.
Best Regards,
Ian Wong -
How to set the Release Strategy without classification for PR
Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh1. Release codes
Create the release codes. For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
Define release indicators and branch to the detail screen. Here you
define whether fixed purchase requisitions may be changed by Materials
Planning, for example, and whether an RFQ or a purchase order may be
created from the requisition.
You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
specify whether a requisition may be changed after the release
procedure has begun. You specify whether the strategy has to be
redetermined after changes, or whether the release procedure has to
start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
example, previous releases are not cancelled if the value of the
requisition item after the change does not exceed plus 10% of its
original value.
Attention:
Be sure to create a release indicator (e.g. B for "blocked") that
serves as the starting point for subsequent indicators. Do not set the
indicators for release for the issue of RFQs and PO on the detail
screen for this indicator.
Also create a release indicator characterizing the released status.
Set the indicators for release for the issue of RFQs and PO on the
detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
Assign a release indicator in dependence on the status of the release.
Example:
You create a release strategy S1 consisting of two release codes 01
and 02. Release with 01 is a prerequisite for release with 02. If
release has been effected with 01, the requisition has been given the
"all clear" for the issue of RFQs.
You have created the release indicators B (blocked), 1 (cleared for
issue of RFQs) and 2 (cleared for RFQs and PO).
Now enter the following as assignment:
Strategy C1 C2 C3 ...
S1 B (blocked)
S1 X 1 (RFQ)
S1 X X 2 (RFQ/PO)
4. Release prerequisites
Define which release codes are involved in a release strategy. Specify
whether a code is set for a release status following release, and
whether one release status is a prerequisite for another (+).
Example:
Strategy Code C1 C2 C3 ...
S1 01 X
S1 02 + X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only. </b> -
Release Strategy without Classification VS with Classification
Can you have a strategy based on with classification and another one without classification in the same client.
Thank you.Hi
You can have either of the One active in a system
If you have activated RS without Classification, all the PR's will be subject to Release Process..
If you now activated RS with Classification then this will Not work as the sytem has already found a RS wothut classification & not depebndent on any charcterisitics.
So you can use only one of the Combination.
This is applicable to only Purchase requsitions.
For Purchase orders & othe Documents you will have only with Classification.
Thanks & Regards
Kishore
Maybe you are looking for
-
How come since updating to ios 6.1.2 AOL emails are not being pushed?
Since updating the only way my iphone 4s receives emails is by manually checking. How do I fix this???
-
Color Printing on High Gloss Paper
I'm using an HP Photosmart Premium All in One (C309a). I am printing a camouflage pattern, with a lot of color on top of color, using high gloss transfer paper. The variations in color are getting lost on the high gloss although it prints out just f
-
AR Invoice Print - Print on Preprinted stationary with Line comments & more
Hi All, I have a requirement to print a report in XMLP for AR Invoice Print. Requirement For Template Body - Line Items Line 1------------------------------------------------------------------------------------- Line 2--------------------------------
-
I have an ipod touch 3rd generation, version 4.2.1 (I think), model A1288, 8gb. A month ago it stopped working and wouldn't respond to a reset by pushing the on and home buttons together, and it wasn't recognized by itunes or by my Vista OS laptop.
-
Form button doing both update and moving to next row
How do I get a form button to do an update of the shown row, and then move on to the next row in the resultset? I've tried to assign both the doQuery; and doNext; functions in the same PL/SQL button event, but with no luck.