Purchase Order Approval:Organizational Unit
gs ko
gs.america at yahoo.com
Thu Feb 27 00:30:52 EST 2014
That's good approach. If you are usning custom workflow, you could create customer rule as well.
Thanks,
Gowrishankar.
--------------------------------------------
On Wed, 2/26/14, michael.mcley at daimler.com <michael.mcley at daimler.com> wrote:
Subject: RE: Purchase Order Approval:Organizational Unit
To: sap-wug at mit.edu
Date: Wednesday, February 26, 2014, 10:57 AM
Swathi,
If you are using the "standard" SAP PO workflow approval,
you can use classification and maintain the levels in a
characteristic. We use a characteristic of type
CEBAN-GFWRT.
Michael McLey
MBUSI - IT Parts & Administration
Mercedes-Benz US International, Inc.
1 Mercedes Drive
Vance, AL 35490
PHONE: (205) 462 - 5239
EMAIL: michael.mcley at daimler.com
-----Original Message-----
From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu]
On Behalf Of Swathi Devireddy
Sent: Wednesday, February 26, 2014 12:35 PM
To: sap-wug at mit.edu
Subject: Purchase Order Approval:Organizational Unit
Hi,
We have a simple Purchase Order Approval Scenario. We have
different Business Units (E.g Manufacturing/Finance).
Based on the Amount of the PO it should goto the person for
approval.
E,g
0
- 5000$ --
- Manager
>5000$
-10000$ -
- Director
>10000$
-
-Senior Director
If amount is greater than 5000$ its 2 level approval
We want to maintain an Org Unit for this approval process.
How can we maintain the amounts in Org Units.
Suppose amount is 6000$ it will go directly to Director.Also
want to avoid Z table creation as much as possible.
I have created Org Units for Each Business Unit and defined
the hierarchy. Any idea where I can maintain this amounts
also to control the flow.
Regards,
Swathi
**************** CAUTION - Disclaimer ***************** This
e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION
intended solely for the use of the addressee(s). If you are
not the intended recipient, please notify the sender by
e-mail and delete the original message. Further, you are not
to copy, disclose, or distribute this e-mail or its contents
to any other person and any such actions are unlawful. This
e-mail may contain viruses. Infosys has taken every
reasonable precaution to minimize this risk, but is not
liable for any damage you may sustain as a result of any
virus in this e-mail. You should carry out your own virus
checks before opening the e-mail or attachment. Infosys
reserves the right to monitor and review the content of all
messages sent to or from this e-mail address. Messages sent
to or from this e-mail address may be stored on the Infosys
e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
If you are not the addressee, please inform us immediately
that you have received this e-mail by mistake, and delete
it. We thank you for your support.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
More information about the SAP-WUG
mailing list