Infor M3 BE Advanced Program Interface (API)
The data transfer between Infor M3 BE and Infor M3 SWB is managed through the use of Infor M3 BE APIs. They are also known as MI-programs. The Infor M3 BE APIs provide the advantage of allowing complicated logic when retrieving data, while a high performance level is still retained, as compared to, for example, ODBC/SQL.
The Infor M3 BE APIs rely on the same part of the System Foundation as the M3 Infor M3 BE Web Applications. Before starting to use them at a customer site, the Internet subsystem (example MVXBINET) has to be created and the Floating Protocol Wrapper has to be installed.
If there is a communication problem, then use the following trouble-shooting checklist:
| Symptom | Possible reason | Action |
|---|---|---|
| Unable to log on | Wrong password | Retype your password correctly. Be sure that NUM LOCK is not accidentally on. |
| Unable to log on | Wrong setting in the libraries panel. | The MI-program that you tried to call was not found in the specified library. Click the button to find out if the library is correct. You may use the OS/400 WRKOBJ command to see if the program object is really there. (Note: this is not a problem in a Infor M3 BE NextGen system.) |
| Connection refused | FPW is not started | Go to the menu in Infor M3 BE and start the Floating Protocol Wrapper (menu item 90). Retry. If problem remains, check that the internet subsystem is started (WRKSBS you should see MVXBINET in the list of active subsystems), and if not, start it (menu item 60), then start the FPW. |
| Connection refused | FPW started but configure for the incorrect port. | Contact your technician to find out what port should be used, then correct the psmi.INI file, located under &/Control. |
| FPW Host xxx not found | Wrong protocol wrapper name | Correct the Protocol Wrapper Name in the psmi.INI file, located under &/Control. It could be an IP-address or a known server name. |
| MvxSockInit:Connect() Failed. Sockets error | Wrong IP-address | Correct the Protocol Wrapper Name in the psmi.INI file, located under &/Control. It could be an IP-address or a known server name. |
| Connected but no data imported | Wrong library list entries connected to the user or the users company and division in MNS150. |
Check and correct the user in MNS150: the settings should be exactly as for Infor M3 BE users not running Infor M3 SWB. Relevant fields to check: Library list, Company, Division. |
| Connected but no data imported | Wrong company/facility/warehouse/ planning area in Server Interface tab | Check and correct Company, Facility, Warehouse and Planning Area in the parameters/server interface tab in Infor M3 SWB. Planning area should be blank, the others must have values. |
| Connected but no data imported | Too short horizon in server interface tab. | Check and correct the Horizon in the parameters/server interface tab in Infor M3 SWB. |