Release startegy modification

Dear Experts,
we have using the release strategy,in the some users like purchase groups and release codes are changing or resigned
from the company,for that we are are assigning the release codes of relived employee purchase groups and release codes
to the existed one.in some cases when we change the purchase group,already existed release strategy changing according to the purchase group.in some cases the current employee are not willing use the release codes of relived employee,please suggest me.
Regards,
Varun

Create new release code in config.
Replace the old code with the new code in all the release strategies.
You can delete the old codes but it does not matter as long as you do not use them in the release strategies.
See that most of the in release PO's are released before the changes.
I f any old PO's are left for release you will have to re trigger the release stategy with the new codes by increasing the value or changing any other charecterstic value. After saving you can put back the old values.

Similar Messages

PR Release startegy

PR release startegy should be flexible so that if we add any of the parameters, the program should follow the rules. The parameters that can be changed are:
1. Document Types
2. Project Types (We will need a custom table)
3. Plants Groups
4. Threshold Amounts
The routing of the Purchase requisition approval is primarily based on the amount on the requisition, the Plant, and the department the requisitioner belongs to.
In standard sap we have static parameters for release staregy, but here requiremnet is dynamic, when ever you chnage any of the parameters the syatem should adapt those chnages and the existing rules must apply for new one.

Why would you change Doc. Type?
If your requirements are not firmed than you should not raise requisition.
No matter how dynamic your business is, requisition raised for a particular requirement should not vanish or change in a day or so.
Practically speaking, it seems your supply chain is not process driven.
For such scenarios you should allow to create POs directly once the requirements are firmed and aprovals covered for POs only.
Regards,
Dakshesh

Release startegy for service PO

Hi,
Can you people help me out with release startegy for Service PO and service entry sheet?
Regards,
Satyendra

Hi,
Please refer below mention format.
SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
Three steps involved in release process of purchase order.
1) Edit Characteristic: -
Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
2) Edit Class: -
After creation of characteristic, create class for release purchase order. In which you can take reference of
Class Type: - 032,
Status: - Release,
Class group: - Release strategy class,
And put reference of your characteristic, which are created by you in first step.
E.g: - Class u2013 REL_PO
3)Define Release Procedure of purchase order: -
In this step four processes involved.
1) Release Groups
2) Release Codes
3) Release indicator
4) Release Strategies
1) Release Group: - In which you can define release strategy group
For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
2) Release code: - In which you can define release code. Enter value as
Release group: - 01,release code: -01 u2013 Purchase Head,
Release group: -01, release code: - 02 u2013 Auditor.
3) Release indicator: - In this step you have to define release indicator.
Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
4) Release Strategy: - This is the final step for release strategy.
Assign release code 01, 02.
Click on release prerequisites, select 02 u2013 check box and click on continue.
Click on release status button, enter release indicator X, I, S and click continue
Click on classification button, Enter values of purchasing group for which you want to created release strategy.
Note: - Create characteristics for service order document type in CT04.
Regards,
Mahesh Wagh

External program to reset release startegy

Hi All,
Can anyone tell me how to reset release startegy from an external program. I understand that there are some exits avaialable to do it. I dont want to add my logic in an exit. Based on my program conditions I need to reset the release startegy of the P.O.
Any Bapi of FM that is available.
Thanks,
Anupma

BAPI_PO_RESET_RELEASE soved the probelm. U need to copy and remove std. check and it will work fine.
Thanks,
Anupma

Purchase order release startegy

Dear Experts,
We have got release startegy for five release codes i.e L1,L2,L3,L4 and L5 for purchase orders
Release startegy is based on Pur order category,doctype, Net order value and Pur group.
For L1-L5 authorisation(all authorisations) is given for General managers.
Currently when emergency is there general Manager has to release L1 to L5 all release codes.
Requirement is that instead of releasing all can it be possible to release only L5 so that all can be released.( This authorisation is for only for L5)
Once the authorisation is there for all any customisation possible for releasing code L5 so that remaining all release codes can be released.
Please suggest.
Regards,
Dayanand

Hi Mr.Shawn,
I have removed ticks for L1,L2,L3,L4 in Release prerequisites then release startegy L1 L2 L3 L4 kept as Released.
Then Even if release one all releasing.
But Requirement is that when only L5 is released only All shall be removed, other wise remaining Releases shall be based on the old procedure only. L1 to L4 shall be L1 is released then only L2 can be released principle. But in case of L5 releases all shall be released.
Is it possible, what needs to be done ,please suggest.
Regards,
Dayanand

Release Startegy for Item Category

Hi ,
Can we have a release startegy for PO for Charcetrstic Item category.
It do not have any reference in in Table CEKKO for any field.
Can you tell me how can I activate the item category as a charcetrstic value in PO release startegy.
Thanks,
Lekhram

PO release strategy always work at the header level but if oyu want to add the item level field as a char (in your case Item category) than you need use the user exit to insert the field in CEKKOZZ include of the CEKKO structure.
Use the user exit M06E0004 to insert your field in CEKKOZZ include.
once you get the field in this include then create the Char and use in classification.
But make sure one thing is that
Suppose you create the first line item of PO with Item category D and than you insert the second line with item category L and your release stratey doesn't have the both the item category than you are in problem
Or suppose your first line has blank item category and second one has item category than also you will have issue.
so make sure you create the PO for same item category without any othe combination to work with release.

Reg Release startegy, Class n characeristics

Hi
This is regarding PO release strartegy
I setup Release strategy for PO's in Development system, for each release startegy allowed characteristic values are mentioned during config as expected
I released transport to quality [we have 2 systems
1. In One quality system i forgot to maintain classes, i maintained class, but still i am getting error 'Error in classification (class 032 class type 032)'
2. in another quality system class and characteristics are maintained before releasing transport. when i see SPRO, system hasnt assigned allowed characteristics values for each release startegy? why?
Do i need to perform any thing else other than creating characteristics and classes?
What task should i b doing in target system
Thanks in advance

Thank you
i understood exept 'donot open the client in quality and assign the values' what does this mean ?
I am doing CL20N in quality only ?
i understood in Qulity[target sytem]i must perform below
--> create characteristics
--> create class and assign characteristics
--->CL20N assign allowed characteristic values for each release startegy

Difrence between work flow n release startegy

hii frnds
can anybody tell me wats the difrence between work flow n release startegy ..
thnks
rohit

Workflow could be generic and can be configured for any process you want.
When you want to control the releases of the documents depending on the parameters that you want to configure, you use the release strategies. While configuring release strategies, you can develop some workflows.
Release strategies is more of a functional concept and workflow is the technical implementation.
Regards,
Ravi

Release Startegy

Hi,
We have configured PO release strategy by taking characters as Plant, Document Type, Value & Material Group.
To be clear release is working fine when we consider a single material in line item of PO.
We have 60 material groups and the release startegy is common for the material groups from 1 to 50 and the remaining 10 material groups 51 to 60 have different release strategy.
If I create a PO with the material group from 1 - 50 i.e. two or theree materials which belong different material groups the release is not applied for that PO.
For the same materials if I create PO for individual material i.e. only single material group the release is applied.
The release for PO isconfigured at header level. but the material groups are at item level.
Thanks & Regards
Sachin

Hi Sachin,
PO release strategy is only in header level not item level. So u should not consider Plant & Material Group as both the fields are in Item level.
Our release strategy willl work if the palnt & material groups are same for all the line items.
If there are multiple combination of plant & material group then release strategy won't affect.
Reward points if its helpful to you.
Sangram

Release startegy of Service Entry Sheet

I configured release strategy for Service entry sheet with Release code 08.
When i actually go to ML81N to release the same, i get same code in the drop down but when i select the same (08), it gives me "error Release with code 08 not possible", instead it allows only to release the same with Release code R1 which is the code for Purchase Requisition.
What could be the problem ?
Regards,
Shail

Hi,
I have just configured two release strategies for entry sheet's and they work correctly in our development sandpit. when I moved these to the test client, the config is showing correctly but the internal tables have not updated properly.
This gives me the same error, but that is because the system cant actually find the release code.
Is this the same problem you are having? If so I can post the solution for you.
Cheers,
Tim

Purchase Requisition Release Procedure Modification

Hi
In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
Appreciate any guidance on these issues
Thanks
Sriram

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

Release startegy for PO

Suppose i want to define release strategy for my POS on the basis of PO value...
Can i get in detail....what characterstick?
We have only one characterstic ZPO_EKGRP.
How to define new characterstic for value release.?
Regards,
Satyendra

thru ct04 create a new characteristic for ur PO value.use:
Data Type                       CURR
Number of Chars              15
Decimal Places                2
Currency                          INR
Template                        _____________.__
tick Multiple values and Inverval valuesallowed.
table CEKKO,field GNETW
give the values in the value tab
save it and assign it with ur class.
regards,
indranil

Data migration for PO Release startegy,PO cnditions

Hi All,
is it possible to data migartion for PO release strategy, PO Conditions(pricing), PO History ?
If yes, please advice how i can achive this.
Thanks

PO Release strategy
You can not do the Migration of release strategy. You need to configure separately.It is better to follow the SAP notes to avoid inconsistancy.
For transportation of release strategy from one client to another client please follow the SAP notes
SAP Note 86900 & 45951
PO Conditions
You can do the data migration of condition records by using LSMW or BDC program. Please explain your requirement clearly
PO History
Do you want to migrate all the GR & IR? What is your requirment? Are you migrating Legacy to SAP.
Only open POs can be migrated.
Explain your requirement in detail.

Release strategy modification

Hi all,
I've a query regarding PR release strategy configuration. Already in our system there are release strategies working based on two characteristics i.e. 1. Purchase Requisition Document & 2. Purchasing Group .
Now, my client wants me to add one more characteristics to the existing release strategies. I've identified this field in communication structure CEBAN (CFWRT - Total value of requisition for overall release procedure).
My requirement is in few release strategies Ive to check a condition for PR total value (CFWRT) is less than 5000 Rs.
To achieve this condition I've created one more charterictics for CEBAN - CFWRT and included that in existing class and modified the release strategy. But, when I created a PR (satisfying this release condition) with total value greater than 5000 Rs. still this release strategy is picking. which shouldnt be the case.
Please help! How can I achieve this...
Thanks,
Rajan U

Hi,
As needed, you created one more charterictics CEBAN - CFWRT and included it in existing release class.And also you redesigned the release strategies but,you have issue for triggering right release statergy for correct value with conditions.
Now just cross check you should have following u201CValuesu201D in the release charterictics {CEBAN u2013 CFWRT} as
1. <= 5000 INR
2. > 5000 INR
Craete release group as PO and create two release codes C1 & C2.
Now as needed you can design your release strategy or create two release strategies as T1 & T2. Keep value <= 5000 INR with release code C1 under release strategy T1 and Keep value > 5000 INR with release code C2( or keep C1 & C2 as required) under release strategy T2.
When you will create PR with value less then 5000,system will triggers release strategy T1 and PR with value more then 5000,system will triggers release strategy T2.
Regards,
Biju K

Work flow for release startegy

Dear experts,
please guide me to configure the work flow at relesae procedure,
1 ) if the lower level approved the document, how the mail will goes to next level approval's SBWP ?
2 ) if the lower level approved the document how the alerting mail will trigger to the next level users mail id ( ex : outlook ) ?
will reward points accordingly

Hi,
http://www.sap-img.com/workflow/sap-workflow.htm
http://www.sap-img.com/workflow/workflow-faq.htm
http://www.sap-img.com/workflow/workflow-of-purchase-requisition-release-strategy.htm

Release startegy modification

Similar Messages

Maybe you are looking for