Item wise release strategy

Hi Experts,
I made item wise release strategy and used material group in class ,however when add this CEBAN-MATKL it doesn't find release strategy when remove this release strategy is working is it need to add something into material master data ?Need your advice
Thanks in advance

create release class, FRG_EBAN is available in system
create release characterisitics .. here what ever name you give, you have to make it 'reference to table CEBAN' and corresponding CEBAN field , in additional data
create a release group and attach the release class created
create release codes, and while doing it you have to specify for which release group it is valid
create release indicator , here specify the changeability
create release strategy with release codes, release prerequisites, release statuses etc
if you are transporting this, in the operational client, using CL24N assign char values for each characterisitcs of release strategy. ( you need not assign char value when that characterisitic is not present int he document e.g.if account assignment is a char, then for release strategy for document without account assignment should not have any value for that char)
if you ensure this much your release strategy should work ok

Similar Messages

Overall release and item-wise release at same time

Hello,
we use item-wise release for our PR strategy. Beside other we have the characteristic Account Assignment Category, which we assigned 'K' for our item-wise release. We also have the characteristic Cost Center.
Now we wanna add a new strategy with Account Assignment Category 'F'.
The problem is, if we do that with item-wise, it will not take affect, because the Cost Center Characteristic will be empty with Acct Assignment Category 'F'.
Now I am wondering if I can create another class with overall release and implement the Account Assignment Category 'F' strategy. But right now, it does not come up after creating a PR with Acct Assgn Cat 'F'.
so my question is, can I implement both classes (Overall release and item-wise release) at the same time?
Thanks
anne

Item-level release is possible. This can be done as follows:
Solution 1
Enter a blank value in the cost center characteristic. You may need to change the characteristic definition (make it non-mandatory) for this.
Then in case of F, it will find the blank cost center and still determine the release.
If you have some misgivings in this, you can try the next solution.
Solution 2
Create a dummy cost center value in the characteristic for the purpose of release. Activate the user exit for PR Release. In this user exit, if the account assignment is F, change the cost center in the communication structure to the dummy value. This will ensure that the release is determined.
Please let me know what happens...
Lakshman

Duplicate item wise release pur requisitions

Experts,
We have item wise release procedure with classification set up for requistions. We have begun work on new projects where leaders have received special delegation for releasing. Is it possible to duplicate the release procedure for these leaders with special authorization for releasing so we can keep project approval separate from ongoing operations.
Best regards,
Diane

Hi Diane
Maybe you can define a new release code for this users (adding this to the strategies of the project) and then asign this code to a new role. So this user will have two release code, one for the on going operation and one for the project operation.
Hope It helps
Regards
Enzo

PR item wise release

Dear Expertise,
Would some body so kind to give me all the customization setting detail that require for purchase requisition item wise release.
Your earlier answer should be highly appriciated.
Regards,
sp sahu

Hello Sahu,
The following link will help you to understand release process and customization.
http://help.sap.com/saphelp_46c/helpdata/en/9f/2d547bb435d1118b3f0060b03ca329/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/a7/2d547bb435d1118b3f0060b03ca329/frameset.htm
in short,
1. Define characteristic
2. Define class
3. Set up release procedure
3.1. Define Release code
3.2. Define Release Indicators
3.3. Assignment of release indicators
3.4. Set up Release pre-requisite
3.5 Determine Release stretagy
Hope this helps.
Regards
Arif Mansuri

Processor of PR item level release strategy

Hi All,
I need to pass the Processor determined from an item level Purchase Requisition release strategy to a WF container. The event is RELEASESTEPCREATED in BUS2009. I have created an import element container called 'Processor' from ABAP dict. data type MEACTOR.
In the binding for the WF trigger RELEASESTEPCREATED I cannot bind the 'Processor' wf container to the Event Object.
What are the steps which I must follow to add the 'Processor' to the RELEASESTEPCREATED event?
The release strategy in SPRO for item level Purchase Req release is complete and the Set-up procedure for Workflow is complete.
Thanks
Mike

Hi,
Go to SWO1, enter BUS2009. Click on create subtype icon there. Then enter all fields as say ZBUS2009. Now save your new BO. then implement and release it , i.e;
Edit> Change Release Status> Object type> to implemented. Again Edit> Change Release Status> Object type> to Released. Then go to events in this objects. Click on event RELEASESTEPCREATED. Then click on event parameter and create a event parameter.
Hope this solves your problem.
Don't forget to delegate ZBUS2009 with BUS2009 in SWO6.
Let me know if you have any queries.
Regards,
Raj

Overall release of PR in Release Strategy

I have created item-wise release of PR using with Classification of Rel Str.
But when I am creating overall release of PR I am not getting the tab.
I made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR.
Pl guide
regards
VS

Hi VS
Am confused. You wrote 'Have created item-wise release strategy' and also asking 'Overall release'.
If you have "made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR", then you have configured Overall release.
If PR does not get release strategy tab at header, it could be due to incomplete release strategies. No release strategy might have been triggered for your PR data. Do you see release strategy tab at item level ?
Best regards
Ramki

PR Release..Overall is good, Item-wise error

Hi,
We used to have PR release without classificaiton. Today we decided to go with Workflow, so Recreated release procedure with classification. After Char Class routines, checked at OMGQCK, basic check is green and Overall Release is Green, but Item-wise release is red with message reading, "no release group exists". I used GFWRT from CEBAN for overall Release. Checked ovr rel flag at document level and release strategy level.
When creating PR, release procedure not kicking in.
Can someone help me please?
Thanks
Raj

This is the problem of Uncleaned Release Startegy. Delete unwanted lines in CL24N before you configure new one. Since you have already configured new strategy, remove it and then delete corresponding line in CL24N.
Check table T16FC-FRGGR and Tcode OMGQCK as well.

Release strategy - item level

hii all
can some body tel me , how and where we have to configuration for PR release strategy at item overview level.
And the same item level release strategy is posssible to configure for PO also??
If not y what is reason???
Thanks in advance
SAP-MM

hi
> how and where we have to configuration for PR release strategy at item overview level.
http://www.sapstudymaterials.com/2008/08/purchase-requisition-pr-release.html
>And the same item level release strategy is posssible to configure for PO also??
hi we cant have itemised release for PO
logically thinking PR can have multiple item and no fixed vendors and even not sure for placing order
so the realing person will decide for the item to be purchase so it has itemised relase
now in PO ,u will raise PO only when u have confirmed the purchase and the order will be for one vendor
so for ordering u have to relese the whole po,
or u can say u will create PO for all the items which have to procure so release will be for whole PO
go to spro>MM>Purchase Requisition>Release Procedure read the left side help for WITH and WITHOUT CLASSIFICATION
Edited by: Kunal Ingale on Mar 9, 2010 6:32 AM

Problem with purchase order release strategy

Hi Guru's
    i am dealing with problem of service purchase order release strategy , when i making the service po , i am not giving any over fulfillment tolerance , after release & making Service entry sheet of PO ,   when i go to the change mode and change
over fulfillment tolerance say 90% , system allow me to make , and not applying release strategy again , so there can be a miss use of this Scenario , so is there any possibility that release strategy , will appear again when change the tolerance ,
0r any other idea from your side , to avoid this ,
your suggestions are really always helpful to me , please guide me for this also
Thanks & regards
Neha

Hi Neha,
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 total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

Class and release group and code in release strategy??

hi experts ,
Can some body explain me..
I have created Characteristics and Class for for release strategy.
But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
I m using the same class what i have created for my company..
So how to over come this issue
Thanks

Release Prerequisites
Definition
The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
Release Indicator
Definition
When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
What does the release indicator determine?
Requisitions...
External purchasing documents....
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether an RFQ or a PO may be created with reference to the item
Whether the document may be changed by Purchasing after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether the purchasing document is released for transmission
Alternative Release
Definition
Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
Release w. Classification (PReqs./Ext. Pur. Docs.)
Use
The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
Operation of Release Procedure w. Classification
The characteristic values from a requisition or external purchasing document are passed on to the classification system.
The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
The persons responsible for the release codes process the document in the sequence defined in the release strategy.

Requisition Release Strategy

Hi,
I am looking for a way for a requisition release strategy to reset (unapproved state) when the value or quantity or both is decreased.
I have managed to do this in Config if the value or quantity or both is increased but not decreased.
Scenario:
1) Create Purchase requestion
2) Approver approves requisition
3) Creator changes requisition - decreases the value or quantity.
4) The requisition release strategy must be initialised.
Is there a way to do this in config or will I have to use a user exit for the decrease part.
Thanks,
G A

Hi,,
Rest can only be done if increase in value is done
3. Question :
Why is the release strategy not reset?
Answer :
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 total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
FAQ note 493900

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

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

PR release strategy for material group

Hi,
I have 2 different line items in PR with 2 different mat groups. How can I set up a release strategy for this scenario. Ex-line No 1 has mat group X and line item 2 has mat group Y. Do I release at header level or item wise release is possible

Hello
In PR you can set up this release strategy without classification release strategy.
w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
Laxman

Release strategy not trigerred if PR changed after Approval

Dear Gurus,
I have a requirement kindly help.   We have a PR generated from PS module, This PR is released by the approver. After the Approval, PS user change the PR qty and value has been increased. Now my client wants that this PR should be again sent for approval and release strategy should be trigerred. After the approval my release indicator is 2 RFQ/Purchase Order. I have set the Changeability indicator to 4 and define the tolerance to 0.1 %.
But PR release not trigerred even after this. Kidnly help.
Thanks.
Johi

Hi Johi,
Check note 493900 point 3:
3. Question :
Why is the release strategy not reset?
Answer :
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 total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
I hope this helps.
Regards,
Ashwini.

Item wise release strategy

Similar Messages

Maybe you are looking for