Forums / Categories / PeopleSoft Supply Chain Management / Supplier Performance: PO Due Date vs Original Promise Date?

    Supplier Performance: PO Due Date vs Original Promise Date?

    We have a little discussion going as to what is best to measure supplier performance against:

    1. Receive Date vs PO Original Promise Date?

    2. Receive Date vs PO Due Date?

    Please chime in as to what your ops do and why that avenue was chosen?  (PeopleSoft Supplier Analysis is based on Receive Date vs Due Date)

    Thanks for your input!

    Dan Rotermund

    Thank you Wendy & Steve, for your replies. This certainly helps in our plan discussion.

    I do like the idea of the customized REASON code. We were contemplating the same issues of "Your Fault / Our Fault" scenarios.

    We also have developed and deployed an overall supplier scorecard process that takes in simlar data and is also coupled with their profile question responses for an overall quarterly look under the hood.

    Thanks again!

    Dan

    Hello Dan,

    We measure by receive date vs. PO Due Date,
    but it would probably be better to measure against the Original
    Promise Date, so you can tell if they kick the can or not.

    Thanks,

    Wendy

    Wendy
    Jamison
    |
    PeopleSoft Support/ Sr. Accounting Systems Analyst | KCP&L
    | 1200 Main Street, 17th Floor| Kansas City, MO 64105
    |816-654-1902

    This
    document and any attachments are intended solely for the named
    addressee, are confidential and may be subject to legal or other
    professional privilege. The copying or distribution of them or any
    information they contain, by anyone other than the addressee, is
    prohibited. If you have received this document in error, please let
    us know by telephone and delete all copies from your computer
    system. It is the recipient's responsibility to check this email
    and any attachments for viruses. Any confidentiality or privilege
    is not waived or lost because this email has been sent to you by
    mistake.

     
Log in to reply

Looks like your connection to Quest Oracle Community was lost, please wait while we try to reconnect.