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,
Ask

ashokkumardash 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.

Similar Messages

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.

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,
Rohit

HI 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,
Grzegorz

Hi,
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
Srihari

Hi,
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

PO Release Strategy not triggerred for particular Total Net Order Value

Dear,
I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
Please suggest for solution.
Thank you.
Warm Regards.

Dear All,
While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
May I know how the value for this field gets calculated.
Thank you.
Warm Regards.

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.

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
RS

HI,
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

Error message if no release strategy is applied for PO

Dear All,
In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
Is there any way to encounter this
Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
OR
While making GRN against this PO, System will give message Like say ... no release strategy is applied for the PO..
Please reply ...URGENT
Regards,
Rakesh Shelar

Dear Thanx.
my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
In this, case system is allowing to take GRN against such POs without release strategies

Release strategy not triggering for Specif plant

Hi Friends
I configured a release strategy with three charecteristics. P.org, Plant, Net value.
this stretegy is triggering for specific plants which are under a particular company code, and if I change to my plant and P.org. its not triggering.
I have deleted all the classifications and release strategies from, no other data in VV_T16FS_2 , AUSP,T16FV,and T16FS tables except this release strategies data.
do we have any settings at cocode level??????
please respond if answer known
Points would be awarded for for your valuable answer.

Thank you deepak for your quick respond
Actually There were already release strategies with same charecteristics, and with the values of other plants and other P.orgs which are under certain companycode.
these were triggering perfectly for PO
Now created new strategy for plant and P.org under different plant code of different cocde. this strategy not triggering for PO.
but if the release strtegy values replaced by the erlier plants and P.org again its triggering.
Now I created new chars, class, and stategies still same problem persists.
Release stategy working for the values of a prticular company code plants, Porgs.
and already tried your suggestion Cocode as char. but same its working for only that company code not for my companycode

Release Strategy in PO for direct materials not driven by MRP

We have a requirement to enable release strategy for purchase orders created for direct materials that are not driven from an MRP requirement for a single plant.
Request you to let me know how I can make this work.
I have an option to make it mandatory to have Preq for these PO's and can enable release strategy for Preq which are created other than MRP.
request to let me know if there are other options in PO's itself where I can find that the Purchase orders are created directly and put release strategy in it.
Thanks and Regards
Murali

Hi Murali,
Standard SAP provides PO release strategy at header level only and not at item level.
So you can create a new PO document type and allow use of only this document type for manual PO creation.
Then set-up PO release strategy for newly created document type, where one of the primary characteristic will be Order Type (Purchasing).
Hope this will fulfill your requirements.
-Ravi

Release Strategy with Workflow for PR & PO

Hi Experts,
I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
So User should get the information about the releases for PR & PO.
But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
Points will be awarded .
thanks & rgds
Swamy

Hi Swamy,
The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
How to configure?
Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
Maintain the details u already have in hand:
For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO. After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
Hope this will give you an idea how the workflow works and how to configure it.
Rgds.

Release Strategy not working for MRP generated PR

I have one qurey. Currently we are release strategy for normal PR.Now client want to activate release strategy for MRP generated PR.
current Release Strategy for normal PR configured as following.
Purchase requisition document     RV
Purchase requisition document     ZADV
Purchase requisition document     ZIMP
Purchase requisition document     ZSER
Purchase requisition document     ZSTD
Purchase requisition document     ZSTR
Purchasing group     A01
Total value of requisition for     > 1.00 INR
Creation indicator (purchase r     Realtime (manual)
Overall release of purchase re     Yes
For MRP generated PR I add creation indicator B - Material requirements Planning.Even after add creation indicator release strategy is not triggering for PR.
To trigger PR any setting need to do other than add creation indicator.
Regards
Sathish

Hi
You don't have to include creation indicator as parameter. Check in what documnet type MRP PR is generated. You can see it in t.code OMDT. At document type level also you can manage it. You need to include creation indicator only if a seperate person approves MRP generated PR.
To know how to configure release procedure see the below link
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards
Antony

Issue with New Release Deploying Crystal Reports for Visual Studio 2010

Previously I created a deployment project with Visual Studio 2010 using the Beta 2 release of the distributable. This worked fine and installed on a 32-bit XP machine.
I've since updated the project to use the new Release version of the distributable CRRuntime_32bit_13_0.msi. Now when I run the installed program it gives me the following message -
"An error has occurred while attempting to load the Crystal Reports runtime. Either the Crystal Reports registry key permissions are insufficient, or the Crystal Reports runtime is not installed correctly. Please install the appropriate Crystal Reports redistributable (CRRedist*.msi) containing the correct version of the Crystal Reports runtime (x86, x64, or Itanium) required. Please go to http://www.businessobjects.com/support for more information."
I've had a look at verious posts and added code to the app.config file so it looks like -
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>
and also tried targetting various .NET frameworks, but without success.
Am I missing something?

Hello,
More info, are you installing on the same PC as the Beta was installed on or a clean PC?
Your app must be set to the full framework, not the client version.
Are you installing by right clicking on your setup.exe and selecting run as administrator?
Setting that option in the app.config is only required if you are using that driver you found the info on.
Run ProcessMonitor and set it to filter your installer and see what it reports.
Thank you
Don

Release strategy not applied for some contracts..

Dear All,
At my client place,In some of the contracts release strategy is not applied.
I have tried evrything...in classification plant,purchasing group,net value and order type (MK and WK)everything is added.
but some of contracts release strategy is there and for some it is not applied...what could be the reason?
Please help.
Amit

Dear All,
Please reply....

Configure of New Release strategy in PR for ERSA Mat type

Similar Messages

Maybe you are looking for