Results 1 to 5 of 5

Thread: How to prohibit entering a purchase order for a vendor but allow inquiry to history

  1. #1
    Member
    Join Date
    Apr 2001
    Location
    MA, USA
    Posts
    260

    How to prohibit entering a purchase order for a vendor but allow inquiry to history

    We have inactivated some vendors with an "XV" search type but users can still enter an order. Tried row security to not allow view but users said they needed to see history. Is there any other way to stop entry for inactive vendors. Solutions greatly appreciated. TIA
    Sr. Business Systems Analyst
    OFS Fitel, LLC
    E1 9.0 Upd 2, T/R 9.1.0.3, Oracle DB 11g, Server:Win 2008 R2 64 Bit, Client: Win 7 & IE8 & Bottomline Transform

  2. #2
    Member
    Join Date
    Jul 2002
    Location
    Philadelphia,PA
    Posts
    358
    If you have access to Oracle support you could refer to Doc id 755938.1 which explains various options to render a vendor obsolete.

    thanks,
    Matt

  3. #3
    Item Help

    Hold Payment Code
    Alias: HDPY
    A code that specifies whether to hold payment of outstanding vouchers and prevent entry of new vouchers for the supplier. The hold code applies only to the supplier on a voucher. The hold code does not apply when the supplier is a payee on a different supplier's account. Valid values are:

    1 or Y
    Hold payment of outstanding vouchers and prevent entry of new vouchers for this supplier.

    2
    Hold payment of outstanding vouchers, but allow entry of new vouchers for this supplier.

    N
    Allow payment and voucher entry. This is the default.

    To hold payment of an individual voucher, rather than all outstanding vouchers, use a payment status code of H in the Voucher Entry program.

  4. #4
    we have also used a field on the supplier to indicate whether a supplier has been certified or not, and our PO programs have been configured to specifically look for that field to have a certain value to allow a PO to be entered. If that field isn't updated, then no PO can be created.

  5. #5
    New Member Olavo Henrique Dias's Avatar
    Join Date
    Nov 2004
    Location
    Brigham City, UT, USA
    Posts
    40
    I like the approach gine13tiger suggested, but as far as I know it wouldn't prevent users from creating Purchase Orders. They wouldn't be vouchered though...

    Here where I work we actually customized the P4310 to now allow orders to be placed for "VO" (Search Type for Obsolete Vendors on Address Book).
    We created an UDC with the list of invalid Search Types. It was actually a simple mod...

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.