Purchase requisition workflow - reset release via BSP and BAPI

Hello,
We have a small workflow to release purchase requisition.
A mail is send to the approver. The approver opens an BSP application to release or refuse the PR.
The approval works well.
The rejection doesn't work well.
I use the BAPI_REQUISITION_RESET_REL_GEN to reset the first release of the PR (00 release key)
We have 00, 01, 02 as release key, and all the release have to pass to release completely the PR.
00 is the requester level.
My problem is :
for example I am the 01 level. I received the mail from 00 level, I refuse the PR via the BSP. In ME53N, the current release key is now 00 but when I look at the workflow, the following agent (corresponding to 02 release key) is determined. Normally nothing has to happen.
Someone has an idea to stop the workflow ?
thanks
Véronique

Hi Martin,
When I checked the contain of container in the workflow (in the log), I saw that the release key is 02.
I don't know why but the WF received the event RELEASESTEPCREATED instead of normaly it is finished.
When I reset the release via ME54N, the WF ends correctly and no new event is received.
How can't I see why the event is started in the BAPI.
In fact it is very strange, if I used the BAPI alone, all works, no new event is started.
But if I used the BAPI in my BSP, a new event is started.
Thanks
Véronique

Similar Messages

  • Purchase Requisition workflow escalation

    Hi All,
    I need help with purchase requisition workflow escalation. The workflow for the requisition escalate to the next level if not approved within 24 hours.So i dont want the workflow to escalate on weekend.
    I want to know what can i do.
    Tx Rosi

    Hi
    For your Requirment :
    "the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release."
    Please follow the below steps.in copy of  WS20000077.
    1.For taskTS20000159:Overall release of requisition , go to
    Latest END tab:  put ACtion as :Modeled ,  Refer.date/time:Workitem creation , below time : choses: DAY,  and on left add 2.
    Outcome :Deadline Montoring.
    2.Then come to OUTcomes tab of the same task:  see  there are 3 lines 1.Step executed, 2.Latest end:Deadline Montoring, 3.Processing obsolete:Processing obsolete ,, all are ACTIVE or not , if not, Activate .then  all should be Green.
    4.next in the OUtcome :Deadline Montoring , use a process control step. to Set missed workitem to obsolete,  in Function: chose : set Work item   to Obsolute. and Workflow Step : chose then step no for the above task(TS20000159:Overall release of requisition).
    5.In "Processing obsolete" path, again call the same task TS20000159. in different activity . and see to the agent assignment.
    I think this will slove your problem.
    How it works:
    1st the PR is send in a WI to the perticular agent by the 1st activity . if the agent do not execute for 2 days. then that WI will set to obsolute . and process flow to" Processing obsolete" path, then agian PR is send to the next agent using the same task but activity created in  step 5.
    thanks
    Kakoli.

  • Purchase Requisition Cannot be released

    Dear SAP Gurus,
    While doing ME54N to release PR. System showing the Error 'Purchase requisition cannot be released'.
    PR created on 23.04.2009 then PO Created against it , again PR was dereleased now again when going for release of PR system is providing the error as mentioned above.
    Message no. MEPO822
    << Moderator message - Everyone's problem is important >>
    Thanks and Regards.
    Anil Thakur
    Edited by: Rob Burbank on Nov 10, 2010 3:52 PM

    Hello Anil
    During this period any release stratergies changed for pr ?  after de release the pr just modified small value and make it same again this is nothing but refresh.
    then check the pr release
    Laxman

  • Purchase Requisition Workflow - Organizational Plan required?

    Hi,
    We are implementing purchase requisition workflow.
    Based on what I have read, it says that the workflow table (table V_T16FW) and SAP HR-PA-OM (organizational plan) must be set up to support the solution. 
    Question:  If we are routing the workflow to a UserID, i.e. Object Type = US (and not an HR data object like Position or Job), do we require an Organizational Plan to be also set up?
    Cheers,

    Thanks so much for your response.
    What about assigning tasks to users, etc. that is usually done in org plan, correct?  If object type US is only used, I assume this is not required either?
    Also, what is the benefit of using Object type = 'S', i.e. position?  At my company, most of the time, when people leave, the position is deleted and a new one is created (there are a couple reasons for this), which means, even if we did use positions, the workflow table would still need to be maintained everytime a person leaves/joins the company (I understand if only the user to position mapping changes, then it makes sense to use positions, and therefore the workflow table stays constant, and only the user to position mapping changes).  Are there any other benefits of using S instead of US?
    Also, is it possible to NOT use a workflow table, and ONLY define an organizational plan?  I was thinking to activate user exit M06B0001, and perhaps ONLY maintain an org plan, and use this to determine approver, rather than maintaining both MM workflow table and SAP Organizational Plan (HR-PA-OM).  Bottom line, we want to maintain as little data as possible.
    Your thoughts?
    Cheers

  • Link a MRP Purchase Requisition to a  Purchase Requisition Workflow

    Hello Gurus,
    I have a Purchase Requisition Workflow  already created.
    I want to create a MRP purchase requisition that start my workflow.
    How can I do that?
    Thanks in advance,

    Hello Charlie.
    Our release strategy hasn't classification. When we I create a MRP purchase requesition, the release stratagy is already assigned to that. however the worklow is not started.
    thanks

  • Purchase Requisition Creation From Release

    Dear PM Gurus,
    For Manual material availability Check to work before release, the Purchase Requisition check is to be set to Immediately in SPRO-> Define Change Docs and Collective PR or Activating Pr from Now On from Maintenance Order. The issue is that I want to restrict the creation of Purchase Requisition to Release of Maintenance Order but what is happening is upon saving the Maintenance Order, the PRs for all non stock materials are created and I also want the manual availability check to work before release.
    Simplifying above details:
    I want Manual material availability check to work and PR generation from release both in my Maintenance Order to work..
    Regards..

    Hi DP Singh,
    I had seen the configuration settings that you are telling me but you see the Problem is:
    If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/PReq Indicator as Immediately, then the Manual Material Availability Check would work accurately but upon saving the Order, System would generate the Purchase Requisition.
    and If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/Preq Indicator as From Release, then the Manual Material Availability Check would not work as no material is as such MRP relevant till the time of releasing the Order but the Purchase Requisition would be created only when the Order is released.
    Now What I want is both the Manual Availability Check to work and Purchase Requisition Creation From Release, but this is not possible according to the Standard SAP System. A workaround could be that I configure the automatic material availability upon release and configure the Res/Preq indicator as From Release, that way the material availability would be checked when the order is released and Purchase Requisitions would also be created from Release but still the Manual Availability Check would not work.
    The Ideal Solution should have been configuring the Res/Purchase Requisition Indicator for all Non Stock Materials to be From Release and the Res/ Purchase Requisition Indicator for all Stock Materials to be Immediately. This way your manual availability Check would work for all Stock Materials and Purchase Requisition for all Non Stock materials would only be created upon Release. But this  But still this is an ideal solution not the actual solution for standard SAP does not give you the flexibility to do such a setting in customizing or using Enhancement.
    The Work Around Solution given by SAP is as follows: The system provides the following workaround:
    After you change the indicator for materials planning-relevance to
    "immediately" you can execute the availability check as required. You must
    not save the order or network.
    Regards,
    Muhammad  Usman Kahoot
    Edited by: Usman Kahoot on May 27, 2010 1:32 PM

  • Deadline monitoring/Escalation - Purchase Requisition Workflow WS20000077

    Dear Friends,
    I have read some stuff on SDN but still couldnt figure out the soultion.
    Its a common problem. We have set a release strategy in Purchase Requisition and are using std workflow WS20000077.
    Now the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release.
    I have set the deadline monitoring using the workflow wizard for model deadline monitoring. With this, The work item gets deleted from the approvers inbox. Next in the obsolete path I have set a process control which specifies the worklow step as the step in which deadline monitoring was specified.
    When I check in SWI1, the work item is set as obsolete but it doesnt go to the next approver for approval.
    Your replies will be highly apprecialted.
    Thanks & Regards,
    Fawaz

    Hi
    For your Requirment :
    "the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release."
    Please follow the below steps.in copy of  WS20000077.
    1.For taskTS20000159:Overall release of requisition , go to
    Latest END tab:  put ACtion as :Modeled ,  Refer.date/time:Workitem creation , below time : choses: DAY,  and on left add 2.
    Outcome :Deadline Montoring.
    2.Then come to OUTcomes tab of the same task:  see  there are 3 lines 1.Step executed, 2.Latest end:Deadline Montoring, 3.Processing obsolete:Processing obsolete ,, all are ACTIVE or not , if not, Activate .then  all should be Green.
    4.next in the OUtcome :Deadline Montoring , use a process control step. to Set missed workitem to obsolete,  in Function: chose : set Work item   to Obsolute. and Workflow Step : chose then step no for the above task(TS20000159:Overall release of requisition).
    5.In "Processing obsolete" path, again call the same task TS20000159. in different activity . and see to the agent assignment.
    I think this will slove your problem.
    How it works:
    1st the PR is send in a WI to the perticular agent by the 1st activity . if the agent do not execute for 2 days. then that WI will set to obsolute . and process flow to" Processing obsolete" path, then agian PR is send to the next agent using the same task but activity created in  step 5.
    thanks
    Kakoli.

  • Purchase requisition date in SNP planning book and product view not in sync

    Hello Experts,
    We have an issue with display of purchase requisition date in SNP planning book.
    We are manually entering the PR's for a perticular week from Monday - Sunday(01.09.2014- 07.09.2014), when the last PR is entered on 07.09.2014, it does not appear on the same day in planning book(cell becomes empty) and moves to 06.09.2014, thus quantity on 06.09.2014 is the summation of the quantities present on 06th and 07th.
    The PR dates are appearing correct when we click on display details in planning book and they are correct in product view, MD04 as well.
    Additionally, this is the same date on which daylight saving time comes  into effect.
    Kindly advise if anyone has faced similar situation earlier.
    Many thanks,
    Aditi

    Hi Aditi,
    Check the time zone that you have in your location in ECC and APO.
    Also note it is recommended that you maintain the same system time zone in APO and in ECC. (check tcode STZAC in both systems).
    Different time zones should generate this kind of inconsistencies.
    Kind Regards,
    Mariano

  • Very urgent purchase requisition workflow

    Hi,
      I have been asked to develop a pr workflow,here i have to capture the tracking number along with the pr no and based on the trancking number it should go to the respective department person to release it.How can I do it.
    Regards,
    Latha prabhu.

    Hi Latha,
    You could do you agent assignment using Rules (Called Role Resolution in 4.6C and below). You can create a Rule using Txn PFAC. Create a rule of category F (Agent Determination: Function to be executed). You will have to develop a function module which must adhere to a predefined interface. You can either extend the PR object to have Tracking Number as an attribute and pass it on to the FM or pass the PR to the FM and determine the tracking number in the FM. You can then determine the User or Org Object responsible. Please read the documentation and see some of the standard rules available in the system.
    Cheers,
    Ramki Maley.

  • Regarding Purchase Requisition Workflow.

    Hi Friends,
    In PR release ,if i have multiple level of approvers, more than 1 than do we need to handle this seperately or the SAP std. workflow will take care by itself. In the activity 'Overall release of requisition' there is a task which uses 'singlerelease' method of business object BUS2105. Does this method require any changes or only maintaining the release strategy congiguration will help.
    PLS help me on this. If question is not clear than pls tell me .

    The question wasn't so clear.
    Regards,

  • Purchase requisition - Workflow

    Hi
    I have one issue related to PR Release,Some requisitions are hanging in the users workspace and few of them are related to released requisitions and few of them are set as a deletion flag from IW32 transaction but these PRs are still exists in users Q. Can any one suggest me how can we delete these requisitions from users Q?
    Your help is appreciated
    Regards,
    Nag.

    Hi Nag,
    Go to the t-code SWI5. Enter "US" for Type and key in the user's ID number. Then select "Work to Be Completed" and then remove the date. Hit Execute.
    You should be able to see a list of workitem pending release, including the workitem that may be stucked for this user. Double click on the workitem to confirm that it is the PR number.
    After reviewing that you got the workitem you want, you may proceed to delete from their inbox.
    Hope this helps.
    Rgds.

  • Purchase Requisition workflow issue

    Hello  friends,
    i have created a workflow for PR release by copying standard  WS20000077  .
    the WORKFLOW trigeers properly  ,
    but when it created it goes to all users of  applied release strategy  , before release of previous one 
    what may be problem  .
    kindly suggest me  .
    Thanks & Regards
    Digvijay Rai

    Hi,
    but when it created it goes to all users of applied release strategy ,
    before release of previous one
    You  mean to say in the 1srt level Approval it goes to all People right. How you are determining the Agent, check that.
    For PR Workflow See the Following,
    WS20000077 this std. Workflow for the PR Release this has multiple levels of approvals, Depends on the no. of approvals it will flow.
    The approver can picked using the User Exit M06B0001 (EXIT_SAPLEBNF_001), here you have to write a logic to pick the Approver.
    The approval workitem comes to SAP Inbox, once the approver click the workitem it will open the Transaction, there the user can approve.
    To see the status of the Workflow, Go to ME53N, in the top left a button, Service Object, click on that, a drop down appear in Workflow > Workflow Overview, you can see the status here.
    Regards,
    Surjith

  • Since doing iOS 7 update I can't send or receive iMessages and when I try to activate it just keeps saying check network settings. I have done a network reset both via wifi and 3G yet still no joy. Frustrated please help

    Have had the problem since iOS 7

    iPads only support iMessage. You cannot send SMS with any of the native iOS functionality on it. There may be some apps in the app store that will, and certainly several messaging platforms (but read the descriptions carefully).

  • Purchase requisition report via Release indicator

    Dear All,
        I would like to know if there is any standard report in purchasing that has the functionality to display purchase requisitions by their release indicator. 
    Thanks

    Hi,
    You can use table EBAN wth FRGKZ Field for Release Indicator.
    You can t.code:ME5A and click Dynamic Selection and select "Subject to Release" in Purchase Requistion  in Application Toolbar and execute to get the report for your PR's.
    1.Enter "YES", It will give report for the PR's which are not Released.
    2.Enter "NO" ,it wil give report of the PR's which are Released
    Regards,
    Biju K

  • 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

Maybe you are looking for