PR overall release strategy (with shared PR document types)

We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know, this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

Hi ,
The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
The Plant can be taken as one of the characteristic.
The view CEBAN gives all the related views.
check the below LInk for Futher information on the same.
http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
hope so it helps
Regards
Anjanna.

Similar Messages

PR overall release strategy with acc. assignment category characteristics

Hi,
Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
see below more details :
I have created the following PR release strategy with classification.
PR type concerned " NB": overall release
Rlease group concerned : overall release
In this release group i have 1 class
in this class i have 2 characteristics : PR type and Account assignement category.
Release strategy 1 :
PR type = NB
Acc. assignment cat = P, W
Release strategy 2:
PR type = NB
Acc. assignment cat = K, V
TEST 1 : PR type NB, 1 item with P category
OK the release strategy 1 is generated
TEST 2 : PR type NB, 1 item with W category
OK the release strategy 1 is generated
TEST 3 : PR type NB, 2 items with P category
OK the release strategy 1 is generated
TEST 4 : PR type NB, 2 items with P and W category
TEST KO, no release strategy is generated
=> what should i do to solve this issue ?
Thank you in advance for your quick answers,
Isabelle

What is the specific requirement for Overall release strategy?
Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
Every line item generates a PO, so logically should be set to a release strategy.
Bottomline is use release strategy at line item level Unless a specific reason exists.
Regards,
Sameer

Add release strategy in the PO document type

Dear all,
I create one PO Return but there is no release strategy in ME28, what should I do to add the release strategy for that PO doc type.
Thanks
Pauline

Pauline,
I would suggest you to please post this query in ERP MM forum to get it answered asap.
Regards,
Faisal

Release Strategy in purchase order document type

Hi Gurus..
I'm tring to tweak the single RS in the system.
I've set the charcteristic using table CEKKO field BSART, restriction 032, I've set two document types as the Characteristic Value (ZLOG - ZADM). Then I´ve set the class with this characteristic, Created Release Groups & linked to class , Created Release Codes, Release Indicator, and Set up strategies
.. but It doesn´t pick any release strategy.
The funny thing is if I delete the document types values entered in CL20N it works for all doc typs, but if I set the docs types that it should take to pick the RS it doesn't work at all...
Please advice..

I´m not such a abapper but I guess there is not values taken to ekko, does it ring a bell?
                                        BUKRS
                                        BSTYP
                                        BSART
                                        BSAKZ
                                        LIFNR
                                        SPRAS
                                        EKORG
                                        EKGRP
                                        WAERS
                                        BEDAT                                             00000000
                                        LLIEF
                                        KUNNR
                                        RESWK
                                        LBLIF
                                        INCO1
                                        KTWRT                                             0.00
                                        LIFRE
                                        WERKS
                                        MATKL
                                        LTSNR
                                        USRC1
                                        USRC2
                                        USRN1                                             0000000000
                                        USRN2                                             0000000000
                                        GNETW                                             0.00
                                        SUBMI
                                        MEMORY
                                        KONNR
                                        REVNO
                                        PDUMMY
                                        KDATB                                             00000000
                                        KDATE                                             00000000
                                        EBELN

Overall release of purchase requisitions - pr document type

hi,
what is the importance of the indicator Overall release of purchase requisitions while defining the PR document type.
Overall release of purchase requisitions
Determines that the items in a purchase requisition are all released at the same time (rather than individually).

Hi Manipal,
overall release makes the release of all the items in the document.
u can also release itemwise in PR only and in all other external documents overall release is only possible
hope it wud have answered ur question.
Reward if useful
Shawn

Overall Release Strategy

Hi Experts
I am trying to set up an overall release strategy with the following characteristics: total value and account assignment K.
In order to get the overall release strategy to work I had to set the overall strategy at the document type level (NB).
Now material PR and consumable PR are subject to an overall release. What can I do to set the strategy for only PR with account assignment K.
Thanks
Belle

Please let us know what have you maintained in CL20N
Regards,
Indranil

PR release strategy with classification

As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
Any pointers to solve this will be highly appreciated.

Hi Ashish,
If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
Regards,
Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM

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
Siddhartha

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

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 !

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.

MM Release Strategy with Cost Centre

My characteristics for the release strategy is Accnt Assigmnt (KNTTP), Cost Centre (KOSTL) and Amount (GSWRT). I link all to the ceban straucture, and for the cost centre, I entered in the value tab the cost centres that I am using, and I entered the cost centres in the release strategy. Everything seem OK for the release strategy, but the release strategy is only selecting the strategy according to the values and not considering the cost centre, what can I do let it consider the cost centre and the value. I have been struggleing with this problem more than a week now. I tried everything that I can think of. Can someone assit me in this matter. I am on ECC 6.
Thank you.

Refer OSS Note :: 52225
Solution ::
Summary
Symptom
Purchase requisition release strategy with classification does not work as expected when the characteristic for cost center KOSTL is included.
Message ME297 is displayed.
Additional key words
CEBAN-KOSTL, KOSTL, Cost center, Release strategy, OMGQ, ME297
ME51, ME52, ME53
Cause and prerequisites
Numeric values used for the cost center characteristic in the purchase requisition release strategy with classification is not recognized. CEBAN-KOSTL is a CHAR field of length 10.
Solution
Enter leading zeros for the cost center value in the release strategy. eg. If the cost center value is 123456, while entering this value for the cost center in the release strategy, enter it as 0000123456.
Cheers !!!!!!
Biswajit

Release Strategy With Classification

Hey All,
I would like to get some information about release strategy with classification for purchase requisation and purchase order.
Please send me some information regarding this.
Thanks
Kawal

hi,
To see the all the linkages firstly see the classifcation and class defined in the sap system at:
SAP easy access --> Cross application components --> classification system --> master data --> characteristics and classes(CT04 and CL02)...
TO see the customisation, check:
Spro --> MM --> Purchasing --> PO/PR etc --> Release procedure --> Rel procedure with classification --> Here check for all the different transactions...like Relase codes, release stategy, access sequence, schema etc...
Also one important point abt it is:
PR is possible to release at header as well as at item level...
But PO and other external docs are only possible to release at header level only...
In the customisation check all the linkages you will get best out of it....
Regards
Priyanka.P

Re: PR Release Strategy with workflow

Hi Expert,
   Is there a way the scenario given below will be possible to achieve..
   All the needed config for the PR release strategy has been define... (release code, group,release strategy,class & characteristic)
Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager ( Release Code :PM)
The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

hi
i think u need workflow for release strategy
Steps involved are :
1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
3) Go to OOCU > here under MM, go to MM-PUR,
4) Click on "activate event linking"
5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
and Save.
6) Click on "Assign agents" and proceed all above steps.
BUS2012 is the relevant business object and Releasestep created is the event for the same.
7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
take help of ur BASIS person
hope it clears
regards
kunal

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

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

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

PR overall release strategy (with shared PR document types)

Similar Messages

Maybe you are looking for