Header Level Release Requisition

Hi,
The purchase requisition WS00000038 is for item wise release. But they need header level release. Is there any standard workflow ?? I dont find any, so i created custom workflow and everything is ok. But when i create the PR, the workitem goes to everyone. I've marked General Task. For standard wf, it works properly, but not for my workflow. It is not picking the agent from Release Strategy settings. Do we need to give the custom wf no anywhere to pick the correct agent ??

What you have done in Release Strategies, can you explain.?
What is the Path? Where you have mentioned Agents in RS for Requisition?
http://help.sap.com/saphelp_erp2005vp/helpdata/en/1d/ea9d9c7aca11d194b70000e82dec10/frameset.htm
Make in SPRO for Purchase Requisition:
SPRO-> MM>Purchasing->Purchase Requisition-->Release procedure->Procedure with classification-> set up procedure with classification-> double click on Release strategies
and aslo
double click on Workflow
http://help.sap.com/saphelp_erp2005vp/helpdata/en/1d/ea9d9c7aca11d194b70000e82dec10/frameset.htm
Edited by: Prabhakar Dharmala on Feb 5, 2008 1:22 PM

Similar Messages

PR (Header level) release strategy not working

Hi all,
I have configured release procedure for PR - Header level release(i.e. With classification). My scenario is as below,
If PR value is <=1000 INR and Plant 1000 Two persons will release the PR. I.e., Release codes A1 and A2.
If PR value is >1000 INR and Plant 1000 Three persons will release the PR. I.e., Release codes A1,A2 and A3.
i have created Two charac(for Plant and Value), one class(Assigned the characs to it), one group, 3 release codes, and 2 Release stratergies (i.e.S1 and S2). All the settings are fine. But when I create PR, system takes only the first Release stratergy by default. That is irrespective of the valuation price in PR system by default takes S1 release stratergy only. Even for higher value PR system is not taking S2 stratergy. I have given correct values in the classification field. Why does this happen? Release procedure without classification is not configured.
Note: I have even ticked overall release for document type NB
Any inputs? Thanks in advance.
Regards,
Ayyappan.

Hi all,
One thing is clear now. System is not all considering the value characteristics. Its only considering Plant character(WERKS). Thats why by default its taking first release stratergy since both have plant value as 1000 in classification view.
Just now i checked by using sinlge character. For release class with plant as character the release procedure is working fine but for class with value as character release is not at all getting hit.
Note:
1.My company code currency is EUR. My characteristic currency is USD. While i create PR in valuation price system by default selects EUR. I am manually changing it to USD. Is that correct?
2. Still my new posting period is not yet open.
Is there the problem is somethig related to above?
Regards,
Ayyappan

PR release refused for 7 lines out of 8 line item for header level released

Hi Gurus,
please help me how to resolve this issue.
i have purchase requestion with 8 line items,out of 8 line items line 5 gets relesed and other lines relese refuded mode.
i have checked the complete procedure,authorisations and tried through ME54N and ME55 also.
please help me , thanks in advavnce.
Regards,
Babu

hi
please check the line items whether its blocked or deleted or value and quantity fields are updated.

Why release strategies for PO at header level only

We have release strategy for Purchase Requisitions and Purchasing documents like PO, Contract and SA.
In case of PREQ we have a choose for either item level release or header level release, whereas in case of PO, Contract and SA only header level release is possible.
My question is why SAP has provided only the header level Release Strategy for PO, Contract and SA? I wan to know the reason and logic behind this.

Hi,
For PR's, there is no header level data. Becuause vendor number is optional since it is internal document from the user dep. to pur org. That's why, vendor number fields is at item level in the source of supply screen. But this is optional field.
That's why, you can release PR line items one by one or all at a time.
If you are releasing all line items at a time, need header level release.
If you release line item by line item, need item level release.
But in the case PO/Contract/SA, these are final reference documents and sending to the vendor as external documents.
That's vendor number is at header level field and line item in the PO are related to the single vendor.
That's why u cann't release line item by item, i.e., item level release.
You can relase all the items in the PO or u can reject entire PO, not a single line item.
That's why, only header level release is possible for the PO/Contract/SA.
Regards
KRK

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

Purchase Requisition Release at Header Level

Hi MM experts,
We are on ERP6. Can we activate purchase requisition release at header level (ie overall requisition dollar level - sum total of all requisition line items) just for one business (company code) without affecting rest of client which uses release strategy at requisition line item level?
Is it possible to share the same document type, e.g. NB that is used by other business?
Many thanks.
Thomas

With the release procedure with out classification , it is possible to release the PR at header level based on the value of the PR . In determination of release strategy , you can maintain the value , currency and release stratergy .
But to restrict this to a particular comany code , you may use the exit M06B0002 where in you can write the logic .
-Hari.

Purchase Requisition release WF with multi-level release strategy

Since it has been "a while" from my WF course and i lack experience with WF's (this is supposed to be the 1st one i implement, finally)...
The problem I'm facing is really in planning phase of sketching up how my scenario should look like. I have to create couple of WFs for a project that involve purchase requisitions and purchase orders.
The problem i'm trying to solve is logic concerning release strategy steps for this documents. They are set-up and well-deffined in customizing, but there are couple ofrelease steps for particular strategy.
Scenario:
1. someone creates a purchase requisition (event for BUS2009 is triggered, and workitem appears for release of Purch. Req. in their workplace)
2. initiator of workflow executes his workitem and selects one of the release codes (this workitem is now complete) - i'd like for new workitem to appear in supervisors inbox automatically...
3. now i need supervisor of initiator to release same purch. requisition with another release code (how to do it?)
4. supervisor of supervisor (mentioned in step 3.) needs has the authorisation for final release with final release code.
5. now the initiator from step 1. has to be notified that requisition has been released by overall head of department.
Org structure i created looks like this:
ORG. UNIT. Level 0 for Purch. Req. (with Head CEO of Plant as final approver)
ORG.Unit. Level 1 for Purch. Req. (with Head of level 1)
ORG.Unit. Level 2 for Purch. Req. (with Head of level 2 and Clerks 2a,b,c)
So these guys (Clerk) 2a,b,c create Purch.Req. They or their Head of level 2 releases their requisitions with his release code Z1,
Head of level 1 should recieve workitem in his inbox to be able to release it with his release code Z2.
Director of the plant should recieve workitem for final release Z3, after Head 2 did his release with Z2, and then guys 2a,b,c should get notifications that their PR's are released.
I managed to get the SAP's standard for Purch. Req. Release working but it's just not enough...
Please advise me, guide me, if u have any idea, how could this be done, because i'm loosing a lot of time here, just searching and not seeing it. The problem is that we don't have any WF experienced guys that could help, so i'm kinda' stuck.
Could standard be used here at all?
Is it possible that the same task (for example. TS00007986 - Release requisition) appears more than once in the sam WF with different agent asignments?
I dont have an idea how this scenario should be built in WF builder.
BTW, i'll have 12-15 plants, does that mean 15 different WFs and Org Units?
Help WF gurus.
Thank you in advance,
BaX

Its' a while since I last time worked with PRs, but I'll give a try...
This part is a bit confusing:
>1. someone creates a purchase requisition (event for BUS2009 is triggered, and >workitem appears for release of Purch. Req. in their workplace)
>2. initiator of workflow executes his workitem and selects one of the release >codes (this workitem is now complete) - i'd like for new workitem to appear in >supervisors inbox automatically...
>3. now i need supervisor of initiator to release same purch. requisition with >another release code (how to do it?)
Why do you want that the initiator (the creator of the PR) needs to go the business workplace and release the PR (or select the release code). Isn't this an unncessary step? Shouldn't it worked like this:
1. Someone creates a PR
2. PR "gets" a release code automatically with some logic defined in customization
3. PR release work item apears in the supervisor's workplace
4. Initiator gets the mail
If I recall correctly, the standard solution works like this, or has quite similar approach.
Whatever way you decide to build your workflow, you won't most probably need a workflow for each plant, but you'll need several org units. But this all really depens on how you decide to do it...

Release of PO at header level

why is that we release PR at "ITEM" leval and PO at "HEADER" level ???
is that because PO is been created with reference to a specific vendor so we do it in the header level
in PR we issue it for all the materials so it is done at item level
is tht the right explanation or do we have any ?? please help
regards
Pavan

Hi,
PR is an internal document. Suppose if you have 3 line items in a PR you will release 1 line item and PO can be created for the particular line item (PO with reference to PR).
Where in PO is an external document and has to be released at Header level.
Regards,
Nagaraja Achar

Is it advisable to release PR at header level

Hi SAP Experts,
Is it advisable to release PR at header level?
If yes, then what can be the drawback.
And can you advise me any setting with which cancellation of PR & PO can be avoidable.
Thanks & Regards,
Anisha Sinha

Hi,
If the material is Directs then it is not an issue to have the release strategy for PR at header level.. just being a regular material for the procurement...
But, in case of Indirects procurement... it is not advisable to have the relase strategy at header level... reason being you need to check the individual items and then only release them...
Coming to your second question, you can have release indiactor "5" with "1" in changeable field... this would not allow you to make any change PR/PO once it is relased. But, it is not really advisable to use this kind of strategy...
Hrishi

Additional Data in Header Level for ME51N / ME52N / ME53N

Dear Gurus,
I have one requirement related to apply enhancement for additional fields in purchase requisition header level.
After searching a lot , I dint found any solution for this.
Does anybody have any solution for this.
Regards,
Shibashis.

I need to add on Tabstrip "Account assignment" for fields
CO Area and Cost Center text field description ( right side ) for each one.
How can I do this? Thanks in advance.

To be able to report by business area at a header level

Business area reporting at a header level in Procurement/AP Subject Areas
At present client is doing a large number of manual lookups in Excel to add Business area detail to certain OBI procurement reports. Reasons for why we are having to do this includes that the report is written at a header level but the business area detail is stored at a distribution level or the document has no distribution lines.
What client would therefore like is for us to devise solutions that would allow us to include the business area detail. Possible solutions that I can think of include doing a join between the employee name, preparer name and requestor name to the HR business area detail, and the way that the ‘Procurement and Spend - Employee Spend’ joins the employee name and approver name to the business area fields maybe something that you can review as a solution.
I am hoping that you can come up with a number of solutions which we can then explore in further detail.
The key subject area that we would like this business area detail to be available in is the ‘Financials - AP Transactions’ area but if would certainly be beneficial to have in the ‘Procurement and Spend - Purchase Orders’ and ‘Procurement and Spend - Purchase Requisitions’ subject areas as well if it is feasible.
Can any plz.. guide the possible soultions we can do with this CR
Edited by: user13050518 on May 11, 2010 7:40 AM

Bonjour,
Je suppose vu votre prénom que vous parlez français lol bien que l'anglais ne me pose pas de problème.
En fait, il s'agit de plusieurs factures (avec différentes business area) pour un même fournisseur.
Au moment de la F110, le système comptabilise le paiement via une seule pièce mais avec plusieurs postes (un par business area) et la contrepartie le compte banque.
La case n'est pas cochée pour le champ T001-XGSBE donc je ne pense pqs que le problème provienne de là.
Cdlt

Migo is not showing the excise tab - header level and item level

Hi,
i have created one PO with excise and i have created MIGO with only capture excise invoice, in MIGO before saving the document system is showing the excise basic, cess and higher education cess in excise tab, header level as well as item level. After saving the document, if i go to dispaly view of the MIGO document system is not showing the header level as well as item level excise amount. The tab itself is not appearing. Can any one help me on this.

Hi,
There are two kinds of statuses, system status and user status.
You can only influence System status if you execute a business transaction that changes the system status.there
are four system statuses open, In process,Released and Completed.
User status can be created as additional information to the system status in any numbers.But for this you
need to define a status profile which would further be assigned to transaction type(header status) and
item categories(item status).
The header status is independent of the item status. One exception is the status Completed.
If all items have the status Completed, the header status is also set to Completed.
For defining a status profile you need to go to
SPRO>Customer Relationship Management>Transactions>Basic settings>Status Management.
Hope this helps.
Regards
Sidd

How to close a PO at the header level

Is it possible to close a PO at the header level or a way to deactivate the PO so that no new items can be added? Thanks in advance for any suggestions.

> Is it possible to close a PO at the header level
Po can be closed at Item level and not Header level. You can set Deletion Indicator and further can be archived thru SARA MM_EKKO
or a way to deactivate the PO so that no new items can be added?
You can activate Release strategy and Choose a Proper Release indicatory so that no new changes to be carried out.
Else go for User Exits

Document Parking Workflow Responsible Agent for Two level release

Respected Members,
I have done all the configuration for document parking workflow.
i had said if the amount is greater than one lakh it should go two-level amount release.
My organisation hierarchy includes two positions,
SUB_HEAD with user xyz
HEAD with user ABC.
i have assigned the position HEAD with two level release workflow in spro.
When i am creating a parking document above one lakh, the work items are generating and it is coming
in the inbox for the both users ie xyz and abc.
MY requirement is that when xyz user execute the work item then only it should go to abc user inbox.
it should not go to abc inbox as soon as document is created.
Please give me the answer as soon as possible,
Thanks a lot.
Manish

Hi,
Have you checked out SAP help file for this workflow?
[http://help.sap.com/erp2005_ehp_04/helpdata/EN/0e/0e3b00b84111d3b5b2006094192bbb/frameset.htm]
Regards,
Lim...

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

Header Level Release Requisition

Similar Messages

Maybe you are looking for