Plant on release strategy - Purchase requisition

Hi,
I have release strategy for one purchase organization. Now, I created another release strategy, for another purchase organization.
Both purchase organizations have the same plants.
But in the second purch org, in some plants, the release strategy don't apears.
Do you know Why? There are no difference on customizing.
Tks.

Yes it is solution
But as I wrote before there is too many incorrect combination.
Example
PG A1, A2, A3, A4. A50
Pl 2200, PG A1 OK
Pl 2200, PG A2 OK
Pl 2200, PG A3..50 NOK
For this example I have to set 48 combinations (strategy with S).
I noticed that I would have to set about 200 strategies. Client dont want accept it.
You wrote set up one unique strategy. How? As I know I need 200 strategies (or there is something I dont know
Kind regards
Arek

Similar Messages

PO with differents plants and Release strategy

Hi Experts,
How Can I do?,
Currently when I create a Purchase Requistion with differents plants the release strategy doesnt works (Just for one plant).
I need to do a Purchase Requistion with differents plants, but I would like to keep any Realease strategy.
could Anybody help me?. where I have to set in the customize?
Tks in advance,
Ignacio

if the plant is avilable in the communication structure cekko then only your strategy will work and i think it is avilable in there
and as i am getting your problem
i suggest u to maintian a blank value in the char. werks in tcode ct04
some times when u put so many values for same charac. in po
then system is not able to judge that on whihc basis it should block the po so system will send a blank vule in the strategy and hence the strategy does not work
so my suggestion is u main tin a blank value in the char. werks or plant in ct04 for the strategy
if u need further clarification then let me know

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

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

Release Strategy - Purchase requistion go back to unreleased

Hi Friends,
I am facing two problem in release strategy in our client system.
Problem. 1:- Purchase Requisition changes( Other then the characteristics maintained) causing PReq go back to Unreleased.
Current System Settings;-
Release Procedure:- Procedure with classification ( Also setting available for setup procedure without classification maintained )
Characteristic maintained in class :- ( Plant, Value , Creation Indicator)
Value maintained in CL24N for plant , Creation indicator.
Release Indicator:- 1 Stage:- X. Blocked
2 Nd Stage:- 4.RFQ/PO no changes
Scenario :- When PR is created and released , If any one changes the Purchase Group in any line item which is not part of the release Strategy. Release strategy gets retriggered and the relase staus goes Blank for some case and for some case release strategy retrigger. My Question is if Purchase Group is not part of my release Characteristic then why release strategy gets retriggerd.( I used only purchase group here for Example, Any other changes also effect the release strategy to retrigger)
I checked all the system setting and it seems to be correct except when i use transaction OMGQCK to check PR release strategies, the log shows 3 errors of type:
Checks re requisns. with item-wise release 3
-> Checks re release group and release class 2
-> No release group exists 1
Problem. 2:- Purchase Requisition not triggering when PR is created from other source linked to SAP.
Please suggest the solution for the above problem.

Hello Kunal,
A few thoughts and questions on your problem:
You generally can't have both release procedure without classification and release procedure with classification working at the same time.
To get the system with classification working, you have to have several things in place and consistent: You need a release group. It should have a class. That class should have all the characteristics you need to assign a strategy to every requisition (or item, if you're doing item-based release). You should use CL20N (or CL24N) assign values to strategies so that you have no possible cases where a requisition (or item) doesn't get assigned to a strategy.
You have to choose item-based or overall release for each requisition document type. You mark this on the document type. You must also choose the same option for the release groups that the document type will be assigned to. Example: document type NB is item-based. Document type ZB is overall. Document type will be a characteristic. CL20N will assign requisitions with document type NB to strategies in release group NN and requisitions with document type ZB to strategies in release group ZZ. Release group NN will be marked as item-based. Release group ZB will be marked as overall-based. Usually, I think, you will just use one or the other, and it will be less complicated, but the release group must match the document type.
The indicators themselves have some configuration, including a field for changeability. Your configuration defines the indicator assigned after a release, and that changeability field will determine whether the requisition can be changed and whether that determines a new release.
As Prasoon mentioned, if there's an enhancement active, that could affect things beyond configuration.
If you are using workflow, there might be custom events related to the business objects involved that can change things, as well.
Are you using workflow?
Are you using overall or item-based release?
Good luck,
- Jeff

How to find out who has release the purchase requisition?

Hi,
I have a Purchase Requisition Number with me and I want to know who has released it. Can any body please help me how to find this?
Waiting for your valuable responses! Thanks in advance.
Regards
Faisal

Hi,
Thanks for your response. However, is there not any tcode by which we can find it out?
By the way I have done the following to find it. Kindly confirm if I have done it correctly:
1. Executed tcode me23n
2. Menu Purchase Requisition->Other requisition
3. Specified the PR number.
4.Menu Environment -> Item Changes
5. Here in this screen, I got some information saying :
Person responsible (user id), Date, Time, Transaction, Change Doc etc..
Here it says that, one user executed tcode me54 and release indicator is changed to 3.
I think this is only the user who has released it.
Anyway, kindly confirm the same.
Regards,
Faisal

No Release without Purchase Requisition in Process Order(subcon)

Hi All,
We have one requirement :
The creation of purchase requisition happens during the creation of process order which is basically governed by control key.
But in case the creation of purchase requisition didn't happen , because of any issue with master data set up in recipe
or say wrong data .
We DO NOT want , the system should allow the release of that process order.
Is there any standard way to achieve the above requirement.
Thanks in Advance!!!!!!

Hello
You can implement your own logic to check the purchase requisition during the release using BAdI WORKORDER_UPDATE. There is a method specific for checks during the release.
BR
Caetano

Release code - Purchase requisition - Release Procedure

Hello,
In the purchase requisition release procedure with classification, we are defining release codes say K, P etc.
My doubt is , Is this being defined else where based upon the designatin of the person in the organisation, or else, we are defining here straight away?
Best regards,
K.Kumaran.

HI
You are correct, you need to define the release code there only. There is no other place where it is defined. What you have to ensure is make sure that it is of Two character and not single. Assign the codes against the designation of the person as per your requirement.
Regards

Release strategy Purchase order missing

Hi experts,
I set release strategy for purchase order and it was working OK, but now release procedure is not active when I create a purchase order, all setting are correct and verificaction too.
Sap version is ECC 6.0, I do not know if there is something to correct this error, because I created some POs and release tab was displayed correctly but now it does not work.
Do you know something to solve this issue?
Thanks
Regards,
Lili.

Please make sure the release strategy is not changed by some one and than check it out
or go to release strategy config and check the release strategy of last config
here everything should be green or yellow
now go to CL30 and enter your class and class type 032 and hit enter
then enter the value of you charactristics which you have used in the Po and hit the Find in inti class from top menu
see what all release stra get pulled.
if oyu pulled more than one that means you have duplication inyour release strategy

Plan only releases one purchase requisition at the time

has anyone seen this scenario? When the planner checks multiple purchase requisitions for release and then, when he attempts to release them, the dialog box shows that only one req got released?

That is unusual.
Has the planner saved the earlier records after checking the for release box? Was there any error/warning message?
Have you checked on the Source side if 1 or more reqs. got created?
Is it possible that the other records were Internal reqs or wip jobs?
Sandeep Gandhi

Release strategy purchase order workflow

hi,
after release strategy defined ,
i configured role on relesae codes in img.
1. If I (functional people and me) define release strategy, I have assigned the roles, then if purchase is created , the work item goes to particular agent inbox or not ?.
Because there is any further configuration is there after release strategy is defined,
Now, I configure workflow only for to send mails to particular release code persons.
I want this clarification.
2. For rejecting POs is there any EVENT.
I found RESET event for rejecting POs, is it correct.
please reply ASAP.
thanks & regards
suresh

Hey,
You need to use business object BUS2012. Do a where used list from transaction SWO1 and you will find the standard workflows delivered by SAP. You can either use these or create a new workflow.
Event ReleaseStepCreated can be used as an triggering event to send emails when a PO is created. If you want to trigger an email only for specific release codes you need to evaluate the release code in your workflow.
Event Rejection_start for evaluating Rejections.
-Kiran
*Please reward useful answers

Release Strategy - Purchase Order

I have configured the relevant settings for creating the purchase order.
I am now able to create the purchase order and email the same.
However, the requirement is to release the purchase order by a Superior in the organization.
I have come across the transaction code ME28.
Can you please let me know the configuration and user transaction steps in order to follow he release strategy of the purchase order.
Thanks in advance for your inputs.
Regards,
Ravi

hi,
Few points:
1. Po can be released only at header level..
2. For configuartion, go to SPRO >> IMG >> MM >> Purchasing >> PO >> define release strategy for PO >>
here you shd set up your new release strategy ...for that you need to edit characteristics, class...
first maintain your characteristics ie. from "EDIT characteristics" ...here create your own characteristics and enter the suitable data here...enter class type '032' for the same...
reference the fields from CEKKO structure...and add your require release relevent fields...
then go to EDIT CLASS...here define your new class and maintain same class type as 032...
3. After this maintain release strategy...click on release group option..go inside...link your req. release group to class...so that the classified characteristics will seems while releasing the document...
4. Maintain release codes...
5. maintain release indicator...
6. then maintain inside Release strategy tab...
here define you already maintain group and codes...maximum 7 rel. codes are possible...
then maintain preriquisite...
In side classification, maintain the fields based on which you wanna release the PO...
and maintain the other req. things on diff. tabs...
7. after doing this check your rel. strategy at OMGSCK tcode ie. given in tree path at same place inside SPRO path define above..
Try making a PO and check whether its working or not...
regards
Priyanka.P

Error In release of Purchase Requisition

Hi All,
In Development Client PR release strategy is working fine but when iam testing in testing client PR release startegy is not working.
I have created class and characteristics before transporting the rel groups but when i checked i am getting error in classification.
What would be the reason? is there anyway we can trasport class and charecteristics.
Regards
Krishna

Hi,
In my understanding the correct way to transport characteristics is using transactions BD91, BD92 and BD93.
BD91
Characteristic                RELEASE_STRAT_CHAR
Logical system               EQ0CLNT100_X
Change number             400000000XXX
Valid from                      31.03.2011
RUN
BD92
Class type                    032
Class                            RELEASE_STRAT_CLASS
Logical system             EQ0CLNT100
Change number            400000000239
Valid from                     31.03.2011
RUN
BD93
Class                            RELEASE_STRAT_CLASS
Class type                    032
Logical system             EQ0CLNT100
Change number            400000000239
Valid from                     31.03.2011
This way you can transport classes and characteristics from each client, don't forget to create the modification number in each client before execute these transactions to transport the classes and characteristics.
You can check tables KSSK and AUSP to have sure about the transport too ^^
See ya
Jony

Making Plant As Optioanl In Purchase Requisition Creation

Hi,
Can we make Plant as optional while creating the Purchase Requistion ?
What would the negative aspect of doing the same.
Regards,

Thanks for the reply.
I have changed setting for NBB, still It is giving the same error.
One of the members in this forum has confirmed that we can't make Plant optional in the PR.
Pls. note that I am checking the same on IDES.
Regards,

PR Release strategy

Dear All,
We want that if any user change account assignment(Cost center,G/L.Order etc..) in PR the release should reset and need reapprovals.
Please let me know how we can achieve this.
Thanks.

Hi ,
           In standard design system only considers characteristics from
CEKKO structure for release strategy consideration. But it will not
stop us in selecting the other characteristics.
Please go through the IMG help of release strategy, will give good
information.
I think you have already read the note:
The characteristics of the class used must all be linked to the
       corresponding fields of structure CEBAN or CEKKO (for purchase
       orders)...."
Characteristics which are created for the release strategy with
classification MUST access communication structures CEBAN or CEKKO since
during the strategy determination, the system cannot access any other
tables or structures.
If the characteristics refer to fields which are not contained in
structures CEBAN or CEKKO, the corresponding fields can be added to
communication structure CEKKOZZ or CEBANZZ, or an append structure can
be created for CEKKO or CEBAN in which new fields can be included.
If you want to use new defined fields as part of the
release strategy clasification, you should use enhancement M06E0004
(User exit "exit_saplebnd_002").This user exit allows you to use the
user fields in strucure CEKKO to include additional data.
Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and
control them through user exit "EXIT_SAPLEBND_002. Otherwise new field
will not work.
As you very well know SAP has provided the following customer exits
which allow us to change the communication structure for determining
the release strategy
Purchase requisition
                       M06E0002 - for item wise release
                       M06E0005 - for overall release
External purchasing document
                       M06E0004
I hope this helps!
Regards
Vijayesh V V

Plant on release strategy - Purchase requisition

Similar Messages

Maybe you are looking for