This information is valuable for the use cases listed below and more

• An error occurs with a third-party program in Sage 100.
• The error refers to a data file not mentioned in the TRSG or online. For example: "Error xx AP_140ManualCheckRegister_Upd.pvc".
• The Installed Modules listing report indicates non-standard programs with a third-party developer listed as the publisher.
• Path errors or other undocumented errors during installation or upgrade.

[BCB:5:Third-party support:ECB]

Sage 100 versions 4.0 to 4.50, and 2013 and higher

1. Open Modules, Library Master, Reports menu, Installed Modules Listing.
2. Check the modules listed for non-standard Sage 100 programs/modules and the publisher listed other than Sage.
3. Asterisks by the modules, or level numbers that aren’t consistent with the existing level number.

Sage MAS 90 or 200 versions 3.71 and earlier

1. Open Modules, Library Master, Utilities menu, Installed Applications Listing.
2. Check the applications listed for non-standard MAS 90 or 200 programs.
3. Asterisks by the modules, or level numbers that aren’t consistent with the existing level number.

Verify activation of a third-party module for specific companies

1. Open Library Master, Main menu, Company Maintenance, and select the Company Code.
2. Review the Activated Modules area for any non-standard application modules.

An error occurs with third-party programs in Sage 100

Some programs listed in error messages are from a third party. For example, the program name includes the module code followed by a number and an underscore.

 NOTE: Third-party programs are in the "..\MAS90\Links" folder or in the main program directory for one or more modules, such as AR, CI, and SO. However, sometimes, a developer directly modifies a standard Sage 100 program, which isn’t a best practice. 

• AR_Customer_Ui.pvc is a standard Sage 100 program, whereas AR_531Customer_ui.pvc is a third-party program.
• SO_InvoicePrinting_Rpt.pvc is a standard Sage 100 program, and SO088_InvoicePrinting_Rpt.pvc is a non-standard.
• AP_140ManualCheckRegister_Upd.pvc is an add-on supported by Scanco. However, Sage supports it when the Production Management module is present.

For known 3-digit Developer Codes, use the Library Master, Data File Display and Maintenance (DFDM) utility to view records in the SY_Developer.m4t system data file. Each record includes a Developer Code and Developer Name fields. For example, the Developer Code "088" in the SY_Developer.m4t file refers to Kissinger Associates, Inc.

Program files added by third-party programs

 NOTE: Third-party enhancements for Legacy application modules typically don’t use the Links folder.  

• Standard Sage 100 program files typically don’t have numbers in their file names.
• The third-party developers typically use numbers in the progam files.
• An error message referencing a non-standard file indicates an issue with a third-party program.
• Removing files from the Links folder that resolve the error indicates a third-party program issue.
• The SY_Developer.m4t data file contains records with a 3-digit DeveloperCode key and DeveloperName field.

Not all third-party developers follow the protocols to add information to the reports. Some modify only a single standard Sage 100 program file, or install enhancements without their signatures. Some third-party enhancements still appear as installed and leave traces in other areas even after complete uninstallation.

How to determine the version and product update of Sage 100 installed
How to disable a customized panel temporarily customized with Custom Office