Sage 300 provides a functionality to customize sage 300 standard screen or to create a custom module as per the business requirement. Whenever an additional functionality is required in standard Sage 300 the custom module is created with a customized OCX screen. With this custom module creation and customized screens, we have to maintain its Roto.dat and Grp.dat files. These files are necessary for custom module or custom screens to be viewed in Sage 300.
In this blog we are going to discuss regarding the possible cause of the custom module screens or customized screens not getting opened in the development or test environment and solution for it.
New Stuff :- GL Accounts Statement Report
As we work on sage 300, we are probably familiar about roto.dat file and grp.dat files and their purpose. In the roto.dat file for each (screen) user interface it contains separate entry with register class ID and grp.dat defines the menu structure for Sage 300 module (for standard as well as custom). In case of adding additional customized screen there will need to add extra entry in these files as well in case of custom module in roto.dat file we need to add an entry for each user interface with its register ID to view into the sage 300.
Below is the screenshot of the roto file
While opening any screen system refers to roto.dat file and as per unique identifier defined for the screen and its registered class ID that screen control gets loaded. But, while opening customized screen or custom module screen sometimes error might occur as “Object is not defined in roto event file.” Please refer to below screenshot for the error message:
Kindly refer to example scenario below:
Suppose we are getting above error while opening GT2007 screen. As per above error message, we might think that there will be missing entry in roto.dat file for screen GT2007 but, as we can see in the screenshot below the entry is already present.
But, we can see in the screenshot above that for the screen GT2007 the type is wrongly mentioned as “STUB” instead of “UI” as specified for rest of the screens. So, the same error can be thrown by the Sage 300 system in case entry type is wrongly maintained anything else other than “UI”. This might cause due to human error while adding additional customized screen in standard mod also.
Resolution for this error is modifying this roto.dat file to change that specific entry type from STUB to UI and saving the roto.dat file and then reopening a company so that roto.dat file changes will reflect.
About Us
Greytrix – a globally recognized and one of the oldest Sage Development Partner is a one-stop solution provider for Sage ERP and Sage CRM organizational needs. Being acknowledged and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third party add-on development and implementation competence.
Greytrix offers unique GUMU
integrated solutions of Sage 300 with Sage CRM, Salesforce.com (listed on Salesforce Appexchange), Dynamics 365 CRM and Magento eCommerce along with Sage 300 Migration from Sage 50 US, Sage 50 CA, Sage PRO, QuickBooks, Sage Business Vision and Sage Business Works. We also offer best-in-class Sage 300 customization and development services and integration services for applications such as POS | WMS | Payroll | Shipping System | Business Intelligence | eCommerce for Sage 300 ERP and for Sage 300c development services we offer, upgrades of older codes and screens to new web screens, latest integrations using sData and web services to Sage business partners, end users and Sage PSG worldwide.
Greytrix offers 20+ addons for Sage 300 to enhance productivity such as GreyMatrix, Document Attachment, Document Numbering, Auto-Bank Reconciliation, Purchase Approval System, Three way PO matching, Bill of Lading and VAT for Middle East. The GUMU integration for Dynamics 365 CRM – Sage ERP is listed on Microsoft Appsource with easy implementation package.
The GUMU Cloud framework by Greytrix forms the backbone of cloud integrations that are managed in real-time for processing and execution of application programs at the click of a button.
For more details on Sage 300 and Sage 300c Services, please contact us at accpac@greytrix.com, We will like to hear from you.
The post Possible cause of “object is not defined in roto event file” appeared first on Sage 300 ERP – Tips, Tricks and Components.