Scripting

  • 1.  SO Duplicate Customer PO Number Warning - During VI import?

    Posted 06-05-2024 12:46

    A customer needs to use the duplicate purchase order warning feature.  We see that it performs as described when manually entering a sales order.  However, when importing sales orders, there does not appear to be a warning written to the VI Job log.  Assuming that Sage intends this feature for manual entry only, would script based solution work?  



    ------------------------------
    Rebekah Veuger
    President
    ClearPoint Consulting Group
    619-997-1627
    ------------------------------


  • 2.  RE: SO Duplicate Customer PO Number Warning - During VI import?

    Posted 06-06-2024 12:18
    Edited by Alnoor Cassim 06-06-2024 13:45

    Rebekah - long time no hear! Back in the day before this feature became available, I would add some Perform logic to the import. Today in your import you should be able to call the duplicate checking function in a simpler way but I'm surprised this checking doesn't happen automatically. I'll get back to you with an example on how to do this once I get a chance unless someone else posts a solution first. In meantime here are some dumb, humor me, type questions which is what version are they on and do they have it turned on in S/O Options for the company code they are running the import in?



    ------------------------------
    Alnoor Cassim
    Accounting Systems, Inc. (ASI)
    ------------------------------



  • 3.  RE: SO Duplicate Customer PO Number Warning - During VI import?

    Posted 06-07-2024 01:17

    In testing on v2022, I do get the warning during V/I import in the log. The record is marked as "Passed with Invalid Fields" where the duplicate PO warning appears next to CustomerPONo if you drill into the log record. It's there but you have to look for it. Also, in Role Maintenance, as you see below you can uncheck "Allow Duplicate Customer PO Numbers". This means instead of seeing a warning, both manually in the UI and in the import, a duplicate PO is not even allowed. In the import it will leave the field unpopulated.

    ** Also, regardless of that setting, if you want the V/I import to outright fail the importing of the order due to a duplicate PO found, I have an example I can post that uses Temp fields that run the Duplicate PO Check function and then only conditionally assigns the CustomerNo if a dupe was not found.

    Hope that helps.



    ------------------------------
    Alnoor Cassim
    Accounting Systems, Inc. (ASI)
    ------------------------------



  • 4.  RE: SO Duplicate Customer PO Number Warning - During VI import?

    Posted 06-10-2024 11:32

    Super helpful Alnoor!  Thank you!  That nugget in security settings is ideal.  I really do with Sage documented its functionality better!  They are using Sage 2021 Premium.  I will review the feature as you described.  



    ------------------------------
    Rebekah Veuger
    President
    ClearPoint Consulting Group
    619-997-1627
    ------------------------------