Chris Giesbrecht
Forum Replies Created
-
Hi Ralph,
In my experience the transactions that are posted from in the transaction (not saved to a batch and then post the batch) usually show the person’s name who posted the transaction as there is technically no batch name to show for those transactions. If you are wanting to use the batch name for reporting purposes you will need to guide your staff to save the documents in a batch and post the batch instead of just posting the transaction.
Hope that helps you out!
-
Sorry, just realized you were looking at the open table. Then I would think those are likely stranded records. Could be caused by one or more of the following.
- GP crashed while someone was entering a JE and had not assigned a batch to it. Because GP will write the transaction to the database as it is entered it will put the user name in place for the batch before the document is saved in a batch.
- Posting error. If there was an error while posting a document that wasn’t in a batch and it didn’t finish moving the JE properly to the open year table. You could check if the document exist in open and current year tables.
- 3rd party product. If you have ISV products that are creating transactions, that could be another road to explore.
-
-
I echo what Jo has said. Database names have to be different.
Also, the is a product by Binary Stream that allows you to run multiple legal entities inside 1 GP company, so you can share all your master record information (customers, items, vendors, etc) between the companies if that would make sense in your scenario. We use it and it works pretty slick for us!
-
Hi Clay,
Absolutely there is a tool for that. And better yet, you probably have it (might need to be installed and turned on). It is called the Professional Services Tools Library, and referred to as PSTL (pronounced “Pistol”). You can install it from the GP installer. After it is installed you can either update item’s numbers or merge 2 items into 1 new item number. This will also update the IV, POP, SOP and other related core GP tables. It will update all the historical transactions. If you have a lot of 3rd party ISV products, you will need to know if it will work with them as well. Some it will work fine and some have additional things you need to do. You will probably want to test it out in a test company if you have to make sure everything works the way it should in your specific environment, as there will be no ‘undo’ button. There are also sql stored procedures that can be run to update in bulk if you have a lot of items to update.
Hope this helps you out!
-
Hi Howard,
Yes, SSRS would be able to run a report based off of any data in the SQL database. Unfortunately I am not familiar with the payroll module. If there is an out of the box SSRS report, it could be modified to bring in the specific MEM information that you are looking for. I have had to add MEM information to a lot of reports. If not, you might need to start from scratch. How are you collecting the data for your reports today? Smartlist?
-
A few other tips for combining master records
- Make sure the vendor you are combining into has all the correct data. For example if they have different payment terms, credit limit or GL accounts you need to ensure the destination vendor has the correct values that you want to use for the 1 vendor going forward.
- The master record combiners do not work with some ISV products. There are some ways around this and is dependent on the ISV’s table structure. I’d be happy to explain further if needed.
- If you are savvy with SQL and have eConnect installed you can execute the combiner with the econnect procedures.
Chris
