Purchase Order Approval:Organizational Unit

[Priyank Dev]

Hi Swathi,
The position ID and org ID would be same across all the system.Logic goes
in this way -
  0             -  5000$ --
     - Manager
                 >5000$ -10000$ -
- Director
                >10000$             -
    -Senior Director

Now when you create a ORG structure for 3 different positions
Manager,Director,Senior Director the system generates 3 different unique
position ID say for manager Pos id 1,director Pos id 2 etc..
Logic-
if amount = 5000.
Call RH get struct FM and pass the position id.
Constant:lc_manager type char10 value '1'."manager position id
*same declare for other positions
*******Call FM to get the user id****************
CALL FM RH_GET_STRUCT.
Pass lc_manager.
else if amount >5000 or <10000
pass lc_director.
endif.
****************************************************
Regards,
Priyank Patil
9620372300






On Thu, Feb 27, 2014 at 12:05 AM, Swathi Devireddy <
Swathi_Devireddy at infosys.com> wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140227/02232f08/attachment.htm