Sage 100

 View Only
Expand all | Collapse all

Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

  • 1.  Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 10:30
      |   view attached
    Attempting to import material transactions into work ticket transaction entry.  My first roadblock (of many?) is figuring out how to import the WorkTicketKey$ field.  There is NO number field, just the key field.  I have looked at the KB, but it refers you to your reseller.

    Has anyone solved these secrets?




    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    (540) 221-4444
    ------------------------------


  • 2.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 12:05

    I have not imported into 2022, but have you tried importing the work ticket number into the KEY field? I would expect the business logic to translate the number to the key automatically like it does for GL account number/account Key and payroll employee numbers

     

     

     

     

    Don't miss out on our 2022 Fall Sage 100 User Group: View the details

     

     

    David Overholt

    DWD Technology Group, Inc.

    9921 Dupont Circle Drive West, Suite 300 | Fort Wayne, IN 46825

    260.423.2414 main

    800.232.8913 toll free

    sagesupport@dwdtechgroup.com

    www.dwdtechgroup.com

     






  • 3.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 16:23
    Thanks.  Tried that and it threw a different error.  Under lines, there is a line sequence number.  I wonder if you have to import that as well.  Just trying to find someone who has been successful.  I hate being a pioneer.

    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    (540) 221-4444
    ------------------------------



  • 4.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 16:40
    We're running into a similar issue when trying to import labor into Sage 2022 PU2. Following is what Scott Brady sent me.  That resolved the initial error I was getting. However, now we found that the import only works if we have the actual WT key in the source file.  WT keys created prior to the upgrade were the WT number.  Since the upgrade a random key is being assigned instead and VI doesn't seem to be able to do the cross reference.  One of my team members reached back out to Scott Brady and we're waiting to hear what he has to say.  

    In regards to the error your Error: "HS Record Invalid or Write Failed. The employee number is required" when importing into PM_LaborEntry: 

    To resolve, place TransactionType before EmployeeKey on import job.  I duplicated the issue and wrote up KB116836 - Error: "HS Record Invalid or Write Failed. The employee number is required" when importing into PM_LaborEntry.  Note: When manually entering, we populate the TransactionType before EmployeeKey

     



    ------------------------------
    Mary Jo Krueger
    Senior Software Consultant
    CLA (CliftonLarsonAllen LLP)
    ------------------------------



  • 5.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 17:07
    Client still on v2022 PU 1.  The key generated when I did a one line entry for material transaction (to see what is written) was encrypted (not the WO number).  Just makes you wonder the depth of QC checks....

    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    (540) 221-4444
    ------------------------------



  • 6.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 17:08
    What QC checks?

    ------------------------------
    Mary Jo Krueger
    Senior Software Consultant
    CLA (CliftonLarsonAllen LLP)
    ------------------------------



  • 7.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 17:18
    We tried the WT No originally and that failed.  Only importing the WT Key worked.

    ------------------------------
    Scott Firgens
    CLA (CliftonLarsonAllen LLP)
    ------------------------------



  • 8.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-22-2022 18:01
    Where do you locate this without DFDM?  Modify the inquiry screen to display it?  And if you have multiple WT's?

    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    (540) 221-4444
    ------------------------------



  • 9.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 09-29-2022 11:23
    We worked with Scott Brady at Sage and found a solution to our issue with importing into the Production Management WorkTicketKey field with VI.

    Our import source file had the last 5 digits of the WT #, not all 12 digits.  So we had tried a calculation of temp2("0000000")+temp1​(last 5 digits) in the WTKey field.  But it would not recognize the WT# and convert it to the key.  If all 12 digits of the WT# were in the import file, VI converted the WT# to the WTKey.

    Scott Brady sent us this formula and it works with only 5 digits in the import source file.

    _OBJ'ConvertToWorkTicketKey$("0000000"+Temp001$)



    ------------------------------
    Scott Firgens
    CLA (CliftonLarsonAllen LLP)
    ------------------------------



  • 10.  RE: Importing Production Management (v2022 Sage Rewrite) Transactions - Any Progress???

    Posted 11-21-2023 15:37

    Has anyone other than Scott had any luck with this?

    Scott's situation is an exact matches to my  problem exactly however it does not seem to work in my client I am currently hoping to upgrade this coming weekend, but we just realized that we had not updated the VI job for this.  The only difference between the answer below is that I had to modify it to pad with 5 zeroes because my import file has 7 digits.

    Oddly enough, I can't get the employee number to import either even though I'm using the same functions in payroll that are being used in another import job for this client.

    _obj'ConvertToEmployeeKey$(Temp004$,Temp007$)



    ------------------------------
    Thomas Rogers (TomTarget)
    Target System Technology, Inc.
    ------------------------------