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.

Similar Messages

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 strategy for purchase requization on basis of document type

Hi All
can somebody can explain me the procedure for creating releasing strategy on basis of doc type
Nabil

Hi,
The below link will help you to understand the process.
Please open the below link and u will get the complete process to have the Release stretegy on the basis of Doc. Type.
http://www.sap-img.com/materials/release-procedure-for-purchase-requisitions.htm

Error "Account assignment 00 for purchase document does not exist " when u

Hai,
I am encountering the following problem when posting a PO based Invoice using BAPI_INCOMINGINVOICE_CREATE.
The error says " account assignment 00 for purchasing document does not exist".
The scenario is very simple. I need to raise an Invoice against a PO. the PO has a single line item of quantity 10 net price 10. Tax code is U2 ( 7% tax).
I am passing the following at header level.
Invoice_indicator ( as 'X'),company code,doc date , posting date, gross amount (107, currency USD, calc tax indicator as 'X'.
At line item i am passing Invoice document item 000001, po number , po item number, tax code(U2) item amount (100),
Does this error has got any thing to relate configuration matters?
Regards,
Upender

Hi Upender,
In some cases, depending on the type of PO / Posting,
you might have to populate the accounting data itab and pass in the BAPI parameter.
you can select the accounting data from EKKN for the PO.
Again it depends on the PO category, wether you need to populate Qty & Unit in accounting data.
Further, the accounting data should be exactly the same as there in EKKN ( all the fields except Qty & Unit ).
Thanks,
Ram

Release strategy for Purchase order

Hi Friends,
My client was using Release strategy for purchase order. Now we want to know the T-code for showing list of Rejected Purchase orders, T-code for for showing list of approved purchase orders, T-code for showing list of blocked purchase order.
Thanks and regards
Krishna

HI,
You can go to SE16N view table name EKKO
FRGKE Release ind. = B
FRGZU Release status = <blank>
mean, this PO yet to approve/ rejected.
FRGKE Release ind. = R
FRGZU Release status = X
means, this PO has been approved.
Hope this helps

Release strategies for purchase requisitions

Hello,
I'm having trouble with profiles and roles for release strategies, this is the scenario:
-for purchase requisitions we have two approval levels, release code S1 and S2. When release code S1 is cleared, then S2 must be approved. The head of a certain purchasing group will use S1 to approve the requisitions from his own department, and then the financial director will approve with S2. However, finance is also a purchasing group, so in some instances the finance director will have to approve with S1 and then S2.
My question is: how can we use profiles and roles so that the finance director has access with S2 to all (*) purchasing groups, but with S1 for only a certain purchasing group (in this case "500")? we can't seem to be able to define certain purchasing groups to different release codes, purchasing groups must be defined at purchsing requisitiom level.
Many thanks
Daniel

HI,
Not necessarily, you just need a different strategy for each different combination of release codes involved.
So if certain P groups need to be put through a different sequence of approvals, then have one new strategy for this group of P groups and one for the other combination of P groups.
Or however many different variations you have.
Steve B

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

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

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

Release strategy for PREQs created from PM work order

Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
Desislava

Hi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj

Release strategy of Purchase order

Dear all,
   I configured Release strategy for purchase order in which i create characteristic,Class.
   I also define release procedure for PO like release group,release code,release indicator & release strategy.
   But it is not reflecting in Purchase order.
Regards,
Nitin Patil.

Hi Nitin,.
check had you missed any step while creating the release procedure...
Follow the link it may be useful to you, this is for PR.... this is same for PO also onle differnce is in coummunicaitton structure CEKKO you neet put...
http://www.sap123.com/showthread.php?t=59&highlight=SettingsimpleReleaseProcedurePurchase+Requisitions
regards
anand

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

Release stratedires for Purchase Order

Hi
Dear All
I need a clarification that my needs cost centre based release strategy for Po, but t is not in Cekko table.i have to use customer exit M06E0004 or any other way to use cost centre as char in release st.
i appreciare if anybody can help/ give the suggestion in this regard
MVRAo

Hi,
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement,request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item)and in total. The latter approach is also termed overall release.
 Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor
of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
Procedure Without Classification (Requisition Items Only)
The conditions can be based on one of the following item characteristics or a combination of
these:
 Account assignment category
Material group
Plant
Total value
Hope this will answer your question
Thanks
Arun agrawal.

Release strategy for sales orders

Hello Gurus,
My customer has got a requirement of approval of sales order before it actually goes for dispatch, (it is inline with the purchase release strategy).
Hope, SAP does not have a standard solution for this but I understand this can be done through the "status profiles". I dont have any idea how exactly this can be configured, can someone help on this? Please guide with the stepwise configuration.
Thanks in advance.
Ajit Patro

Hi,
User statuses are always defined in a status profile.
Procedure
First, you create a status profile.
Assign the corresponding object types to the status profile.
Define the required user statuses in the status profile.
Assign the user statuses to the corresponding business transactions.
If necessary, translate the status profile and the user statuses.
To be able to work with a status profile, you first need to assign it to the order type in Customizing (Customizing for Shop Floor Control by choosing Master Data - Order - Define Order Types).
For information on how to create a status profile, see Customizing for Shop Floor Control by choosing Master Data - Order - Define Status Profile.
You have to activate the customized status profile.
Regards,
Siddharth.

Release strategy for GR?

Hi,
My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
Any help will be appreciated.
Best regard

Hi Yosea,
Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
Note: Controll always suggested at the time of making agreement (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
Hence there is no logic is going for that option
Hope it clarifies,
Regards,
Sapsrin

Release strategy for purchase requisition does not kick in

Similar Messages

Maybe you are looking for