Sage 100

 View Only

  • 1.  "Next" Not Available in VI Import

    Posted 10-31-2023 09:58

    Client needs a Bank Rec deposit import, and Entry Number is a required numeric field where the "Next" operator is not available.  We can't use "Incr" because there are multiple imports per day.  These imports will happen automatically, so user input is not possible.  Any ideas?



    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    spawlowic@rklesolutions.com
    (717) 735-9109 Ext. 4352
    ------------------------------


  • 2.  RE: "Next" Not Available in VI Import

    Posted 10-31-2023 13:43

    What about including a sequence # column in your source file?  Or maybe you can import to G/L Trans JE instead?



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



  • 3.  RE: "Next" Not Available in VI Import

    Posted 10-31-2023 13:47
    Edited by Brett Zimmerman 10-31-2023 13:47

    Maybe this kb will help (in case you haven't seen it):

    How to import into Bank Reconciliation Transaction Entry (BR_Transaction) using Visual Integrator

    Description

    Cause

    Resolution

     CAUTION: Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst.

    Background:

    Bank Reconciliation Check, Deposit and Adjustment Entry has two methods of data entry split into two separate tabs.

    The first tab for checks, and the second tab for deposits or adjustments to the account.

    The two imports share some key fields including BankCode and DocumentType, therefore it is necessary to import into either one or the other using separate or chained import jobs.

    To import into BR_Transaction, Check Entry:

    • Design an import into BR_Transaction using the following fields in the order listed below:
      • BankCode
      • DocumentType (set to C for checks)
      • CheckNo
      • EntryNo
      • CheckDate
      • ReferenceNo
      • CheckPayeeName
      • CheckAmt
      • ClearedBank
    • Note: Entry Number can be set as an incremental assign, making sure to note a default (starting) value in the import properties window for that field

    To import into BR_Transaction Adjustment, Deposit Entry:

    • Design an import into BR_Transaction using the following fields in the order listed below:
      • BankCode
      • DocumentType (set to A for adjustments / deposits)
      • TransactionDate
      • EntryNo
      • AdjustmentType
        • A = Adjustment
        • B = Bank Charge
        • D = Deposit
        • I = Interest
        • N = NSF
        • W = Withdrawal
      • DocumentAmt
      • ClearedBank
    • Note: Entry Number can be set as an incremental assign, making sure to note a default (starting) value in the import properties window for that field
    • Note: If importing the DocumentDate field; the DocumentDate and TransactionDate fields need to be the same dated column in order for the DocumentDate field to properly populate

    Solution Properties

    Solution ID
    224924250052886
    Last Modified Date
    Mon May 02 23:35:49 UTC 2022
    Views
    14



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

    Original Message


  • 4.  RE: "Next" Not Available in VI Import

    Posted 10-31-2023 14:22

    @Brett Zimmerman that will depend upon the third party provider's ability to add a sequence number column; since no humans will touch this, it has to be automated; I was thinking the same thing but am unsure if they will be able to add sequential numbers that will carry over into each of the multiple files per day.  I originally started out in G/L Trans JE Entry but had an issue and switched to GJ Entry with a Bank Rec import; now I'm back to looking at Trans JE Entry.  Incr assign won't work because there are multiple files per day and each line-item's entry number must be unique for each day.



    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    spawlowic@rklesolutions.com
    (717) 735-9109 Ext. 4352
    ------------------------------

    Original Message


  • 5.  RE: "Next" Not Available in VI Import

    Posted 11-01-2023 09:39

    It's kind of an off-the-wall idea, but could you just use a randomly generated number for the EntryNo?  The RND() function, basically?



    ------------------------------
    Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
    ------------------------------

    Original Message


  • 6.  RE: "Next" Not Available in VI Import

    Posted 11-01-2023 11:48

    Nice idea but I'd be wary of a rare duplicate causing problems.

    My general strategy for this (depending on the source data format... if txt or csv) is to run the file through a VBScript to add a column with what I need for VI.



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

    Original Message


Related Content