There can be many reasons for that error. The most likely causes are either the joins between tables or a condition statement with an incorrect conjunction statement. It used to be that when one wrote a condition and then modified part of the condition that the field would revert to the Company field. If you had a Boolean statement and Company was not true/false, it would throw this error. A quick way to find the error is to look at the SQL statement on the first page.If there is nothing obvious, try building a duplicate query and test after every table or condition is added.
Yes, if UD fields are utilized by the solution then they will need to be created before the solution can be imported. If you’ve never used the UD table before, it is possible to bring the fields in as part of the solution. If the table has any fields in it, you’ll have to add those fields manually. VendorDetail_UD.CriticalSupplier_c. The trick is knowing the attributes of the field. in this case, it looks like it should be the same as Vendor.VendorNum. Always add UD fields and tables when everyone is off of the system and no processes are running. If the table in UD Maintenance does not say it is in Sync after you regenerate data model and IISRESET then repeat the process again.Once it is all synced, import the solution file.I hope this helps.
Note: Be careful about bypassing new purchase suggestions. The system will want to create a suggestion if it is not linked to a PO. Orphan records between Purchase Orders and Requisitions are hard to deal with.Some of our companies have created email alerts that a new Requisition has been approved for Purchasing. That informs our Buyers and interested parties that a Requisition is waiting to be turned into a PO. Buyers could then run Generate PO Suggestions and process the Requisition information.Another more difficult option would be to replicate the Generate PO Suggestions process for the Requisition and create the records with a BPM. Buyers could then open New PO Suggestions and process them thru like normal.I hope this helps.
First, Preach. Amen. I loved Crystal Reports and thought SSRS was a step in the wrong direction other than the fact that you can write reports that expand when someone wants to see detail. Second, I noticed early on that Epicor wrote a lot of sub-reports. This allows them to feed a list of variables or keys to the subsection and thus display subsets of the data in relative order. Another approach if you have Advanced Print Management is for the data to be spooned out is small subsets of the data. It creates a series of small specific reports rather than dealing with all of the data at once. I hope this helps.
I’ve seen problems like this where they had to increase the limit in the webconfig file. Also, check your Process MRP settings. Number of MRP Processes and Number of MRP Schedulers should not exceed your hardware. Finally, check to see 1) the last log created. 2) other logs which might contain warnings or errors. Too many errors might cause the process to lose threads until it can no longer run. Example: Inactive components in jobs. Two MRP runs at the same time in the system agent. Record locks…. I hope this helps.
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.