How to turn off Release strategy

We need to upload purchase orders via LSMW. While doing so, we do not wan the release
strategy to be active to avoid the need for approving each order. How can I turn off the release
strategy.

Remove the release characterstic from release stratagy through CT04 or you can delete relese
character stic from release class through cl02 .Once you upload LSMW then add the
characterstic in class.

Generally not required to turn off the release strategy once activated. But if your business
needed or you are trying in sandbox, then just remove the assignment of release class in
release group & save. Now create purchasing document, you would not have release
TAB.Later you can assign release class in the release group,when you needed for release
strategy for purchasing document.

Not sure if this requirement is to handle the cutover POs/ POs which were already approved in
legacy system, I have handled this by two ways in the past ( as due to last minute changes we
were not sure abiut frequency and need of turning release strategy to on / off

1. We have use a charactertistc (corressponding to PO date ) in Rel strategy and setup in such
a way that REL strategy is active for PO with PO date > Go-live date ( all legacy POs were
loaded with s date earlier than Go -live date)- this ensure that we need not to do on/off several
time

2. another case we created a seperate PO doc type and excluded from rel strategy, no uses was
given authorization for creation of this except the cutover / data migration team which was
responsible for cutover

OLD Release Strategy – Deletion

hi

U need to follow following sequence while deleteing release strategy

proceed as follows:
Make all the deleted release settings in Customizing again, save them, and then delete
them in the following sequence:

1. Delete the release strategies

2. Delete the release indicators

3. Delete the release codes

4. Delete the release group

5. Delete the class (Transaction CL02), provided a new one was created for the new release
strategies.

Then use Transaction SE16 to check if the entries in the tables T16FK, T16FV, T16FS, T16FC
and T16FG, are deleted there may be entries from previous Customizing

(take help from basis for this Manually delete entries from table using %sap_edit Tcode after
open the table with SE16N.)

If u have deleted in wrong sequence then reconfigure Release strategy and delete in
above sequence

Skip to Content

 ProductsProducts
 IndustriesIndustries
 SupportSupport
 TrainingTraining
 CommunityCommunity
 DeveloperDeveloper
 PartnerPartner
 AboutAbout

Search
Log On


o
o
o
o


Home / Community /Archives/ Archived discussions are read-only. Learn more about SAP
Q&A

Release strategies per document type

Good day,

I have a situation if I create a PR for a specific document type (Self-Service Auto PO) and per
purchasing group combination,

Upon creation of the PR, if the valuation exceeds R26315, SAP issues an error : PR Type
Self-Service Auto PO: Maximum spend is R26315. No release strategy could be
determined. The result is, no PR is created at all.

I cannot find the setting in config and I've gone through all different setting scenarios for
release strategies on PR level

I also need to know where I can set the setting for Auto PO creation after a PR is released.

Your assistance and guidance will be highly appreciated

Anita

Tags:

 error_caused_by_own_development

Anita Botha
May 18, 2016 at 13:23 PM
0 Likes
Not what you were looking for? View more on this topic or
13 replies

Ashok Kumar Telugu replied

May 18, 2016 at 09:30 AM

I suspect that the message you are getting is Customized one. Can you share the Error message
details along with its Application area and message description?

0 likes
Anita Botha replied
May 18, 2016 at 11:10 AM

Yes it must be customized, but I cannot find it. See image. That is all I get. I cannot navigate
further into the message. Nothing happens and if I click ENTER, no PR is created

0 likes

Ashok Kumar Telugu replied

May 18, 2016 at 11:18 AM

You should contact the available programmer or anyone who have knowledge of identifying
the enhancement / badi's immediately.

0 likes
 

Jürgen L replied
May 18, 2016 at 09:35 AM

Have you already contacted the colleagues who have originally customized and supervised the
release strategy?

0 likes

Anita Botha replied

May 18, 2016 at 11:11 AM

The person no longer works for our company. He doesn't reply to my emails either.

I was just dropped into the hot water

0 likes

Jürgen L replied
May 18, 2016 at 11:34 AM

Then make use of the transaction ANST (or ANST_SEARCH_TOOL) to find where the
modifications in the program have been made.

This pop-up is home-made, and this message does not exist in standard SAP.

The values are even incorrectly shown in the message, the R in the message is the end
of currency ZAR.

SCN is not where you should address this kind of question. contact your supervisor, there must
be more ressources than just you to analyze own developments.

1 likes

Sudhakar Chaganti replied

May 18, 2016 at 09:39 AM
Hi Anitha

Release strategy couldn't determined means we need to check master data setting and
configuration settings like characteristics (ct04) and class (cl02) and cl20n

what is your release strategy combination? could you please explain details, if possible share
screen shot.

@auto Po use the ME59n t-code to create auto Po

setting required

Need to maintain the inforecord in me11

need to maintain the sourece list me01

auto po tick in purchasing tab in mmr

auto po tick in vendor master and execute above t-code me59n

Thanks

Sudhakar

6.jpg(23466 B)
5.jpg(41430 B)

0 likes

Anita Botha replied

May 18, 2016 at 11:04 AM

Hi,

Thanks for your reply.

I already checked CT04, CL02 and CL20N. The value R26315 is no where hardcoded on the
doc type or even visible to overwrite or delete. My value for release is R0-R3000, PRC
release should be determined. If I create a PR between 0-26315, the release kicks in, but if I
exceed R26315, It complains about maximum spend for the doc type and not even a PR is
created

For the Auto PO, I did set config settings for services as Auto PO, maintained the tick in the
vendor master, but still, no PO is automatic created for the PR. The PR is not even visible in
ME59N.
We don't use auto PO's for stock products, because we have existing contracts in place with
release orders

0 likes

Naveen Kumar KJ replied

May 18, 2016 at 11:10 AM

I am not very sure about the release strategies & valuation involved it,

but for auto PO from PR, please look into the below points, it might be needful.

No configuration settings needed,

1) Material Master purchasing view tick automatic PO check box

2) Vendor Master purchasing view tick automatic PO check box.

3) Maintain Source list for Vendor & Material.(ME01)

4) Maintain Purchase Info Record.(ME11)

5) Create a Purchase Requisition.(ME51)

6) Use T.Code: ME59 & execute for PR for vendor, you will be able to create automatic PO.

Note:

During creation of PR ,select check box of Source Determination in the 1st screen of ME51
/ME51N

Ensure that Purchase Info Record should be there.

If you have more than one vendor then fixes only one vendor in source list.

For Service auto- PO, you need to activate Automatic Purchase order creation for Service
requisitions in ML91. Create info record based on Material Group,For Automatic PO , info
record is mandatory

0 likes
Anita Botha replied
May 18, 2016 at 12:19 PM

Thank you.

For the PR doc type self-service, purchasing group combination upon creation of the PR with
the source determination, I have to reference a info record based on material group and have to
reference a contract as well because our PRC process we need to have contract in place.

I did create the contract for the purchasing group and vendor, but get the following message

0 likes

Ashok Kumar Telugu replied

May 18, 2016 at 13:12 PM
We have already informed you that you need to consult your supervisor or your immediate
lead as these pop up's you are getting are home made.

0 likes

raghavendra sai replied

May 18, 2016 at 12:00 PM

Hi, Could be a wild guess that the cl20n FOR THE release group / strategy / . Please check the
value limits have been properly maintained for that starategies to cover the limits logically . I
encountered such situation where system confused to find a proper strategy to catch upon .
Regards

0 likes

Jürgen L replied
May 18, 2016 at 13:23 PM

Moderator message: Discussion locked - take help of your local IT organization - nobody here
knows your highly customized programs.