Item Level PR Release

Dear all,
I am using PR release at Item level, I have 2line items in my PR i have refused 1 line item & approved the other, now when i m creatin the PO from that PR it still shows both the line items...
system should show only the released line items..
please guide
cheers

Dear,
As per my view, When you create purchase order with reference of purchase requisition system take both line item which you given.
But if you want to restrict the creation of purchase order for not released line item of purchase requisition.
Make Message no. 06055 as error message number via sap config.
For do this follow bellow path.
SPRO -> Material Management -> Purchasing -> Environment Data -> Define Attributes of System Messages
and make it as error message.
Regards,
Mahesh Wagh

Similar Messages

Item level PO Release in ECC 6.0

Hi All,
It is possible to configure item level release strategy for PO ?
I am sure it is not possible till version 4.7 and you please advise whether it is possible with ECC 6.0 .
If so, can you please explain how can this be configured.
Gobinathan G

Hi
As per SAP release procedure are of two types.
With classification ( Item level and Header Level)
Without Classification ( Header Level only)
For PR which is internal document both release types are applicable but in case of PO which is external document release type without classification is allowed

Item level release

Hi experts,
what is mean item level release and header level release in PR. How to configure it.
pls explain in detail
regards
arun

Hi,
Release Procedure
Use
You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
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.
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.
Regards,
sasi

PO and SchdAgreem Release Strategy at Item Level

Hello!!
I have the request to setup a the release strategy for the PO and Schedule agreements at line item level....
as far I know for PurReqs is possible to do that... but for PO and SAs it is only at header level...
Do you know if is possible to do that in configuration??

Hi,
Release strategy for PO & SA is only at Header level, since these documents are external purchase documents.
But, PR is internal purchase document and release strategy is possible at both item and header level.
i think, it is not possible to do release strategy at item level for PO & SA as you said,
Regards,
Srinu.K

PR Item Level Release WF not working after Release Strategy change

Hi Experts,
           I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
I really don't understand y after changing the release strategy workflow is not working and giving the following error.
Even if i restart the workflow in SWPR the same error is occuring.
Exception occurred    - Error when starting work item 000000390118
PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
CREATE                   - Error when creating a component of type 'Step'
CREATE_VIA_WFM - Agent determination for step '0000000003' failed
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
AC00000148             - Object type 'TS' not valid
Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
Regards,
Hari

Hello Hari,
please set a breakpoint at function module
ME_REL_GET_RESPONSIBLE
and see what happends in section
    CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung über T16fW
      WHEN '1'.
If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
Best wishes,
Florin

Whether Item Level release is possible in PO [Purchase Order] ?

Hai SAP Gurus,
Whether Item Level release is possible in PO [Purchase Order] ?
Guide me..

Hi,
In std sap system its not possible...
You can release at header level only..
Recheck it from here:
SPRO >> MM >> Purchasing >> PO >> release procedure...
Here there is no option provided for item wise release,...
Regards
Priyanka.P

PO release at item level

Hi all
Is it possible to release PO at item level.
Our requirement is as follows:
We have a field in material master of each material to be checked before PO can be released.
The PO price should not be greater than the value in the material master field for each material.
Is there any way to do this.??
Thanks in advance
JOE

Hello all
Thanks for your responses.
The industry is contract manufacturing where we quote raw material cost also to customer.
Actually this price is stored in the material master accounting 2 field.
While creating the PO , buying price should not exceed this price.
So we have a user exit to check the prices and give an error message.
In some situations like short lead time for FG from customer, they agree for higher price of raw material because of short lead time.In this case higher authority need to approve the higher PO price.
any suggestions.
Thanks
jo
Edited by: Jo George on Jan 5, 2009 9:08 AM
Edited by: Jo George on Jan 5, 2009 9:10 AM

How to restrict/hide the CREDIT BLOCK RELEASE LINK AT ITEM LEVEL of Servic

Hi,
We are using CRM2007 Stack 4.
In WEB UI Change Service Order screen for a credit service order which
is blocked for credit, at item level a link is available for release of
credit block. This link is currently accessible by all users.
Please advise us how to prevent users accessing this link for order
credit block release.
Regards
Achuthanandan

I am looking for this answer as well. Has this been answered or resolved?
Thank you,
Carolyn

Pur Requsition Release - Header and item level

Hi Team,
I have set up release procedure for header level.
I have gone thro the threads pertaining to PR release extensively on this forum and have configured accordingly.
1) At the header level release, I will get the 'release startegy' tab in the header only if I have the characteristics maintained for the PR document type. If I start assigning in the classes with 'CHARACTERISTIC' for the overall value which is GFWRT along with the Doc type, then it does not show up.
2) I have also tried at item level with plant, item val and doc type. It does show up, but for only the 1st strategy 01
THE ISSUE IS - I have 2 strategies 01 - Mgr & 02 - Fin Ctrl...It shows up for 01 , but in ME54 if I enter 02 and PR number, get the below error
The 1st level shows in PR, like wise at header as well.
If I try 2 nd level it gives a hard error as below...it should show up for 2 nd level right
"Purchase requisition XXXXX4540 cannot be released with release code 02"
Appreciiate anybody's help..
Best Regards

Hi,
Have you simulated the release strategy.
How the release effect happen.
have you set the release status with right relese indicator.
please ensure all above.
Check this link for PR release procedure:
https://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
PR release strategy
http://www.sap123.com/a/59/
SAM

Processor of PR item level release strategy

Hi All,
I need to pass the Processor determined from an item level Purchase Requisition release strategy to a WF container. The event is RELEASESTEPCREATED in BUS2009. I have created an import element container called 'Processor' from ABAP dict. data type MEACTOR.
In the binding for the WF trigger RELEASESTEPCREATED I cannot bind the 'Processor' wf container to the Event Object.
What are the steps which I must follow to add the 'Processor' to the RELEASESTEPCREATED event?
The release strategy in SPRO for item level Purchase Req release is complete and the Set-up procedure for Workflow is complete.
Thanks
Mike

Hi,
Go to SWO1, enter BUS2009. Click on create subtype icon there. Then enter all fields as say ZBUS2009. Now save your new BO. then implement and release it , i.e;
Edit> Change Release Status> Object type> to implemented. Again Edit> Change Release Status> Object type> to Released. Then go to events in this objects. Click on event RELEASESTEPCREATED. Then click on event parameter and create a event parameter.
Hope this solves your problem.
Don't forget to delegate ZBUS2009 with BUS2009 in SWO6.
Let me know if you have any queries.
Regards,
Raj

PR workflow for item level release (stock and non-stock)

Hello gurus,
I am not getting the agents.!!
I am creating a workflow for pr( item level release)..and using standard wf WS00000038 for this, as the standard wf contains the simple release procedure only but i have to add some custom steps to it, so i have copied this wf as custom wf .
In this wf i have to fetch the agents based on the "stock" and "non-stock items".
so i have maintained strategies and release code like:
i have maintained two strategies W1(non-stock) and W2(stock)..and release code for W1 are P1 and P2..here P1 i have given for my first level of approval and P2 for second level of approval.
The release code for W2 are P3 and P2..first level is P3 and second is P2.
so what i have did in a workflow , started with a condition step where i have given "releasecode = p1".. if yes than than it will go for getting approval from p1 , in this activity i am using standard rule 157.
The main thing is 1). i am not getting how to fetch agents using standard rule. 2)and how and where to define next level of approval for both stock and non-stock.
means by using condition step in the starting i am dividing workflow in two parts stock and non stock but how to proceed next.
i am really confused. should i use rules or write my own methods. please if anybody has gone through the same scenario than please suggest some points. i will really appreciate the help.
Kind Regards.
Himanshu

Hello HIM Joshi !
                   Include the task TS00007986 and all its branches and in a loop and loop around it for two times.When the loop goes for the first time, it should pick the first agent and during its second iteration, it should pick the second agent.
                   To accomplish so, In the same loop, but before the above task , include a background task which should populate the agent ids depending on stock and non-stock details and pass it to the the task TS00007986
                   That's all.
Regards,
S.Suresh

Release strategy - item level

hii all
can some body tel me , how and where we have to configuration for PR release strategy at item overview level.
And the same item level release strategy is posssible to configure for PO also??
If not y what is reason???
Thanks in advance
SAP-MM

hi
> how and where we have to configuration for PR release strategy at item overview level.
http://www.sapstudymaterials.com/2008/08/purchase-requisition-pr-release.html
>And the same item level release strategy is posssible to configure for PO also??
hi we cant have itemised release for PO
logically thinking PR can have multiple item and no fixed vendors and even not sure for placing order
so the realing person will decide for the item to be purchase so it has itemised relase
now in PO ,u will raise PO only when u have confirmed the purchase and the order will be for one vendor
so for ordering u have to relese the whole po,
or u can say u will create PO for all the items which have to procure so release will be for whole PO
go to spro>MM>Purchase Requisition>Release Procedure read the left side help for WITH and WITHOUT CLASSIFICATION
Edited by: Kunal Ingale on Mar 9, 2010 6:32 AM

PR item level Release WorkFlow

Hi Experts,
I have activated PR item level release WorkFlow WS00000038. My MM consultant has configured release strategy with ME51N. The Work flow works fine On releasing it sends notification work item to initator but on release Refusal it don't send notification work item to initator. Can anyone guide me how to resolve this issue.
TS00007986 SINGLERELEASE
4 Outcomes of release
1) Positive Confirmation
2) Negative Confirmation
3) Confirmation Release Cancelled
4) Purchase requisition item significantly changed
Now 1) posative confirmation is working fine.
but when we reject release then in that case also the workflow log it is going in undefined output that is significantly changed.
can anyone help me to resolve this issue.
Regards,
Hari

Hi Hari,
When you reject a PR, 2 events are getting triggered (Significantly changed and rejection_started). You check this in Transaction SWEL by rejecting PR.
The reason why output is going to Significantly changed branch is in SWEL you can see that 1st Significantly changed event is getting triggered and then Rejection_started.
Solution1: Deactivate the Significantly changed event in termination events tab.
Solution2: Create an attribute(Database object) for your business object. This attribute should be of type EBAN-BANPR. Check if BANPR = 08 and then send the rejection mail.
I hope this clears your doubt.
Please Revert back to me if you have any queries.
Regards,
Gautham Paspala

PO Release process item level control

Hi,
Please guys any way to control Release process at item level based on account assignment any configuration or user exit or bapi.
JACK

Hello Jack,
Addition to my previous response, here is the step by step process to define release procedure.
http://www.sap123.com/showthread.php?t=59
When you maintain characteristic, consider the OSS note which I mentioned in my previous thread.
Hope this helps.
Regards
Arif Mansuri

No organizational data exists on item level (error message)

Hello everybody,
I still have this error message when try to create a shopping cart : 'No organizational data exists on item level'
Following a lengthy discussion with SAP Support, SAP recommended that I remove the reference of the Purchasing Organization and Purchasing Group to the backend system (R/3).
After removing the reference I was able to complete the SC creation process, but I got an error at the PO creation process, where I am unable to release the PO since it is not linked to a backend (R/3) Purchasing Organization/Group.
I am currently using SRM 4.0 with EBP 5.0 in Extended Classic Scenario.
I need an Urgent help on this issue !!
Thanks,
Lina

Hi,
If You have own PO document type (ZCS) then don't hange it.
in SYS attrib add a local EBP system
If you don't use local categories, You don't need to add product cat. * for local system.
in my ppoma_bbp company have two purch orgs.
-for local (fields with purch org and system id is empty)
-for backend (fields with purch org is filled from backend system.)
Example:
Company (function with company code PW01\R3100)
- Purch org local (function purch. org. checked but not filled)
- Purch group local (function purch. group checked bud not filled)
- Purch org backend (function purch. org. checked with values PZ1\R3100)
- Purch group backend (function purch. group checked with values PZZ\R3100)
Regards,
Marcin Gajewski

Item Level PR Release

Similar Messages

Maybe you are looking for