Error message when you try to open the Purchase Order Entry window in Microsoft Dynamics GP: "Purchase Order Processing setup information is missing or damaged"


Microsoft Dynamics GP 2010 and 10.0

  1. On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to System, point to Security, and then clickAlternate/Modified Forms and Reports.
  2. In the ID box, type the user ID.
  3. In the Product list, click Project Accounting.
  4. In the Type list, click Windows.
  5. Expand the Purchasing folder.
  6. Expand the Purchase Order Processing Setup folder.
  7. Click Project Accounting.
  8. Click Save.
  9. On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to Purchasing, and then click Purchase Order Processing.
  10. Click Project.
  11. Make the appropriate selections.
  12. Click OK.

Comments

Post a Comment

Popular posts from this blog

AOS machines application ( events )

Here are some events from the AOS machines application event that can be useful when managing an AOS: Event Log Entries How to Troubleshoot Event ID 149. Object Server 01: Ready for operation Use this to verify the AOS build/version information from the kernel build section. Event ID 172. Use this to verify the .Net Business Connector build. This is helpful if you think the issue is related to components not being on the same build. Event ID 1000 Use this information along with any Event Id’s of 1001 to confirm the times when the AOS crashes. Event ID 1001 This indicates that they have the option marked to send mini memory dumps to the Watson site. Pass the contents of this event on to your Escalation Engineer so they can review it to see if there is information that points to the issue. Object Server 01: RPC error: RPC exception 1726 occurred in session X This means that the AOS had data to send back to the client but the client was no longer available....
Read more

Table ID for the tables in AX 2012 R2

Table ID for the tables in AX 2012 R2 Hi, AccountingDistribution ( accounting distribution 7452 ) AccountingDistributionEventTmp ( accounting distribution 100001 ) AccountingDistributionTemplate ( Accounting distribution template 7453 ) AccountingDistributionTemplateDetail ( Accounting distribution template detail 7454 ) AccountingDistributionTmp ( AccountingDistributionTmp 100002 ) AccountingDistributionTmpAmounts ( Accounting distributions 7455 ) AccountingDistributionTmpJournalize ( accounting distribution 100003 ) AccountingDistributionTmpPurchSummary ( Encumbrance summary 7446 ) AccountingEvent ( Accounting event 7456 ) AccountingEventDateTmp ( Accounting event 100004 ) AccountingEventTmp ( Accounting event 100005 ) AccountingTmpEvent ( Accounting event 100006 ) AccountSumMap ( Account totals 1326 ) AddressCountryRegionBLWI ( BLWI country/region 1049 ) AddressCountryRegionGroupBLWI ( BLWI country/region groups 1050 ) AddressZipCodeImportLog_NL ( ZIP/postal code import log...
Read more

Common Problems & Solutions ( AX 2009 )

Common Problems & Solutions We have found that in a number of AOS crash cases they are resolved by installing the latest kernel hot-fix. Therefore it is recommended that you consider implementing the latest kernel roll-up as part of your maintenance. This could mean applying the latest kernel rollup once a quarter. Since the kernel hotfixes are cumulative, easy to uninstall, and do not include X++ fixes they are typically able to be installed with a lot less effort than an application hotfix. We do recommend that you apply the kernel rollup in a non-production environment and do some testing before applying it in your production environment. Please see the information from the  AX Kernel Patching  section on how to update to the latest kernel hotfix rollup. If you implement code when users are in the system you could have cache or data access issues that result in an AOS crash. Therefore, when implementing code in your production environment it is recommended that you...
Read more