After Creation of PO Release strategy is missing

Hi Experts,
We have a problem that we have created a PO but we found after that release strategy is getting missed out.
What could be the possible causes for this?
Note: We have checked in CL20N everything seems to be in place.
Cheers,Kumar.S///

Hi Jurgen,
Very sorry for the late reply as i was not in office.
I have checked the following char in CL20N transaction,
Plant,Purchasing group,order type,total net order value,Purchase organisation,Vendor account group.
This is FYI.
Please reply ASAP.
Cheers,Kumar.S///

Similar Messages

No PO Creation without PR release strategy

Hi all,
Is there any way of preventing a user from creating a PR on which no release strategy is applied (i.e. no release strategy exists for that user) and then creating a PO from it?

This is standard functionality of SAP that whenever PR is not subjected to release strategy PO can be created against that PR.
Why do u want to not to create a PO if no release strategy is ther
If ur requirement is like that, u can develope a BADI with logic that, if no release strategy is triggered for PR, then PO can not be created

Purchase requisition release strategy tab missing

Hi all
I configured purchase requisition release strategy and ME51N is working issuing no error but it is not displaying Release Strategy Tab , please help me where i am wrong.

hi,
check few reasons:
1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
2. check the release strategy OMGSCK, is there any problem with your release strategy...
3. Check whether you have maintained all the classified field in the document or not..
4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
regards
Priyanka.P

How to block PR creation with no release strategy

Hi,
We have this PR release strategy implemented. Currrently, user are able to create the PR even there's no release strategy determined. Thus, PO can be created as the processing state is "02 Active".
Would like to block user from creating the PR if there's no release strategy determined. How should we do in order to achieve this?
Many thanks in advance.
Sue

Hi Sue
Assuming that you are using release with classification.
Create a new characteristic for PR document type (CT04)
Attach this characteristic to your Class (CL02)
Create new release strategy and in Characteristic data you will have to assign all your PR document type. This will ensure that all the PRs need to be released.
Regards
Rajesh
-Do reward if this is useful.

Release strategy for PR in Third party case

Hi,
We have this third party scenario where Purchase reqs are created at the time of Sales Order creation. A release strategy is attached to these purchase req by defining a custom field in MMaster, whenever qty goes up or equal to tht field release strategy is applied.
The problem is, for the same material's PR, the release strategy is set in one case whereas for other PR (of different sales order) it is not set. Please help let me know what could have gone wrong.
Thx.
Amit

Per your information you say that based on a custom field qty in material master release strategy is triggered. Do you have any charecteristic maintained for the Release strategy anything other than this parameter- because there must be some difference between the 2 Reqs.
Or check the change history in Material master it may be possible that at the time of second sales order if the field value was changed so that release strategy was not triggered.
Please give more details
Thanks
Deepak

Purchase Order not subject to release strategy

Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisah

hi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic   e.g. NETVALUE
Click Additional data Table name CEKKO      Field name GNETW    and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X    Mutliple values
X    Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group   Rel. Object   Class                 Description
02                                 REL_PUR        Rel. Strategy for PO
Release codes - New entries
Grp         Code
02           01
Release indicators
Release indicators           Release        Description
      0                                                        Blocked
      1                                     X                Release
Release Strategy
Release group   02
Rel.strategy    01
Release codes   01
Release status   0
                        1
Classification   Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
regards
ravikant dewangan

PR Release Strategy-Characteristic Z_GSWRT must be linked with CEBAN-GFWRT

Dear Experts,
I did a simple config for PR Release strategy. using Plant(Z_WERKS) and Item values(Z_GSWRT )
chose overall PR Release. During simulate release
the second level release its not able to simulate and it says check Prerequistie for second level
Can somebody expain why the system is giving me this below message.
Characteristic Z_GSWRT must be linked with CEBAN-GFWRT
Message no. ME_RELCHK056
Thank you
Imraan

Thanks for the solution that helped me to understand PR Release much better.
Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
In my PR Release strategy with 2 levels I have these below things:
Rel Groups : 1 Group with name AA
Rel Codes: For AA is A1, For another AA is A2.
Rel Indicator: nothing is selected, am not sure what to do in this step.
Rel Strategy : For AA is S1, For another AA is S2.
I created class Z_GFWRT but am not sure which group I should assign it AA or I have to create another new group for Overall release.
After I checked the release strategy the system is giving me this below message.
No release group exists
Message no. ME_RELCHK014
Please can you walkme through in this process. This is first time I am creating a PR Release.
Thank you Very Much
Imraan

PR Release Strategy Characteristic Changes

I created several characteristics for a purchase req. release strategy. I added an incorrect value and then deleted it on one of the characteristics. Is there anything else that needs to be done to ensure that value is really deleted?
I'm receiveing an error when I ALE that I have documents that won't post for the error:
REQ_PURCH_ORG : Value "Structure Exists " not found
Structure exists is not a value associated with this characteristic.

Thanks for the solution that helped me to understand PR Release much better.
Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
In my PR Release strategy with 2 levels I have these below things:
Rel Groups : 1 Group with name AA
Rel Codes: For AA is A1, For another AA is A2.
Rel Indicator: nothing is selected, am not sure what to do in this step.
Rel Strategy : For AA is S1, For another AA is S2.
I created class Z_GFWRT but am not sure which group I should assign it AA or I have to create another new group for Overall release.
After I checked the release strategy the system is giving me this below message.
No release group exists
Message no. ME_RELCHK014
Please can you walkme through in this process. This is first time I am creating a PR Release.
Thank you Very Much
Imraan

Release strategy should revert

hi
in PO we r using only release strategy not version management .
our scenario is like this , once a PO has released and if any body tried to do any change in PO after that , then those release strategy should revert to unreleased status.
guide us where to do right configuration .
what currently happening is , if in changing mode we are giving Quantity more then previous it is reverting release strategy other wise not .
regards
sachin sharma

Sachin,
As SAP standard, release strategy will be reset if:
- the changeablity of relesae indicator set to '4' incase of PR and '4' or '6' in case of another purchasing doc (PO, RFQ, contract)
-the document stii subject to previous release strategy
-the new TOTAL NET ORDER VALUE is higher then the old one
For release strategy reset in PO i suggest to use user exit.
Reward if useful

Release strategy for RFQ's not triggered after change

Folks,
Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
1) document type (AN)
2) purchasing type (RFQ purchasing document)
It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
Message was edited by:
MdZ

Hi,
For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
As RFQ don't have any specific table where the data is stored related to RFQ.
So we Use CEKKO which only identifies the document type of RFQ.
In your case in initial process while creating the RFQ release strategy is active.
What change you have made to the Released RFQ.
rgds
Chidanand

Creation of release order possible during release strategy

Hi folks,
we have currently contract and purchase order release strategy parallel in place. Both are working fine.
We are using quantity and value contracts.
Quantity contracts are changed frequentely by the business; with every change (adding new items, changing prices of existing items), the release strategy is pulled again.
Our release indicator is set to 6 and has value change 0,00%.
The business requirement is now to release a contract with status X (e.g. 10 items and a total item value of 10.000EUR). After release, call offs can be created for all the released line items.
If a new line item 11 is added, it should still be possible to create call offs for item 1-10 but not for item 11.
Item 11 should undergo a new release.
Has anyone ever come across such requirement?
I have tried version management. However, version management will only force a new release whenever the version is completed.
Even then, the complete contract is subject to release strategy and it is not possible to create call offs.
We dont want to set error message ME347 "Release orders against contract xxxx not possible (contract not released)" to warning, as this will allow to always create call offs regardless of the contract being released or not.
Any ideas greately appreciated.
Thanks!!

I suppose program checks in EKKO whether contract is released,, irrespective of version exist it or not. IF you are able to direct it to EREV, then may be version 0 or ( current - 1 ) released can be returned.
Isn't it a special case that your version 0 data is intact in version 1; Even if someone change lines 1 to 10 , with or without adding line 11, it still triggers version 1. How do you ensure that lines up to 10 are not changed. you may have to look in CDPOS CDHDR with object Revision..
This is just an idea which you may discuss with your developer to see whether a copy of the program can be modified..

Re-set release strategy of rejected PO,after doing respective changes to po

Hi friends,
I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...
Here PO printout is possible only after the final approval...
Pls give some inputs in fixing this issue..
Thanks in advance....
Regards
Shashidhar...

Hi
What are the characteristics of your strategy?
Try to change one of them save and then rechange it to the original
eg.
If the strategy depends for example on the Purchasing Group (PG)
i mean according to different PG's different strategies working
then with ME22N change the PG save and rechange it again to the original.
or
for example If the strategy depends on Materail Groups (MG)
then do the change with MG
With ME22N change the MG save and rechange it again to the original.
I guess this will trigger the strategy again.
Hope it helps
Best Regards

PO release strategy not triggered after PO printout

Hi Experts,
I have configured PO release strategy and have given 10% tolerance to PO value.
When I change PO value (more than 10%) after releasing the PO, but before taking Print out of PO, the system triggers new release strategy.
But when I change the PO value (More than 10%) after taking PO print out, system do not trigger the new release strategy.
I want the system to trigger new release strategy after PO print out (if its going beyond the tolerance).
Please help.
regards,
Anand

Hi Anand,
you cannot reset the release once the PO is printed.
When the purchase order is printed/faxed the vendor will deliver the goods. Therefore it would make no sense if the system resets the strategy.
Please ensure that changeability of the release indicator should be 5 or 6.
Sanjeev

Release strategy of PO creation under contract

Hi,
if PO creation without any contract, release strategy is required. However, if PO is created from contract, no release strategy should be used. Pls advice how to configure it. thanks

The best option is you differentiate the PO document type i.e. create a seperate document type (ZNB) for those PO which are created wrt contract...Now while creating PO release strategy use PO document type (BSART) as one of the characteristic and there don't use this new PO document type (ZNB)
Regards,
Indranil

PR Item Level Release WF not working after Release Strategy change

Hi Experts,
           I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
I really don't understand y after changing the release strategy workflow is not working and giving the following error.
Even if i restart the workflow in SWPR the same error is occuring.
Exception occurred    - Error when starting work item 000000390118
PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
CREATE                   - Error when creating a component of type 'Step'
CREATE_VIA_WFM - Agent determination for step '0000000003' failed
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
AC00000148             - Object type 'TS' not valid
Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
Regards,
Hari

Hello Hari,
please set a breakpoint at function module
ME_REL_GET_RESPONSIBLE
and see what happends in section
    CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung über T16fW
      WHEN '1'.
If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
Best wishes,
Florin

After Creation of PO Release strategy is missing

Similar Messages

Maybe you are looking for