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

procedure for workflow

hi

pls can any one explain step by step procedure for sales order, purchase order workflow design. Thax heaps.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 12, 2007 at 01:54 PM

    Purchase Order and Sales Order Workflow

    Purchase Order workflow ( Transaction : ME23N) determines the approval path for the buying organization . It first goes to the buyer, buyer's manager & thereafter based on the cost center & the associated amount, it goes for approval through the Cost Center organization .

    i.e,

    Buyer ( Requestor in the procurement deptt. of the buying organization)

    |

    |

    v

    Procurement Manager

    |

    |

    v

    Cost Center org. approval ( based on amount & Sign.Authority level)

    Regarding , Sales Order( Transaction: VA01); it is created in the Sales Org of the company & basically governs the pricing structure of the order .The routing of an SO is

    Sales Org. ( based on the cost center of the sold item)

    |

    |

    v

    Distribution Channel

    |

    |

    v

    Division

    |

    |

    v

    Reg. Sales office

    |

    |

    v

    Sales Group

    |

    |

    v

    Sales Person

    Regards

    Vasu

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 12, 2007 at 01:55 PM

    Hi,

    The following steps for PO.

    Steps in Workflow

    <b>1. Creation of Attachment by the PO creator</b>

    As the first step in release of PO, a Work Item will be sent to the user who created the PO. The user has to attach documents for the reference of the approvers of different release codes and then execute the Workitem. However, attachment of document is not mandatory. The user can simply execute the workitem if he/she thinks a reference document is not required for a Purchase Order.

    This step is required only for workflow of first level release code.

    <b>2. Approval of Release by the Responsibility (Silent Release)</b>

    Each responsibility associated with a particular Release Code will receive a Workitem for PO Release with the particular release code. Responsible person has the choice to either approve it or reject release of PO.

    <b>3. Release of PO in Background</b>

    When the user chooses to release the PO (in Step 2), the PO will be released in background by the Workflow.

    <b>4. Reset Release</b>

    A Background Step resets the Release of PO for the respective Release Code when the user (in step 2) rejects the release of PO.

    <b>5. Email on the status of Release to the Responsibility</b>

    Email will be sent to the agent who executed Silent Release with the status of the release.

    <b>6. Monitoring for External Release</b>

    A wait step will be monitoring for external release of PO with the Release Code of the Workflow. Receipt of the event will terminate the Workflow.

    <b>7. Monitoring for Change in Release Strategy</b>

    A wait step will be monitoring for Significant Change in Release Strategy. Receipt of the event will terminate the Workflow.

    Thanks

    Srinu

    Add a comment
    10|10000 characters needed characters exceeded

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.