Release approval procedure and purchase requisition

Question

Hello gurus,
just now I discovered a strange behaviour (in my view) in one of our client's system:
There is a release strategy for certain purchase requisitions. When I create one of those, the release strategy is applied and the Requisition Processing State is set to "In release" automatically.
But now comes the strange part: I can create a PO and copy that same purchase requisition item into it and save the PO! I.e. I can order the item, even though there was no prior release of the purchase requisition.
Unfortunately I cannot try myself right now, but this is not standard behaviour, or is it? Where is the sense in having a release strategy when the item can be ordered anyway, even without release?
Thanks in advance
Alicia

Answer 1

Hi Alicia,
Go to transaction OLME -> Purchase Requisition -> Release Procedure         
-> Procedure with Classification -> Set Up Procedure with                   
Classification -> press button 'RELEASE INDICATOR', make                    
'double click' in your last release indicator and check if the flag         
'REL.FOR ORDENING' is set or not.                                                                               
Go to transaction OLME -> Environment Data -> Define Attributes of          
System Messages, and see if you have defined the message                    
06 055 as warning or error?                                                 
Please check additionally if you have in EBAN (for the requisition) the fields FRGKZ, FRGZU, FRGST filled with entries.
Also deactivate your user exits and check the behaviour again (see note 365604).
Regards,
Edit