Hi Luann- Yes. This would all be done through reason code maintenance. You can setup separate reason codes with specific GL codes to be used for each of these instances. I believe these would all fall under Inv.Adjustment type reason code. Under there you will see a checkbox for “Count Discrepancy Reason”. It’s been a while but I believe if you check this it will show up in the pick list for cycle count reason. -Nick
Hi-We use DMT if the qty is large. You could grab all of your legacy SNs and DMT them all in. For RMA, when you click on the serial number button it brings up the common serial number entry popup. There is the ability in that popup to create an SN. Not sure if it is the same for FS but the SN popup screen is almost identical throughout Epicor. Have a look.-Nick
The only way I know how to do this is to give them direct access via paired down permissions. Are you cloud or on-prem? We used an integration to allow receipts against a PO. -Nick
Oh...and assign the product group to the part…-Nick
Ryan- I agree with Paul. My preference is product groups assigned to parts. In the product group you would assign a GL control code:Go to control code maint to setup new corresponding control codes ( before assigning to prod group) and set the GL account. -Nick
Hi Jack- Are you familiar with BAQ export? Pretty simple. Take the same BAQ used in the dashboard and just set a schedule to export to CSV. Or you could use a script with DMT to export and use Windows scheduler to schedule. -Nick
John- Thank you. Much appreciated. -Nick
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.