I would like to know if anyone among you has implemented the integration of Ephesoft with M3 on supplier invoices?and more specifically on the management of the supplier table in Ephesoft?Thanks
Hi Dens,
Yes we do have implemented Ephesoft integration with M3. Management of supplier table in Ephesoft can be done in various ways. Could you please give more information about your context ?
Hi David. I'm glad to see your answer. We're also interested in using Ephesoft to register Supplier Invoices in m3. Now we do it manually through APS100 FAM function 400. Do you know if this integration with m3 also replaces the need for manual entry of information completely?
Hi Theodore,
Yes it does ! Ephesoft allows you to scan invoices information and prevent you to enter the information manually. Then, the digitized invoice is sent to M3 so that it can be integrated using the IDC connector.
While studying more in depth the integration of Ephesoft with M3 on supplier invoices, I noticed that, even if the "standard" integration exists and its configuration is pretty well documented, this integration on certain functionalities is not completely achieved.
In particular, to "help" find the M3 supplier number on a scanned invoice, "specific" tables must be implemented in Ephesoft on request.
This is provided as an option in the process and is what I just asked support for.
In theory, there was another way for Ephesoft to query M3 via APIs.
But in reality, this is a new feature of Ephesoft but cannot be used with M3 because of the level of security that ION requires (OAuth2) and that Ephesoft does not know how to manage (yet).
On the other hand, even when these tables are created, they will still have to be fed regularly from M3.
And this is where the "unfinished" side of the integration appears because nothing is really planned and delivered (to install) as standard.
Would you have any information to share with me on these elements which, for me, must be part of the "standard" integration that we want to use from start to finish?
Hello, We are in the same situation, we are looking to implement Ephesoft as a scanning solution. We are struggling to find best practices. We have tested to setup the "standard integration" which basically contains of saving the invoice in IDM and uploading the invoice to APS450 and it seems to work. But as you write it would make sense to be able to do lookups directly from ephesoft to find the correct supplier etc.
Would appreciate if anyone that have implemented ephesoft with M3 can share their experience.
The integration we are implementing utilizes API calls and a standard BOD integration (MCBOD_SupplierPartyMaster_Sync_Out) to sync vendors to provide a vendor database for Fuzzy searches in Ephesoft. For scanned images where a PO number can be extracted API PPS200MI_GetHead is used to validate the PO and Vendor data. Otherwise, no PO provided, or invalid PO, the Vendor database in Ephesoft is used for a Fuzzy search based on extracted attributes.
At Pfaudler we are in the middle of he implementation. We are now using it for the "input of invoices" but we are struggling with the step of matching the purchase order lines (we have a lot of partial delivery). I would be happy to hear about other experiences or share our process
Hi Elisabetta,
I think you will have to build your matching logic in MEC map.
I had a project where company had lot's of POs, lots of partial invoicing. Headers matching was not an option, it had to be done on lines level.
I built matching logic in MEC map.
Using various parameters like M3 ITNO, supplier item ID, invoice line price and quantity, etc, I try to identify what PO line is being invoiced.
Regards,
Kirill
Thanks Kirill
sounds interesting. Until now we have not been able to find a right way to go. The consulting company is helping us with various idea but until now it is not working. Would you have a possibility to show me something more about your settings? We are in the Multitenant Cloud.
It's not about settings. We use APS450MI APIs to load AP invoice to M3 and match it with PO.
APS450 program behaves same way as APS450MI API.
First we create batch header record. At this point we have to decide how to match this invoice with PO.
If you select option 1-matching on line level, we need to add invoice lines to batch header and for each invoice item line we need to provide PO number and line.
When you look at your suppliers invoices, are there PO numbers and PO line numbers?
