Overall purchase requisition's Workflow : mechanism of release code

Hi all,
i need to implement Overall purchase requisition standard workflow ; i need to have 2 actors for process's validation, so i set release code like this :
01 - ACTOR1
02 - ACTOR2
The workflow is launched, the ACTOR1 received a work item in his workplace, whe he execute the work item, the transaction ME54N is launched. Well. But the ACTOR1 can a decision for him but also for ACTOR2, why ? the process is not good for me. If ACTOR1 has taken a decision the workflow of release code 01 is finished. An other workflow is launched for release code 02, when the ACTOR2 go to the transaction ME54N he can take a decision for his relase code but he can also cancel the previous decision of ACTOR1, it's not good for me, can you explain to me ?
Thanks for help.
Cheers.

Interesting solution using the user-exit.
I just finished modifying the delivered overall purch req approval WF. I needed to add a few fields for reporting so I created virtual attributes via delagation on BUS2105. I created approval and initiator agent attributes and email addresses. It works fine and I don't have maintain any further code other than what is in my business object which I can use again and again.
Many roads on the way to Rome

Similar Messages

Overall Purchase requisition Release strategy : Changed after Rejected

Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.

Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev

Overall Purchase Requisition

Dear Gurus
I am facing the problem of overall purchase requisition.
I have GFWRT - Total Purchase Requisition Value as a characteristic in Class ZPR_Release.
Now I am attaching this ZPR_Release with PR Release Group.
Now if I use this class in PR Group with overall Requisition Option Either in document type or in Purchase Requisition Group state, it is not working however when I remove the check of overall Req, it is working fine.
Can you please tell me what is the issue and what configuration I am missing
Regards
Sajid

Hi Sajid,
Few things to check:
1. Check the Class Characterisitc definition in CT04 and make sure the field GFWRT is mapped from the Communication Structure (table) CEBAN.
2. Check if the Overall Rel indicator is set for the PR Doc type definition in addition to the Rel Group settings
Set your Rel Strategy parameters in IMG andgo to ME54N and you should see the Release Strategy tab at the PR HEADER (Not at item detail section this time)
Let me know if this was helpful

Purchase requisition not subject to a release strategy

Hi All,
When I will release PR, appears Error: "Purchase requisition not subject to a release strategy". I've check the configuration, but it was appropriate. Can anyone help me to find the solution?
Regards,
MamaRara

hi
In our case also we have faced this problem
Usually when you are executing ME54N the system displays the latest viewed / modified PR.
Hope in your case the latest PR viewd / modified is not subjected to release. Hence it is showing the message
Go to ME22N open your PR - Press save button. Then try to open the same in ME54N.
Hope this will help you
SAS

Purchase requisition must be create with material codes only

Hi gays,
Can u solve my problem.
We are having "3 " document types to create purchase requisition.
3 types are using different depts.
I need to restrict the 1 document type with material code only they should raise the purchase requisition.
other 2 types can raise the purchase requisition with or with out material code.
Please explain how to restrict.

First check the field selection key assigned for the Document type at
Spro > MM > Purchasing > PR > Define document types..
Then Go to
Spro > MM > Purchasing > PR > Define Screen lay out, here Select the above field selection key & copy it as and make the
Description field as Display..
Again go to Spro > MM > Purchasing > PR > Define document types..
and assign the field selection key for the Document type for which you want the Description field as Display..
Then Create PR & Check

Purchase requisition's Workflow :

Hi all,
i must implement the standard workflow for purchase requisition, i use the number 20000077 - Workflow for overall release of requisition.
I would like to know if it's possible to have many responsibles for a code release in release strategy or it's not possible, for each release code there can be only one agent. I use user-exit to get responsible.
Cheers.

Hi,
You can create positions in organizational management plan for workflow (T-Code : PPOCW). Under each position, you can assign more than one user.
In SPRO, linked the release code to the position (Object Type : S) and assign the position id (from the one you created in organizational management plan) in the workflow.
In your workflow definition, assign the positions as agents to the task. After you assign the agents, you can actually see the users under each position (if you have already assigned users to positions).
When the workflow is triggered, all users for the position linked to the particular release code are sent the work item. If anyone of them have processed the work item, it will be removed from all the workflow inbox of the other users.
I hope this would help...
I just implemented the PR workflow recently but is still new to the field. Please correct me if I am wrong.
Thanks,
YL

Call purchase requisition approval workflow in abap program

Hello,
I copied the standard workflow for the approvaI of a purchase requisition WS00000038 and i tested it. I create a purchase requisition in me51n. This is triggering the event releasestepcreated which starts my workflow. Everything goes ok.
Now, i want to call this workflow in ABAP. I do not know exactly how to do it. Here is the code I tried.
data: ls_objkey type SWR_STRUCT-OBJECT_KEY,
lt_mesage type table of SWR_MESSAG,
gt_container type table of swr_cont,
gs_container type swr_cont.
gs_container-element = 'ReleaseCode'.
gs_container-value = '01'.
append gs_container to gt_container.
gs_container-element = 'requisition'.
gs_container-value = '0010000362'.
append gs_container to gt_container.
gs_container-element = 'RequisitionHeader '.
gs_container-value = '0010000362'.
append gs_container to gt_container.
ls_objkey = '0010000362'.
CALL FUNCTION 'SAP_WAPI_CREATE_EVENT'
EXPORTING
object_type = 'BUS2009'
object_key = ls_objkey
event = 'RELEASESTEPCREATED'
TABLES
input_container = gt_container
MESSAGE_LINES = lt_mesage.
As you can see i filled he RequisitionHeader, requisition and release code. I saw in the workflow that i copied, that these are import parameters. Requisition and release code are mandatory. 0010000362 is a purchase requisition that i created.
After i run the program i receive a work item in SBWP but it has the status error.
Can you help me?Perhaps anyone has done this. I think that i am not filling the correct data or something like that. Maybe you can look in the standard workflow WS00000038 and tell me what I should pass and how.
Thank you,
Efren

Hi Efren,
The Problem is, for the purchase requisition there is two key fields.
So when you pass the keyfiled to workflow it should be the concatenation of Purchanse requisition number and the item number.
You have to pass the object key as below.
ls_objkey = '00100003620010'.
Then only your business object will getting insatanciated.
Thanks,
Viji.

Purchase Requisition (PR) Workflow

Hello all,
I hope you can lend your thoughts/experience.
I have been advised that a PR workflow (without the need of a user exit) can be designed to route notification to the approver based just on the structure in organizational management (OM).
For example in OM users, John and Jane is assigned to Finance department while the approver for Finance department is Mary.
When a PR is created by John or Jane, notification will be routed to Mary based on the structure in OM.
To do the above, I have been advised that the I will still have to maintain the workflow configuration in MM but that I do not need to assign a position to the release group/release code.
The problem is that if I do not assign a position, I cannot save. So this is a dead-end.
My thoughts are that this requires implementation of user exit, M06B0001.
I hope someone can help.

Hi Richard,
I have done many of the Purchase requisition workflows before and according to the customizing it is not mandatory to have a position or the user assigned to a release strategy. It becomed mandatory only if you have the value "1" in the Workflow column of the Release codes. If you do not have a 1 in that field then the event will be raised but it will not start the standard workflow. Once you have a workflow attached to the event "ReleaseStepCreate" and within the workflow you have an activity to release the PR based on the rule which searches for the manager of the user who created the PR you have the workflow ready. Just incase you need it the rule number is 00000168 and you can view it via transaction PFAC.
Hope this helps,
Sudhi

IW31-Create Purchase Requisition automatically from PM order - Release 5.0

Dear Experts,
Currently we are working in the 4.6C Release but we are doing the migration for 5.0. In PM, in the 4.6C release when we
create a PM Order in tcode IW31 we select a component and the system shows us the screen to inform the quantity and
automatically the system shows us a screen to Create Purchase Requisition where we can fill or select some fields.
However, when we create a PM order in the 5.0 using the same tcode, the same material type, the system creates
automatically the Purchase Requisition without to show us the screen to fill or select the fieds. I´ve checked the customizing
comparing the systems but I couldn´t find something.
I was wondering If you could help me with this issue?
If my comments are not enough to understand me, please let me know...
BR
Valdevair

Dear friend,
Do check configuration node at
plantmaintenance and custonmer service - maintenance and service processing -maintenance and service orders - functions and settings for order types - define change documents,collective pur.requisitionsindicator,operation no.interval
here for your order type and plant , check whether generation of PURCGHASE REQUISITION from maintenance order settings.
there will be three options
1) never
2) from release
3) immediatly.
hipe this will help you.
Regards,
pardhu

Purchase requisition generated before service order release

Dear Experts,
We're testing the Logistics Integration Scenario for the Procurement of materials.
When we enter a spare parts item(which is configured to create a purchase requisition in ERP)
and just save the service order,
the purchase requisition is created in ERP as soon as the order is saved even though the order is not Released.
Is this a standard behavior?
We expect that the purchase requisition should not be created until the service order is released.
This symptom happens not only with purchase requisition scenario but also with the purchase order, reservation, too.
Does anyone have an information on this? Any information would be highly appreciated.
Thanks in advance for your help.
F.T.

As far as I know the standard behaviour is that the PR is created upon order save and not upon the status of the order or items changing to released.
To get around this you can set user status and use status management to prevent the PR getting created or use the BADI CRM_SRV_FIND_LOG_SC to supress creation of the PR.
Hope this helps.

While TECO of PM order, purchase requisition status reverting to In release

Dear Guru's,
I want to know the relation between Maintenance order TECo(Technical completion) to Purchase requisition status. Bcoz while we do TECO, dependant PR's which was in Release completed status reverted baclk to In release. Plz help
Guruprasad KS

Hi
In QS51-->selected set of UD >select the Code>Here remove the followup action -->QM_PM
Save
Regards
Sujit

Reg: Workflow for Overall Purchase Requisition Release

Hi Experts,
I have got a requirement in Overall or Header level PR release.
My question is,
for Header Level release,
I am using BUS2105 and what are the event I need to maintain,
so that my workflow get trigger.
Regards,
Shriraam

Hello ShriRam,
         You have to use RELEASESTEPCREATED event if release steps are configured.
          If no release steps are configured,you can use CREATED event.In such case, you have to implement a BAdI named ME_REQ_POSTED.
         In either case, you have to use the change document BANF in the transaction code SWEC.
Regards,
S.Suresh

Regarding overall purchase requisition release strategy

Hi,
For following combination PR release strategy is not working.
1.Total value of requisition
2.Purchasing Organization
3.Name of Requisitioner/Requeste
But when we take any one of them it is working. But when I tried to put together, these field system is not picking any release strategy.
What would be the reason? is there any inter connection between these fields?
Regards,

Dear Aj,
Chek is theare any other release strategy in the syestem wth mentioned chraterstic,
also chek all chraterstic are ticked in the release strategy?
Some time syestem is not able to find the unique release strategy,
Please let me know

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

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 purchase requisition's Workflow : mechanism of release code

Similar Messages

Maybe you are looking for