Release Procedure of Purchase Requisition

We are trying to configure the release strategy of purchase requisition with classification system. Following field are included in the release strategy: document type, creation indicator, requisitioner, item category, purchasing organization and total value of item; but the strategy is not effecting due to the item category field. We have verified all the remaining fields and they are working properly.
Following are the characteristics detail of the item category.
1.Multiple values checked in the Basic Data tab
2.Following values set in the Value tab
         a. blank for standard
         b. K for consignment
         c. D for services
3.Following values set in the Additional data tab
         a.CEBAN in the table name
         b.EPSTP in the field name
However, we have also verified the following table and field values in Additional data tab
1.     CEBAN table with PSTYP field
2.     MEREQ3211GRID table with EPSTP field
3.     MEREQ3211GRID_DATA table with EPSTP field
4.     MEREQ3211GRID_DATA table with PSTYP field
But none of the above is working.
It will be highly appreciated if you provide help to configure the Release Strategy of Purchase Requistion with item category.
Thanks & Best Regards
M. Rehan Qureshi

Hi Muhammad
The item category applied in PR is external one (Field: EPSTP)
In IMG ("Define external representation of Item categories"), a corresponding internal item cat are defined (Field: PSTYP).
In the comm structure CEBAN, the available field is internal item cat. is PSTYP.
Hence u need to maintain the values of internal item cat for the characterisic.
By this, you will get the desired.
warm regards
sairam akundi

Similar Messages

Release Procedure for Purchase Requisitions

HI
i have making a class in cl01 then create Release Groups & link to class but when i save a group massage here Please check release classes (see long text) can anybody help me
thanks vijay

pls check the following:
http://www.sap123.com/showthread.php?t=59
regards,
indranil

Release approval procedure and purchase requisition

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

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

Release procedure for Purchase orders

Hello SAP Gurus,
Can anyone explain in steps the release procedure for purchase orders and also can any one explain how it differs from Puchase requisition release procedure.
Thanks
NDS

Hi
Release procedure for Purchase orders here is process flow.
Go to spro>img>materials management>purchassing>Release procedure for Purchase orders
1. Create characterstics -Intially you will create characterstics based on which you would like to release a purchase order.
Charactrestics are like plant, purchase order value,purchase group etc.. Assign characterstics to release class 032.
2. Create Release group say 01 and create release codes like pm(project manager), gm(general manager) etcc..
3. Create a Release starategy say s1 and assign release group to it 01 and release class 032 and department to whom this release stategy applies say MM. define the order of release say first pm followed by gm etc..
4. under classfication define value limits for release of purchase order.
5. define release indicators
6. simulate the release
7. assign if there is any workflow.
hope it helps.

Cancellation of Release of a purchase requisition

Hi,
Currently the system allow to cancel the Release of a purchase requisition eventhought the Purchase Order already created for it.
I could not locate the any system message that actually control this.
How to disallow the cancellation of Release of a purchase requisition if the processing status is 'PO Created'.
Best regards,

Dear Eric,
We cant do cancel of PR onece PO created.not only that onece release of PR we cant cancel the PR we can do only flag the release PR.
Hope this will helps you
Prem.

T.Code for Release Procedure for Purchase Order Type

Hi Frd
im working in ECC 6.0.
OMGS is t.code for Release Procedure for Purchase Order Type in SAP 4.6.
Can anyone tell me what is the t.code for Release Procedure for Purchase Order Type in ECC 6.0 .the OMGS t.code is not working in ECC.
Thanks
By
Pari

Hi Rajasekharan,
Go to tcode ME22 and enter the Purchase order number.
inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
Click on a item and press the Green Button.
U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
Actually the tcode for releasing purchase order is ME28
Reward points if useful.
Cheers,
Swamy Kunche

Define Release Procedure for Purchase Orders

Hi Friends,
We are changing Release procedure for purchase orders for one department from > $ 5000 to > $ 10000.
We defined three characteristics for the class namely Purchasing Order Document, Purchasing Order Type and Ner Order Value which is Currency data type. I Defined Release Procedure for Purchase Orders in configuration master. It's working fine, I mean the Net order Value field is updated in Configuration Client.
After transporting the above change to the Testing Client, the Net Order Value field did not update in testing Client even though I created Characteristics in Testing Client (as characters are not transportable, I created them seperately in Testing Client). I can't update the Net Order Value manually in Testing Client as it says "Client 010 (test) has status 'not modifiable' "
Please tell me how to update that field, as the net order value didn't change even after transport. I can't change manually in testing Client as the status is "not modifiable"

Hi,
Yes I have already done that.
In SPRO,
After hitting the following:-
MM --> Purchasing --> Purchase Order --> Release Procedure for Purchase Orders --> Define Release procedre for Purchase Orders
I have to process the objects in the following sequence,
Release Group, Release Code, Release Indicator, Release Strategy & Workflow.
Upto Release Indicator it is fine. After hitting Release Strategy, I should select the release strategy (which I just created) and display. Then 4 buttons will be displayed namely,
Release Prerequisites, Release statuses, Classification, Release simulation.
Upto Release statuses it's fine. Afeter hitting Classification,
the values of Purchase document & Order type are populated, but the Total Net Order Value is Blank. It is supposed to populate the amount & 10,000. But it is not.
Actually that amount will be stored in the field GNETW of table CEKKO. But CEKKO is a Structure not a table. So I can't update the field.
Please advice me...
Thank You,
Nag

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Overall release strategy in purchase requisition

hi,
how do i configure overall release in case of purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics? is their required two seperate classes for item and overall release? i've allready chosen the field BSART and GSWRT for item wise release,
plz help me in details
regards
Aniruddha

Hi
For PRs, there are two types of release procedures available
With classification
With this we can release the PRs both items wise and in their entirety
Without classification
With this we can release only at item level
When you create the Release Group under the release procedure with classification
you check the box " ov Rel P Req (Overall release of purchase requisitions
This Determines that the items in a purchase requisition are all released at
the same time (rather than individually).
This should help to relsove your problem.
Regards
Vikrant

Redetermine release strategy for purchasing requisitions

Hi Guys,
How can I redetermine the release strategy for purchasing requisions when changes on the costcenter (EBKN-KOSTL) are done -
I know that it will be redermined when I add the costcenter as charateristics in customizing for release strategy but thats not an option
I also tried to add coding in userexit for changing the communication strategy (Include ZXM06U13) but this exit doesn't provide information of the document number and position (EBAN, EBKN ..) so I can't find out if changes have been made
I spend several hours trying to find solutions for this issue but no working results so far ..
I hope you can help me on that
TIA
Manuel

Hi,
Note that EBKN will have entries corresponding to a PR only when it is
saved or checked, so KOSTL will not have any values for a PR which is under
creation. You should always use fields from structure CEBAN while
creating characteristics for Requisition release procedure as it
contains most of the relevant data about a PR under creation/change.
I would advice you to check the note 365604.
Please also check the changeability indicator in the customizing:
transaction OLME -> Purchase Requisitions -> Release Procedure -> Procedure with Classification -> Set Up Procedure with Classification -> Release indicator -> check the detail screen for settings.
Please check additionally the possible values for your characteristic cost centre (transaction CT04).
Regards,
Edit

Release procedure for Purchase Requsition and especially f. a document type

Dear Experts,
how can I establish a release procedure. I need to set up the procedure
without classification. But it depends on a document type.
I have been to the customizing section with spro
Materials Management/Purchasing/Purchase Requisition/Release Procedure
and have choosen "Set up Procedure without classification. ".
But can I assign a document type and how is the handling generally with.
Release Codes
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Thanks
Ilhan

Hi Ramesh,
You are saying:
"Click on the Release strategy button under item tabs". Where is this button.
All what I have is: Tab for "Material Data", "Quantities", "Valuation", "Account Assignment",
"Source of Supply", "Status", "Contact Person", "Texts","Delivery Adress", "Customer Data",
on calling of Tcode me54n I get immediatly a message
"Purchase Requisition 5000000131 can not be released" although I didn't enter any number in it
Why does it refer to a PR Nr. generally . I think it is pre-filled- How can I call this transaction without this message ? Or how can I call this transaction so that I can type in my own Purchase Rq-Nr.
Regards
Ilhan

Perform check after release step of purchasing requisition

Hi,
does anybody have a suggestion where to place best some logic which needs to be performed after a release step is performed successfully.
background: we use different types of Purchase requisitions, while each one is assigned to a static release strategy. I like to change it in more dynamic way by adding certain logic after a release step is performed.
example: if preceeding release step was 10 and purchase requisition is of type x then check purchase value and account assignment in order to process the current stepo automatically.
Currently the logic runs during a nightly job, but I would like to add it immediately after a release has been performed. I would imagin something like user exit, BusinessAddIn, or an event which I can use assign the job.
Can anybody suggest something?
Thanks in advance
Best regards
Torsten
Edited by: Torsten Hübsch on Apr 29, 2011 10:36 PM

Hi,
Enhancement M06B0005 is relevant for PR in case of overall release
Check on trx SMOD :
Enhancement        M06B0005
Short text         Changes to comm. structure for overall release of requisistion
--> Function module                Short Text
EXIT_SAPLEBND_004              Changes to Communication Structure for Over.
Enhancement        M06B0002 is for item-release
Short text         Changes to comm. structure for purchase requisition release
-->
Function module
EXIT_SAPLEBND_001
BR
Nadia Orlandi

Delivery Date getting Copied to Release Date in Purchase Requisition

Hello,
When i am releasing the Purchase Requsition, what ever the Delivery Date the system is proposing based on the Planned Delivery Days given in Material Master is copied to the Purchase Requisition Release Date.
Is there any error in Customization ??
Regards,
Kumar

Hello Shakthi,
System is considering Delivery date as Release Date when you create the purchase requisition.
Thanx & Regards,
Kumar

Rejection(release refused) of Purchase requisition?

Hi all,
Sorry to post again.
In ECC 6.0 i have to reject a Purchase Requisition in the transaction ME54N.
When i am rejecting a PR in ME54N an event in Business object type BUS2105 called 'Rejection_start' is getting triggered. There are two more event in this business object 'Rejected' and 'Rejected_stop'. This is the root cause of my doubt.
Will PR be rejected by just pressing the Reject button in the transaction ME54N or there is some more to be done.
Regards,
Gautham P

Hi,
Just click on the reject button and save the PR, then the PR gets rejected.
As you are asking about the bussiness object BUS2105 and the events in the business object the details are as follows:
Rejected' : This event is triggered when you are pressing the reject button and save the PR
'Rejected_stop' : This event is triggered when you are cancelling the rejection ( You are approving the PR by pressing release button) after rejection of PR.
Regards,
sampath

Wrong Release date in Purchase requisition wh later than requisition date

Hi,
Purchase requisition created through Planned order then Source (contract) is assinged through Transaction ME57.
After that in display of PR as found below mentioned below,
Release date is 27.11.2008 and Requisition date is 04.12.2008. MRP type maintained in Material is Auto Reorder point.
Checked In display changes of PR as Planned delivery time new value is 45 (45 maintained in Contract and contract assigned in source list) and old value is 0 (Material master-MRP 2 view) on 04.12.2008.
My question is How come PR release date as past as 27.11.2008 when requisition (PR creation date) date is 04.12.2008. Suggest any setting required to check.
Looking forward to your expeditious response.
Regards,
C. Sundar Rajan

Hi,
If I guess, there is an exception message "06" on the PR.
check with MDO4, if there is the exception message 06 that means :
In order to get material at requested time you have to release the PR in the past. This message help the purchaser to detect the problem and try to reduce to lead time by calling the supplier.
PR release date = Requested date - safety time- lead time - setup time - processign time- ....
If you want to change the system behaviour you have to change to chage the item strategy ont the:
MRP3/Planning/Strategy group.
best regards

Release Procedure of Purchase Requisition

Similar Messages

Maybe you are looking for