Sage 100

A client on Sage 100 2024 Advanced ( they are NOT using Production Management which I presume is the P/M noted in the error)

They emailed the following ( highlighting is mine ): 

"Object reference not set to an instance of an object. API Error: Module P/M is not on file." errors with eBridge Amazon order imports intermittently.   1-4 per day.  This results in a sales order in Sage with only header data, no lines.   A retry of the order import always works, but the order must first be deleted in Sage.   eBridge is saying this is purely a Sage 100 issue

This seems like it's probably an eBridge issue or somehow related due to the mention of API Error? Or could this in fact be Sage's problem? Has anyone with eBridge dealt wiht this?

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

Having written a bunch of API for Sage 100 code, the problem starts with the Sage BOI objects returning bogus error messages like "Module x/x is not on file" when that module is not even installed, to the point where my error handling routines have a list of phrases that cause the code to ignore the error message (my favorite is "Customer Number is not numeric" - of course not, the field is a damn STRING), and I only log error messages if a write statement fails, not if an error message exists.  There is also the whole  Sage 100 architecture not understanding what objects are supposed to be problem - Sage 100 in the UI won't let you save an order with no lines, but BOI will.  An Object should behave the same no matter where it is called from.  This area is the root of most VI headaches.

That being said, if "API Error" is in the message, then that is coming from the eBridge BOI code, because Sage 100 doesn't actually have an API, which is why myself and others have written ones for it.  So they will need to answer how their error handling works and what the real issue is.

Phil

------------------------------
Phil McIntosh
Friendly Systems
------------------------------

I agree with your thoughts and as soon as I saw the API error I advised the client that eBridge should probably take the lead. Naturally, with 85% of ISV integrations it's a great game of "prove it's us". I advised them to talk to eBridge further.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

Original Message:
Sent: 10-21-2025 10:43
From: Phil McIntosh
Subject: eBridge: API Error: Module P/M is not on file - Sage 100 2024 Adv

Having written a bunch of API for Sage 100 code, the problem starts with the Sage BOI objects returning bogus error messages like "Module x/x is not on file" when that module is not even installed, to the point where my error handling routines have a list of phrases that cause the code to ignore the error message (my favorite is "Customer Number is not numeric" - of course not, the field is a damn STRING), and I only log error messages if a write statement fails, not if an error message exists.  There is also the whole  Sage 100 architecture not understanding what objects are supposed to be problem - Sage 100 in the UI won't let you save an order with no lines, but BOI will.  An Object should behave the same no matter where it is called from.  This area is the root of most VI headaches.

That being said, if "API Error" is in the message, then that is coming from the eBridge BOI code, because Sage 100 doesn't actually have an API, which is why myself and others have written ones for it.  So they will need to answer how their error handling works and what the real issue is.

Phil

------------------------------
Phil McIntosh
Friendly Systems
------------------------------