PR release procedure problem

We are using SAP 4.7 EE Version.
Regarding PR release procedure, I have created PR release procedure by using characteristics with Plant, Total value of the item, document type, creation indicator and account assignment category.
Created class PR_RELEASE with above-mentioned characteristics. The same is used in PR release procedure.
When I am creating PR, the release procedure not picking up for standard procurement (stock material) account assignment category.
We have identified the problem with account assignment category u2018 u2018 (Standard) while creating PR. For other account assignment categories (K, U, X, A), it is working fine.
Recommend any SAP note numbers if you have or known.
Points will be rewarded.
Thanks,
SK
Edited by: s k on Jun 9, 2008 2:11 PM
Edited by: s k on Jun 9, 2008 2:12 PM

Hi
Blank Account assignment does not work, as you cannot create a chracteristic Value as Blank.
You need to create a new release strategy without the account assignment category chracter.
Or remove the account assignment Chracterisitc from the release strategy
Thanks & Regards
Kishore

Similar Messages

Release procedure problem and error

Dear Friends ,
I facing some major problems in release procedure , i had configured one release procedure in 4levels , due to some reason i had deleted 3release groups and codes due to it was not working . But after deleteing in purchase order it showing all release level and only firest level is working unable to make MIGO and other release levels are not working . The relese code which i had created is appearing in RFQ/CONTRACT etc automatically . I had not created for this any release level . It's very very different case ....till date never faced and heared . How to resolve this probelm . Due to what reasons this kind of problems occurs .
RB

Hi,
Try to delete all the release procedure available in the system.
First try to do the documents coorectly and configure.
You might have done mistake in assigning the charcteristics to the class
Please try create a NEw release procedure once again.
Don't worry about the procedure in the RFQetc...
G.Ganesh Kumar

Release procedure problem

Hi Gurus,
          I created a release procedure for PO. i created a single chs based on total amount of PO and assigned it to a single class. then configured it for 5 release codes. all the simulation is working fine.
          But when I created the PO worth of 6 laks, which is above the level of last release code >=5 laks. when i go for release in ME29N or ME28 its giving an information message saying "document is not applicable for release procedure. in ME28 i am getting "message no documents found" for my release code and release group combination.
          Where should i have gone wrong. give me some suggestions.
Thanks & Regards,
Poorna.

Hi,
Your Maximum amount of PO which is applicable for release strategy is 5 Lakhs for your last release code.
Now if you create the PO for 6 lakhs then how the system will consider the release strategy.
Thats why you will not find the same in ME29N or ME28 to release the PO.
So you need to change your Characteristics value for last release code from = 5 lakhs to >= 5lakhs.
then system will consider the release str for any value above 5 lakhs for that last release code,
rgds
gsc

Problem in creating Release group for Release Procedure for PR

Hi Experts,
I could not able to create Release Group ( 01 & 02 ) for Release Procedure and assigning it with a Class
( Z_CLASS_PR ) in Set up Procedure with Classification.
The following error is getting displayed.
Please check release classes (see long text)..
How to over come this problem.
Thanks in advance.
Regards,
Nani

Release group:
You are only allowed to use one class for each release object (1=PReq, 2=Purchase order). When you use the overall release (as of Release 4.0A), you are only allowed to use one class for the overall release or individual release. If you use the overall release for purchase requisitions, you must mark this for the document type (transaction OMEB, flag for V_T161-GSFRG) and the release group (transaction OMGQ, flag for V_T16FG-FRGFG). In the overall release, the system only takes into account characteristics that are identical for all items. If, for example, item 10 of a purchase requisition contains material group 001 and item 20 contains material group 002, the material group is set to BLANK for the strategy determination.

Problem on PO release procedure

Dear all
I have some difficulties over Release procedure.
I have to apply release procedure on contract and standard purchase orders and i successfully completed the configuration of release procedure on contract.
For release procedure on PO, i created the required class and charaseristics.
I am getting confusion while maintaining release group.
for contract i have maintained the release group as under.
Rel Grp Rel Obj Class Description
02 2 Z_CONTRACT_RELPROC Contract Release procedure
Kindly guide me what to be maintain in release group for PO release procedure.
Thanks & Regards
Prasant sekhar

Hi,
You can not assign More than One Class to "Release Groups".
Create all the Characteristics for RFQ, Contract, PO etc for CEKKO table ...
Then Assign all these Characteristics to a Class...
Then maintain
Release Groups
Release Codes
Release indicator
But Create Diff Release Strategies for RFQ, Contract & PO...
for each Release Strategies you can maintain Same Release Group or Diff Release Group..
whenever you are trying to create Release Strategie, You will Blank Characteristics for that "Release Strategies",
There you can select the parameters.
Thx
Raju

PR release procedure no longer working-error MEPO 822

I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.
Situation :
One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.
NB = NOT subject to release
RNB = SUBJECT to release.
So when they :
create a PR with document type RNB - it will goes for approval.
create a PR with document type NB - it will not go to approval.
It was working fine until after they created a new document type which copied from NB, called ZTP.
ZTP = NOT subject to release.
They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.
Findings:
I've created a PR, and go to ME45N to release it but system prompt me an error message
"Purchase requisition 10000066 cannot be released". I check on the message data, the error coming from MEPO, message number 822.
So i check in OSS and found a note which is similar to this case.
Note 939371 - Overall release PR using ME54N gives error MEPO 822
Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text
But my question is,is it also applied to ME51N and without external application as per my client's case?
Please anyone help.
Thanks.

Hi guys!
Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.
Here's the reply from SAP :
Purchase requisition 10000066 cannot be released
Message no. MEPO822
Now click the other requisition button and let say
choose Purchase requisition 10000068,
Execute ME54N again:
Purchase requisition 10000068 cannot be released
Message no. MEPO822
Comment/explanation:
The log incidence seems not having problem with release
strategy as it was ok but it was the last PR was called
everytime ME54N was called. This same as it works in enjoy
transaction ME21N/ME22N or ME51N/ME52N.
For example, When using ME21n or ME22n to create or change PO,
after saving the PO. There are 2 ways to exit the transaction,
1, enter another T-code or use /n to exit directly.
2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)
Then you can access ME23n to see the difference.
For the 1st way, ME23n won't display the last PO created in ME21n
For the 2nd way, ME23n will display the last PO just created!!!
Please see attached consulting note 595627 that explains a new
functionality as of release 470:
Due to performance problem, a decision had to be taken about the way to
use transactions. If you leave transaction ME21N/ME22N via the
exit button (F3), the expected PO will be displayed next time you use
these transactions. But if you quit abruptly (/nXXX) the PO number
won't be saved for the next transaction ME2?N.
As SAP note is the official document to explain system behavior,
this document is provided by SAP developement to explain this system
behavior to customers.
In your case, you had used ME54N and this was same as you use ME53N.
The last PO always display. You may try to view Purchase requisition
with release strategy, for example Release group R1, Rel. strategy
R1, then after this execute transaction ME54N again, the message
MEPO822 will not be there anymore.
Hope this will help you guys if you're having the same problem in future.
Thanks,
Crystal.

PO Release Group Problem

Hi All
This problem regarding Purchase Order Release Strategy.
I have deleted the existing Release group : 02 and created New Release Group: 11 for Purchase Order Release Procedure.
I deleted Release Group 02 and Release strategy in sequence.
But still when I'm using ME29N transaction, system using release Group 02 not New group 11.
I verified all Release Group related tables.
T161E,S,G,F,
T16FG,FH,FT,FC,FD,FK,FB,FE
But there are no entires for Release group: 02.
when i look into EKKO table, purchase order linking automatically to release group 02.
from which table system pulling this?
How to solve this problem
Please suggest
Thanks
SUNIL KUMAR

If these all the POs were created before you delete the release group and created new than system will not take new release group
you have to put it the old one back and release all the POs which has old release group than you delete the release group
you can keep the new one so the new POs created based on the new release group
in sm30 check this both table
V_T16FG_2 and
v_T16FG
should be clear

Release strategy problem in Purchase order

Hi Guys,
I was trying to configure Release strategy for the purchase order and this button   is not triggering in my purchase order.
I dont know where I was doing wrong and where might be the problem as I tried several times.
Can someone give me some good idea about it how to configure in a proper way.
If you need any further information please let me know.
Thanks
Krishna

Hi
I hope you followed the following steps:
1. Create Characteristic using CT04
2. Create a class and link to the characteristic using CL02( class type: 32)
3. Configuration of release procedure
    SPRO IMG->MM-> Purchasing -> PO -> Release Procedure -> Set up procedure
    A) Create release group and link to class
    B) Create release code
    C) Set up the release indicator
    D) Set up Release Strategies-> strategy and codes
    E) Set up Release Strategies -> pre requisites
    F) Set up Release Strategies -> status
    G) Set up Release Strategies -> values for strategy
Regards,
Subhashini

PO Release Procedure Setup

I have configured the PO release procedure for PO with header value of more then 25000. In the process I have created the following -
1. Custom Characterstic
2. Custom class
3. Release group
4. Release code
5. Release indicator
6. Release strategy
but the problem I am having is that the workflow event 'ReleaseStepCreated' is generated in the system even for PO with header value of less than $25000. Also the 'Release' tab is not appearing in the PO header.
Please help. Appreciate you time.
Sridhar Jami

I think this issue is also related to mis entries in SWEC.
Go thru' this Note 797775 - Entry in Transaction SWEC hinders workflow. Verify all the steps stated in this note even you think it might not be the right note.
Regards, IA

PR release procedure

Hi,experts
Good Sunday.
I finished the configuration of PR release procedure,but it is not effective as I created PR.
My scenario of PR release procedure:
1) Create two characteristics Z_WERKS,Z_GSWRT mapped by CEBAN-WERKS and CEBAN-GSWRT.
2) Create a class Z_PR_REL_CLASS includes above two characteristics.
3) Create a release group named AA refer to class Z_PR_REL_CLASS.
4) Create three release codes L1,L2 and L3.
5) Create two release strategy S1,S2
S1 limits the PR total item value small and equal than 1000 RMB.
S2 limits the PR total item value great than 1000 RMB.
Yes, I finished the details of the above configurations,
However, I created several PRs with the various total item values,the corresponding S2 release procedure is not adopted.
I don't know what the problem is.

Hi,
All configurations done by you are correct. I doubt, you have selected Overall release for PR or Item wise release of PR.
IF you have selected Overall release , than you need to choose GFWRT instead of GSWRT from structure CEBAN.
Also, check in step -'Check release strategy', if everything is in Green.
If all of above is correct-
Check values in Classification tab of S2.
It should be >1000 RMB.
Values in Classification tab of S1 -
Its should be 0.00 - 1000 RMB
The characterstics Z_GSWRT, Should have flagged 'Interval Allowed'
Regards
Pushpam
Edited by: Pushpam Rastogi on Feb 22, 2009 9:04 PM

BDC/LSMW for SPRO to MM to Purchasing to PR to Release Procedure to ...

Hi experts,
May I know those screen in SPRO can do BDC or LSMW? I am facing problem on trying up the BDC using SM35 on the following screen. (I can't get the transaction code).
The path is:
SPRO -> MM -> Purchasing -> PR -> Release Procedure -> Set up Procedure With Classification -> Release Strategies.. The SAP program is SAPL0ME2, but I can't execute it using SE38 since it's a program Type 'F'.
So may I know any possible way for us to use recording approach on these to do Mass insertion of data?
Thanks.
Cheers,
Wong
Edited by: Julius Bussche on Sep 12, 2008 10:37 AM

Hi Vijay,
First, you can try on SM30, V_T16FS. Simply double-click on 1 release strategy, then Click on "Classification". You will see the classification screen allow us to enter value on each characteristic of the class.
However, I try using SHDB (recording), it shows empty screen on the value for class in the 'Classification' screen.
Thanks.
Cheers,
Isaac.

Restriction for PO release procedure

Dear All,
I have to restrict the PO release procedure.
Suppose there are only 3 person can release the PO but i have to restrict that 3 person for that PO quantity.
suppose, PO quantity 1000.
Person 1 --> Can release up to 1000.
Person 2 --> Can release 1000 to 5000.
Pesron 3 --> Can release 5000 to 10000.
Here quantity is 1000 ,
Then person 1 should release the PO and others should not.
and if quantity is 10000 ,
then person 3 should release and others should not release.
Right now in my client site anyone from this persons are able to release the PO.
So i want to restrict them by PO quantity.
Please let me know that, for this any BADI or User exit is available in system.(Or is there any customization need to be done and how)
If yes how to apply that, give me step by step procedure to solve the above issue.
Please give your inputs to come out of this problem.
Thanks & Regards,
Sanket.

hi,
in the exit i have mentioned ,use the import parameters which contains structures which has fields related to that u mentioned which r populated at runtime.
check tht fields in the structures for specific users u want to rstrict.
ex:
if sy-uame = < >.
else.
endif.

Deactivate release procedure for some PO's

Hi guys
my problem is this:I have some purchase orders which must be released by a manager--->now this manager wants to delete this release procedure so that the purchase orders are free for ordering immediately.
Is there a way to 'deactivate' the release procedure only for these orders?
Thanks in advance
Bye
Massimiliano

Hi guys,
I apologize if I have been not clear..I mean:there are 4 purchasers whose purchase orders must be released by the manager..now the manager wants to delete this release procedure so that the purchase orders made by these users are free for ordering immediately because there is no time to release etc...and it is requested to send immediately to vendor and so on
Is there a standard way to cancel the presence of release strategy on PO's so these PO's can be free to manage?
Thanks again
Bye

Release Procedure Query

Hello All,
In our scenario we are using release procedure without classification.
Let say in a Startegy S1 created there are three level of approvals L1, L2 and L3.
It goes in a way that if L1 created PR it should be released from L2 level from ME55 then L3 from same ME55 transaction which is fine.
But problem comes when L2 or L3 Person raises requisition. Let say L3 level person has raised requisition then he himself can released that from L1 and L2 level from ME55 transaction as he is on last level and has authority to release the requisition.
Ideally this is should not be fair practice.
We need to know how we can control this so that person who raised requisition should not release himself/herself.
Is there any configuration setting or any other way to do. Or we need to change the strategy.
Regards
Himanshu Nijhawan

Hi,
Do not design release process of PR as you explained. PR releaser always a PR releaser only and he should not create any PR. Also PR creator always used to create PR and PR creator should not release PR.
You can easily restrict and control PR release process by having well designed user authorization matrix and release matrix. As per release u201CVALUESu201D, release matrix designed and based on authorization, control can be established for transaction codes.
Lets example: User 1 will create PR, user 2 will change PR and you have 3 release codes for releasing PR such as like L1, L2, L3 for three user respectively user 3,user4 and user5..Now you can allow (authorized to) user to do following transaction
Transaction Code----
> User
ME51N----
> user 1
ME52N----
> user 2
ME53N -
>(All users ie..user1.user2,user3,user4 & user5)
ME54N or ME55 with release codeL1----
> user3
ME54N or ME55 with release codeL2----
> user4
ME54N or ME55 with release codeL3----
> user5
If business needs, you can give authorization user3, user4 and user5 to change PR(ME52N) by eliminating user2.
NOTE: For more details contact basis team and control all these by authorization object.
Regards,
Biju K

PR release procedure for material types

Hi all,
I have a question, I created new release procedure for combination :
1. NB pur.requsition, purchasing group + material type (let sey roh.. etc)
2. YNB pur.requsition, purchasing groups + material type (ZSTE-001, ZSTE-002, ZSTE-003).
- 3 characteristcs for pur.groups, doc.type and material type.
- 1 class
- 2 release groups (E1 and P1)
- For release group P1, In rel.strategy in classification I entered values for pur. requisition (NB), purchasing groups (001,002, 003 ect) and material types (ZUSL-001.. ect)
- For release group E1, in rel. strategy in classification entered values
values for pur. requisition (YNB), purchasing groups (001,002, 003 ect) and material types (ZSTE-001, ZSTE-002, ZSTE-003)
So, problem is that if I enter pur.requisition YNB and material type ZSTE-001, needs release; if I add item with material type ZUSL-001, there is no release.
How can I restrict the values so that is giving error if by mistake is entered between material types ZSTE-001, ZSTE-002, ZSTE-003 material type ZUSL-001 in document type YNB, which is not allowed to be entered?
Thanks in advance,
Anchi

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

PR release procedure problem

Similar Messages

Maybe you are looking for