Sage 100

 View Only

  • 1.  Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-14-2023 14:50

    I have a Sage 100 Adv client asking me to edit some customer #'s in A/R Inv Hist and S/O Hist, for data they're pulling from Sage 100 into BI.  Although initially it seemed doable, I'm now having second thoughts re: any possible implications.  For example, we obviously want to avoid running into issues down the road during an Upgrade or rebuilding utilities or whatever.  Where I'm concerned is if the system is misled based on these changed sales order and invoice customer #'s, and causes data issues, errors, etc.  Although we had considered other possible feasible workarounds, it seems we may need to further address but I'm eager to hear some feedback.

    TIA.



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------


  • 2.  RE: Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-14-2023 15:30

    Create a UDF and import into that with the changes they want?



    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    ------------------------------



  • 3.  RE: Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-14-2023 15:45

    We flat out refuse to edit audit fields in Live data. 

    UDF's... sure... and occasionally SalesPerson codes, but not key fields like CustomerNo.

    If it is a permanent change, do a customer renumber / merge.

    Or perhaps do a data extraction to a SQL database, where you renumber / translate in the query... leaving the original data as-is.



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 4.  RE: Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-15-2023 11:05

    Agreed.  I like Phil's idea of adding a UDF as a customer number alias / alternative number.



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------

    Original Message


  • 5.  RE: Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-17-2023 11:45

    Awesome, thanks!!  Going the UDF route.



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------

    Original Message


  • 6.  RE: Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-17-2023 11:48

    If you import into invoice history, be careful if you use DateUpdated for automated reporting.  Usually that is the date the user clicks Yes to update the invoice batch... but if you import to the table, the DateUpdated will be affected.



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 7.  RE: Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-18-2023 08:29

    @Kevin Moyes, can you clarify your last post re: 'DateUpdated' if you have a chance.



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------

    Original Message


  • 8.  RE: Looking for feedback re: editing customer #'s in A/R Inv Hist and S/O Hist

    Posted 07-18-2023 09:49

    We occasionally set up external automated reports (Visual Cut) based on when invoices are posted (like emailing shipping notifications the day after posting), using DateUpdated as the filter (eg. because invoice dates are not reliable if they are not posted over a weekend...).

    Use VI to import to invoice history: all the DateUpdated values are refreshed, causing a resend of those shipping notifications... or whatever the automated reporting does.



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


Related Content