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

Similar Messages

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

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

Item wise release strategy

Hi Experts,
I made item wise release strategy and used material group in class ,however when add this CEBAN-MATKL it doesn't find release strategy when remove this release strategy is working is it need to add something into material master data ?Need your advice
Thanks in advance

create release class, FRG_EBAN is available in system
create release characterisitics .. here what ever name you give, you have to make it 'reference to table CEBAN' and corresponding CEBAN field , in additional data
create a release group and attach the release class created
create release codes, and while doing it you have to specify for which release group it is valid
create release indicator , here specify the changeability
create release strategy with release codes, release prerequisites, release statuses etc
if you are transporting this, in the operational client, using CL24N assign char values for each characterisitcs of release strategy. ( you need not assign char value when that characterisitic is not present int he document e.g.if account assignment is a char, then for release strategy for document without account assignment should not have any value for that char)
if you ensure this much your release strategy should work ok

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

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

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 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...

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

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

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

Old PR release strategy - release completed status change

Dear Gurus,
We have impletemented Item level release strategy for PR.
There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
Please advice
Regards
RS

Hi,
Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
Check the value of Changeability of purchasing document during/after release ( 1 - 6).
Choose the appropriate value based on your req.
Regards,
Udayasankar Rajagopalan
Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM

Precautions to be taken before going for new PR Release strategy

Dear all,
We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
Need your advice on
1)If we go for new release strategy as off with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
3)Any other which I missed out, please suggest me
Thanks
RS

Hi,
It is better to release all existing PRs using your current procedure without classificaton and clean up.
If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
REgards
Ram
Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

Release strategy tables

Please tell me the tables used for release strategy of PR, PO, service PR, sercice PO, RFQ, contract, and delivery schedules.
Is there a method of finding out the table by some methodology. It is not possible to remember all the tables.
In case of PR item level release is required. Give some guidelines as to how to activate item level guidlines. it is possible both with and without classification.
Regards

HI,
Release strategy tables
Release strategy without classification
T161I as described above.
T161E Release code and Description
T161S Release indicator
T161G Assignment to release indicator
T161F Prerequisites
Release strategy with classification
T16FG, T16FS as described above.
T16FH description of the release group
T16FT description of the release strategy
T16FC Release code
T16FD Description of the release code
T16FV Prerequisites and actions
T16FK Assignment to release indicator
T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator
Other tables are
EKBE History per Purchasing Document
EKBZ History per Purchasing Document: Delivery Costs
EKKN Account Assignment in Purchasing Document
EKPA Partner Roles in Purchasing
EKPB "Material Provided" Item in Purchasing Document
EKPV Shipping Data For Stock Transfer of Purchasing Document Item
EKRS ERS Procedure: Goods (Merchandise) Movements to be Invoiced
EKUB Index for Stock Transport Orders for Material
EBAN table has fields for release status and indicator.
To See the tables
goto Transaction SE11, in the field Table click F4, Click on Information system
In the applciation Compnnets enter the following & execute
MM* Materials Management
MM-CBP* Consumption-Based Planning
MM-PUR* Purchasing
MM-SRV* External Services
MM-IM* Inventory Management
MM-IV* Invoice Verification
MM-IS* Information System
MM-EDI* Electronic Data Inter
MM-FT* Foreign trade
OR
goto SE16 Click F4, You have two options Information system & Sap Applications.
Click on SAP Applications & selec the application you wnat to see, for E.g Purchasing you can click on materials managemnt, Purchasing if you drill down you will see the list of tables....
http://help.sap.com/saphelp_47x200/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Check release stratergy with and w/o classification
Thanks & Regards,
Kiran

Overall release of PR in Release Strategy

I have created item-wise release of PR using with Classification of Rel Str.
But when I am creating overall release of PR I am not getting the tab.
I made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR.
Pl guide
regards
VS

Hi VS
Am confused. You wrote 'Have created item-wise release strategy' and also asking 'Overall release'.
If you have "made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR", then you have configured Overall release.
If PR does not get release strategy tab at header, it could be due to incomplete release strategies. No release strategy might have been triggered for your PR data. Do you see release strategy tab at item level ?
Best regards
Ramki

Processor of PR item level release strategy

Similar Messages

Maybe you are looking for