Number of chars in the PR Release strategy

Hello gurus
How many chars are allowed in the PR Release strategy? , Is it possible to set up the PR Release strategy with item wise and overall release.
Thanks
JJ

Hello:
You can calculate this value using the variation calculation. For exapmple: if N is the number of positions and M is the number of characters (or leters) teh Variation is
V(n,m) = n! / (n-m)!
where the operation n! = n * (n-1) * (n-2) .... 3 * 2 * 1
In your case you have 10 positions for cost center and 26 leters plus 10 numbers as characters.
V(36,10) = 36! / (36-10)!
V(36,10) = 36!/26!
V(36,10) = 3635343332313029282726! / 26!
V(36,10) = 363534333231302928*27
V(36,10) = 9.22393E+14 possible cost centers
Best regads,
Jose Luis

Similar Messages

NUMBER OF CHARACTERISTICS AND VALUES IN RELEASE STRATEGY

Hi there, how R U.
Please, can any body help my with this one ?
How many characteristics may I have in a release estrategy for purchase order an contracts ?, how many values could a characteristic have ?, if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
I hope you can help me.
Have a nice day.

How many characteristics may I have in a release estrategy for purchase order an contracts ?,
You can have as many number of characteristics you want for release strategy, no restirction
how many values could a characteristic have ?
You can have as many as you want, no restiction
if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
Release code you can define only 8 and if oyu want more release code than create new release group and assign more release code
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
the release strategy can hold only 8 release code but every release strategy you can have more than 8 charcteristics and each char can have n number of values and that can be decied at char creation level

How to check the PR release Strategy change date?

hi,
how to check when the PR Release Strategy chagned by someone ...?
Regs,
S J Solanki

Hi
You can directly go into the Purcahse order & check for the Heder changes which will give the Changed Date
If you need to use two table to find out the date when the Strategy was changed.
Use Table CDHDR & CDPOS. Object key is the POurcahse order number
Thanks & regards
Kishore

Exception:"Decrease the number of char between the beginning of the document and its root element"

I'm now using a javabean in my jsp page to parse xml;when my xml file's size is
about 10k,it just work fine;when my xml file's size became 50k,it throws the followng
Exception:
Failed to open xml document,Failed to retrieve Public id or system id from the
document. Decrease the number of char between the beginning of the document and
its root element. But when I run this javabean in JBuild ,it works fine no matter
how big the xml file becomes;
Why? the error message is in the attachment.

The prologue must be included at the top of the document, followed by the root
          element.
          joden2000 wrote:
          > what does this exception mean:decrease the number of char between the beginning
          > of the document and its root element? When my xml file is about 10k,it works
          > just fine,when it becomes 50k ,the exception show.How can I deal with this?

User exit (To change the PO Release Strategy): M06E0004

Dear Experts,
         I am trying to implement the enhancement for changing the PO release strategy, using exit M06E0004 for following situation.
If PO is already released and then if any changes made to it affects the net amount which makes it less than previous net amount. We have to change the PO Release indicator to 'Blocked'.
We have tried to change the value of USRC1 USRC2 USRN1 USRN2 of structure E_CEKKO but it is not workingu2026
Please help me *how / what to change in the E_CEKKO structure*.
I am new to User Exit.

Hi Nagarajun,
I am able to solve this problem.!
All u have to do is follwoing two step.
1.maintained a flag in ur enhacement part (FM to Z_FIND_PO_RELEASE_STRATEGY)
inorder to know whether the current PO is without PR or not then export its value to memory.
2.Do enhancement in standard FM ME_REL_STRATEGIE_EKKO
(which is used to reset release strategy and indicator).
Inside this fm u can find below code
if xchange ne space.
*- Strategie geändert --------------------------------------------------
    if e_frgst ne i_frgst or
       e_frggr ne i_frggr.
      perform reset
         using e_frgst e_frggr
               e_frgzu e_frgkz e_frgrl.
      e_reset = 'X'.
*- Wertänderung prüfen -------------------------------------------------
    else.
      if t16fb-kzfae eq '4' or
         t16fb-kzfae eq '6' .
         perform currency_conversion using *cekko-waers
                                          bwkurs_old
                                          hwaers
                                          fwaers
                                          bwkurs
                                    changing *cekko-gnetw.
        f1 = *cekko-gnetw * t16fb-tlfae / 1000.
        f1 = f1 + *cekko-gnetw.
        if cekko-gnetw gt f1.
          perform reset
            using e_frgst e_frggr
                  e_frgzu e_frgkz e_frgrl.
          e_reset = 'X'.
        endif.
      endif.
    endif.
else.
    perform reset
       using e_frgst e_frggr
             e_frgzu e_frgkz e_frgrl.
endif.....
above code is use to check the PO amount and with old net amount,Since normally code is done to reset indicator only when amount is greater than old one, u can copy above code and modify with ur condition(i.e flag) and paste in last line.
Please check & reward is useful.

Release Strategy with New Class and Char.

Dear All,
I have facing problem when creating the new release strategy for different country. i have create new Characteristic and class for new Release streategy.
when i going to add in Release group.. system giving the error.
Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
My existing Characteristic for india :
ZP0_GNETW     Total net order value     CURR     15     2     INR
ZPO_BSART     Order type (Purchasing)     CHAR     4     0
ZPO_EKORG     Purchasing Organization     CHAR     4     0
ZPO_EKGRP     Purchasing group     CHAR     3     0
New Characteristic for South africa :
ZPOSA_BSART     PO Order Type ATSA     CHAR     4     0
ZPOSA_EKGRP     Purchasing Group ATSA     CHAR     3     0
ZPOSA_EKORG     Purchasing Organization ATSA     CHAR     4     0
ZPOSA_GNETW     Total net PO value ATSA     CURR     15     2     ZAR
ZPOSA_WERKS     Plant     CHAR     4     0
Please help me how do configure 2 release strategy for 2 country.
I will be very thankfull to u.
Regards,
Vishal Garg

HI Biju K,
I can use exising Characteristic Like Purchasing Organization & Purchasing Group & Plant etc. But in the case of Net order value : ZPO_GNETW Total net PO value for my indian company Currency is INR and for My SA company currency is ZAR. What will i do in that case.
Please explain..
And aslo clear the concept of creation of new Characteristic as Company Code & design different release strategies based on company code. How i can do that..??
Please explain in details.
I will be highly thankfull to u.
Regards,
Vishal Garg
9810402156

Release Strategy Triggered even if the characteric values were not correct.

Hi,
I have configured release strategy based on characteristics
Purchasing group and
Document type
It has 2 release indicators with 3 levels of release.
There are 2 release strategies assigned to same group 01 but have different release codes namely 01,02,03,04
Release Strategy A1has
Doc type NB and Purchasing group 120
Release Strategy A2 has
Doc type ZINT and Purchasing groups 130,131,132,134,135,136,137,138,139
However a strange thing happened.The release strategy was triggered for doc type NB and Purchasing group 190.
This purchasing group is not listed in either of the 2 strategies
Can any one explain why the release strategy got triggered?

That means the old release strategy is not cleraed from the system
do one test
Go to CL30N tocde and enter you release class and class type 032
hit enter
now here enter the value of your char which is in the PO and hit Find in initial class from header
see which release strategy is pulled by the system
here you will see the release strategy and make sure that is not other than what you expect

How to determine the right PR Release strategy

Hi Experts,
Could u help me to solve this problem!
As our business, we want the system automatically determine the right Release Strategy based on the total Amount(amt) of PR such as
- if PR total amt <= 1000 USD --> must checked by only Department Manager (DM)
- if PR total amt >1000 USD --> must checked by Department Manager (DM) and General Director (GD)
so i've already configured system like that:
1. Create characteristic : CEBAN_GSWRT (Structure CEBAN ; Field GSWRT)
2. create anew Class CEBAN_GSWRT, which associated with above Characteristic
3. Create release Group "03", which associated with above Class (CEBAN_GSWRT) and cheked "Overall Release PR"
4. Create Release Code DM ; GD
5. Create two Release Strategy such as:
5.1. Strategy 01 - DM Only, which have only DM release code & assigned to class CEBAN_GSWRT and the value identified here is <=1000 USD
5.2 Strategy 02 - DM -GD , which have DM & GD release code & assigned to class CEBAN_GSWRT and the value identified here is >1000 USD
then, i created two PRs, one have amt <1000 USD , another >1000 USD, but the system alway get the same Release Strategy 01,its mean that system allway apply the first case Amt of PR <1000 USD.
Note: In the Document Type i checked Overall Release also!
So, pls help me to show out wrong or missing steps!
Thanks in advance
Vietttq.
Edited by: viettq on Sep 1, 2009 4:32 AM

Hi,
Please open the below link, it will help you to understand the complete step by step process:
http://www.sap123.com/showthread.php?t=59

Item category control the release strategy?

Hi,
Currently the purchase of a material needs to be released.
My issue is that as soon as I change the item category in the sales order,
the material does not need to be released.
How does item category control the release strategy?
Sincerely,
Ketan

Hi Ketan,
You can set item category in the characteristic of a release strategy.
In your case, I guess the item category characteristic is already created. So you can just add the desire value into the characteristic.
Go to SPRO > IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure With Classification > Set Up Procedure With Classification > Release Strategies
Select the related release strategy, double click to view the detail. You will see there are 4 buttons in the bottom of the screen. Choose 'Classification' and enter you value of item category.
Thanks & regards,
JT

Shifting the PR without classification to classification release strategy

Hi Sap Guru,
I have deleted the PR release strategy without classification and configured PR release with classification in dev server.
Now before putting to production server I have to delete the old one and transport the new one. I have done the same procedure in Quality server but while tranporting the request the old one is not deleted and new strategy is also not mapped in Quality server.
Let me know which sequence I should delete the without classification in the system and incorporate the new release strategy with classification in live server.
Thnx
AC

When you deeleted "Without classification". the chnages were supposed to be transported to Production all the way.. first
This should be followed by your configuration through Classification.
The order is :
Characteristics first- BD91
Class- BD92
Your configuration and any other custom changes
and Classification data- BD93 in the very end
If you have messed up,
delete your strategies first, and then your classes and then your charcateristics .. transport them and restart the cycle

ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active, because the minimum value should be 5000$ to trigger the 'Release Strategy'.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy (the one for 5000$) even when the amount is less than $2500.
I have already tried with the ser exit EXIT_SAPLEBND_003, its a blank user exit and the structure available is CESSR.
Can any one tell me how to activate the 'Release Strategy' tab and the lowest Release stratedy should be selected ????
What i have investigated is that once i will set the Release Strategy to the lowest Release stratedy then that tab will automatically become active.
Please tell me how to select the lowest Release strategy using the CESSR structure ?
Points will be awarded...
Thanks
Rahul

Use this exit.
MM06E005

What is the name of the table where Release Strategy changes are maintained

Dear Friends,
Every time I make the changes in the Release Strategy Codes the Signature of the Approver changes in the Output. The problem is that it even changes for the Older PO's which are already approved by some other approver. Is there any way this problem can be sorted out? or can any one give the name of the table which records the changes made in the Release Strategy along with time and date? I will be really thankful if you guys can help me out!

Hi Chintan,
I hope you are talking about the release codes, which we attach later on to user Ids and signature means its description. I hope followed correctly.
In standard system, as and when you change the description of release code at back end, it gets reflected on front end. No matter whether its old or new PO. There is no way out to stop this. Every time you display the purchase order, the release codes checks for description at back end and displayes the same. Still, it should not bother you, as the already released PO dosent get affected for any changes you do at back end in the entire release strategy.
Beside the tables mentioned by other friends AUSP is the table where all release related entries gets stored.
I hope it clarifies.
Regards
sachin

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

How to Display PO Release Strategy in Enjoy Screen

Dear all,
I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
Thanks a lot.

Thanks 4 the reply Rahul.
I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
Thanks and appreciate if anyone could help.

Release strategy's status

Hi friends,
I've created a new release strategy with new release codes.
When I create a purchase requisition, the tab release strategy appears with the codes I've created.
But, I cannot procede to release it via ME54N even if I got a SAP-All profile, the status still a yellow triangle...
What's wrong with it ?
Edited by: Bahia M. on Nov 25, 2009 11:48 AM

Hi,
Go to ME54N,
Give the PR number and u will get release streatgy.
and check for authorisation obeject in ur profile
The authorization object Release Code and Release Group in Purchasing (M_BANF_FRG) determines which purchasing documents the user may release and which release codes he or she may use to do so. The authorization object
M_EINK_FRG comprises the following fields:
1 Release group
You use the release group to determine which purchasing documents the user may release.
Example 1:
You have created different release groups for purchase orders for different plants (for example, release group 10 for PRs in plant 0001, release group 20 for PRs in plant 0002). Using the release group, you can now specify whether a user can release POs for plant 0001 only, or for both plant 0001 and plant 0002.
Example 2:
You have created the following release groups for different document categories: release group 01 for PRs; 02 for RFQs; and 03 for contracts. Using the release group, you can now specify whether the user can release RFQs onlyor PRs and contracts as well.
2. Release code
You use the release code to determine how the user may release purchasing documents.
Example:
The following values have been defined in the authorization object for the
user Miller: release groups 01 and 02 (from example 2), and release code Z1.
User Miller may thus release POs and RFQs using release code Z1.
Hope Help U !
Regards,
Pardeep Malik

Number of chars in the PR Release strategy

Similar Messages

Maybe you are looking for