New Release Strategy in case of PO amendment
Dear All,
We have the release strategy at PO level on 3 parameters,
Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
When ever users edit the PO, again system sets the release strategy as per above logic.
Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
Can any one send me a user manual and steps for this.
Thanks in advance,.
Vikas
Hi,
You can set a control within Config. there is a parameter called as release indicator.
Follow this IMG path:
SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
1 Cannot be changed
2 Changeable, no new determination of strategy
3 Changeable, new release in case of new strategy
4 Changeable, new release in case of new strat. or val. change
5 Changeable, new release if new strategy/outputted
6 Changeable, new rel. if new strat. or value change/outputted
Changeable, new release in case of new strategy
Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
Hope this explanation was clear.
Prashant Rathore.
Similar Messages
-
New release strategy should not trgger for PO released with old Rel Strategy
Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
RohitHI Rohit
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 most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine -
New release strategy / Old PReqs
Hi,
New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
Many thanks in advance for your clues.
Regards,
GrzegorzHi,
Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you. -
Pr& po -new release strategy?
Hi Friends,
My requirement is to add new release strategy for pr & po.
Characteristics & Class are remain unchanged.
Pl advise to how to proceed, i mean
i have to set/create new release procedure, ie.,
New release groups
New release codes (bcos new codes are added & release levels remained same)
New release strategies
How i can retain the Old PRs & POs released with earlier release strategy/release codes?
PRs & POs not released can be with new release strategy, but i have to ensure the old prs & pos (released) were with earlier release strategy & release code.
Also, I need ur advise, how the new release strategy works for workflow
pl help
thanks & regards
SrihariHi,
First of all, if you would only like to create the new release strategies, then the only possible settings you should do are -
1) Create the new release code;
2) Create the new release strategy;
3) Assign the release characteristics values to your new release strategy in CL20N transaction.
For those old PRs and POs (regardless of if they were released or pending for release), the same old release strategy remains unchanged (and therefore, you should be much careful if you wish to delete the outstanding release codes and/or release strategies through configuration). Having said that if you would like to keep the same release strategy though changes are to be made to your old purchasing documents, then you will have to assign the proper value to the "Changeability" field of your "released" release indicator.
In case of release strategy in support by workflow, basically, the workflow item will be triggered (in accordance with the pre-defined logics that you built in terms of task ID). As soon as the approver determination is made in background, the workflow item will be then sent to such agent who will then take a proper decision (approve, reject or forward).
Cheers,
HT -
Configure of New Release strategy in PR for ERSA Mat type
Dear Friends,
Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
Regards,
Askashokkumardash wrote:>
> Dear Friends,
>
> Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
Hi,
Create Characteristic for Material type and Communication structure CEBAN and a create class with 023 and assign character to class and create Release group and code for MRP controller and finally assign this particulate role to the MRP controller User ID and he release the same. -
How to activate a new release Strategy Of PR without deleting the previous one?
Dear All,
1=I have a release strategy in purchase requisition which is without classification and active in system.
2= Now i configured a New Release Strategy for Purchase requisition which is with classification
My question is i want to activate the New one with classification in System without deleting the previous one.
Should it possible? and How?
Ritesh.Dear Dev,
My old release strategy at item level.
But the New one is at header Level.
But the previous one showing the release Indicator.
But when i delete the old configuration the old release indicator vanishes.
But the thing is in Pr with out classification we have same Pr doc.Type
But in New Configuration We want to at header level and with same doc type.
so without deleting the old one if i activate the New Strategy whether the system allow me
to see the New Release Indicator?
As My testing when i deleted the old one the Old indicator in Line item Level vanishes. -
PR Old Release Strategy - triggering NEW Release strategy any change OLD PR
Dear Gurus,
We have implement item level PR release strategy,
characteristic used: 1. Document type, 2. PR item Value, 3. Material Group, 4. Change date & 5. Account Assignment Category.
BEfore the above implementation, there is a OLD PR release Strategy existing in the system at one level release.
Now the issue, the OLD release Strategy status is release completed, now the user goes and change the PURCHASING GROUP in old PR, new release gets triggered. How to Stop this, system should not trigger NEW STRATEGY,
Please advice
REgards
RSHI,
If i use date created as a characteristic, then Old release strategy get reset and the no release strategy will be trigger henceforth, the status of the PR will be INACTIVE.
ANy charateristic we use, there will be only 2 options for old released PRs, 1) It will reset the strategy to new one or 2) the old strategy will be reset and make the PR status as INACTIVE.
Is this is standard behaviour? pleae advice
Regards
RS -
How to configure release strategy in case of document parking ?
Hi experts,
I have a requirement wherein i have to create a workflow with four level approval when a document is parked before it can be posted.
The approval is by company code,reacon code and the amount .For example for a particular reason code for particular amount one person has to approve,if the amount is greater then 2 people have to approve, so on.
Is it possible to configure such a release strategy in SPRO ?
Kindly help,
thanks in advance,
regards
AshwinIf it are FI Invoice you're talking about, it's possible.
Do you have access to the best practices of Public sector management ? There's an example on how to implement an FI workflow.
If not, check workflows on the object FIPP -
Pr& po -new release strategy? released/locked/incomplete
Dear MM experts,
I would like to understand what it is meaning of
released
locked
incomplete
while doing assignment of object class thru cl24n for new release strategies,
I am clear on released & locked, I would like to understand what is "incomplete" means as per SAP.
kindly clarify
thanks in advance
srihariIncomplete means - When you go to CL02 or CT04
you are entering the statu for calss or char as locked or released
but when you are creating and that time if you have keep the status is in preparation and without changing the status you start maintainig the data in CL24N than you will see the statu as incomplete. -
hi,
i am having xxxxx class for po release strategy with 3 characteristics-(plant, po value and document type)
now i want to have only 2 characteristics with document type and PO value.
again i want to use new release codes for my new strategy, keeping the same class for release strategy.
can i define new release strategy using the new codes?, then what shall be the impact of the same on below
1. already released PO, now want to amend,(after new release strategy implimented)- what would be the effect on PO?? which release codes shall hit the same?
2. already release PO(i understand there wont be a problem in GR, as release ia already effected)
3. new PO shall catch the new strategy- no problem with the same.
for implimenting the new strategy using the same class, can i delete the old release strategy with codes or i just need to remove the value mentioned in the classification view of the release proceedure.thank u.
my point is while re-defining the release proceedure.
earlier i had 150 release strategies and arround 40-50 release codes. now only 12 release codes
i just need to get confirm, if i create a new release code and assign a new release strategy using the same class(only deleting the plant characteristics), what will happen to old po(released) for which now we are amending.
i assume i need to delete/remove all the data of old release strategy available in classification view, and keeping the release codes as it is in release pre-requisites fr old release strategy.
or just any body briefe me what are all the condition for changing the exsiting release strategy.if i need to create new release code,release strategy by using the same release class. -
Release Strategy with New Class and Char.
Dear All,
I have facing problem when creating the new release strategy for different country. i have create new Characteristic and class for new Release streategy.
when i going to add in Release group.. system giving the error.
Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
My existing Characteristic for india :
ZP0_GNETW Total net order value CURR 15 2 INR
ZPO_BSART Order type (Purchasing) CHAR 4 0
ZPO_EKORG Purchasing Organization CHAR 4 0
ZPO_EKGRP Purchasing group CHAR 3 0
New Characteristic for South africa :
ZPOSA_BSART PO Order Type ATSA CHAR 4 0
ZPOSA_EKGRP Purchasing Group ATSA CHAR 3 0
ZPOSA_EKORG Purchasing Organization ATSA CHAR 4 0
ZPOSA_GNETW Total net PO value ATSA CURR 15 2 ZAR
ZPOSA_WERKS Plant CHAR 4 0
Please help me how do configure 2 release strategy for 2 country.
I will be very thankfull to u.
Regards,
Vishal GargHI Biju K,
I can use exising Characteristic Like Purchasing Organization & Purchasing Group & Plant etc. But in the case of Net order value : ZPO_GNETW Total net PO value for my indian company Currency is INR and for My SA company currency is ZAR. What will i do in that case.
Please explain..
And aslo clear the concept of creation of new Characteristic as Company Code & design different release strategies based on company code. How i can do that..??
Please explain in details.
I will be highly thankfull to u.
Regards,
Vishal Garg
9810402156 -
Precautions to be taken before going for new PR Release strategy
Dear all,
We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
Need your advice on
1)If we go for new release strategy as off with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
3)Any other which I missed out, please suggest me
Thanks
RSHi,
It is better to release all existing PRs using your current procedure without classificaton and clean up.
If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
REgards
Ram
Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM -
Release Strategy for a new material type in PR
Dear Friends,
One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
Regards,
AskHi,
Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
Then follow all the cusmozation path for your PR release startegy .
For Config part refer the below wiki link it may help you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808 -
Issue with retriggering Release Strategy
Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand SampathHi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew -
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
Maybe you are looking for
-
HT1338 internet browser is so slow when I first open it??
my internet browser either safari or firefox are so slow to start up??? if i open new tabs its straight away....and straight away for new windows.... what is this about?
-
I'm almost positive it's because of a font I installed but I installed over 1000 so I can't really pinpoint the problem. Anyways, sometimes when I open a document, the font won't be displayed correctly. It will always be displayed in the same weird f
-
I need the new version of flash on my macbook pro but it will not download. I tried to download google chrome instead and it will not download either. But this time there was a small error message in the middle of the screen that says Plug-in Failure
-
ACS v4.0 - Appliance vs. Server
With the appliance coming into line with the server version of the ACS, what are the advantages of one over the other? I know the advantage to the engine is security hardened device. This doesn't matter to me. I want to know the advantages you have f
-
JSF - Create a User Object on Login
I have a JSF Application, wherein the user is authenticated by the Container - Form Based Login. I have defined Security-Config in the web.xml and assigned roles. I am also able to mask certain URLs based on the Logged-In user's role. I have also def