Skip to Content
author's profile photo Former Member
0
Former Member

Logical problem in Purchase Order Release (urgent)

Posted on Dec 03, 2007 at 08:49 AM 13 Views

Hai Guys ,

I am defining a workflow for PO release and i did the release procedure for 3 levels of approve. My workflow running successfully. the workitem send to the appropriate users and they release the workitem as very well. I used the standard workflow. my logic was

Release Code = Approver

01 = user1

02 = user2

03 = user3

when i create the PO the workitem was send to the user1 for release. he execute the workitem it will go to the release screen and he is able to release. after releasing and before saving user1 is able to release the user2 and user3 releases also. that was the logical mistake happening. the user1 should not allow to release the user2 and user3 releases. how it can be done?

Thanks in Advance.

Regards,

R.Sathis Kumar.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 01:12 PM
    1

    HI Satish,

    Double click on work item then goto task and go to ->Terminating events define the events as I said in the earlier reply.

    Regards,

    Gopi.

    Reward points if helpfull.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 01:16 PM
    1

    I think you can take help from Standar Workflow For Purchase Order WS20000075. The Release step uses this a method that has the following terminating event. I think you can restrict user 1 from releasing release code o User 2 by doing the release in background in other words not offering the user with ME29n screen.

    Thanks

    Arghadip

    Add a comment
    10|10000 characters needed characters exceeded

    Comment on This Answer
  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 04:26 AM
    1

    The problem lies with Release Procedure Configuration and not in workflow.

    What you need to do is to define Release Prerequisite for each release strategy. Or ask your functional guy to do that.

    And it will work even without workflow scenario.

    Check it pl.

    Dinesh

    Add a comment
    10|10000 characters needed characters exceeded

    Comment on This Answer
  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 11:25 AM
    0

    set the follwoing events as the outcome events for your workitem.

    when user change the PO and SAVE then only the following events are going to trigger.

    Purchase Order Rejected----REJECTION_START

    Purchase Order Released---RELEASED

    Purchase Order Changed Significantly---SIGNIFICANTLYCHANGED

    Reagards

    Gopi .

    Reward points if helpfull.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 04:32 AM
    0

    Also check the approver's authorisations. If he has all - 01,02,03 authorizations, system will allow him to approve in all these cases.

    What I am not sure here is whether system will force him to save after 01 release and then go to 02 OR

    do all 01,02,03 at once and then save.

    You need to test this and see.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member
      Dec 04, 2007 at 05:41 AM

      Hai Ravi ,

      Could you please tell where i can see this M_EINK_FRG object. I gave the Link between the user and the release code and release group in the release procedure under the workflow tab. whether you mean that place?

      Regards,

      R. Sathis Kumar.

    Comment on This Answer

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.