P1 365 Architecture and User Interface

We’ve used the architectural strengths of our P1 Version 1 product to allow us to build an embedded, integrated and automated EDI solution for D365.

  • The front-end UI has been redeveloped in X++ and the D365 UI controls

  • The software is embedded in D365

  • The software runs in customer’s Azure cloud

  • There is automated EDI/ERP integration using standard D365 Web Service technology

  • It works by exception, D365 notifications/e-mails

The EDI processing engine has been left in C#. This has been done to allow P1 to work both with D365 and other ERP systems.

So, if your customer runs D365 in one division and SAP in another P1 will process EDI transactions for them both.

1.png

You’ll see here we’ve added a new menu item to the D365 main menu, EDI Processing. This menu item behaves exactly the same as all other D365 menu items.

3.jpg

This is the main EDI Transaction screen.

4.jpg

From this screen a user can track progress on any EDI transaction and where required link directly to the corresponding D365 transactions.

With D365 transactions you can also come back the other way, if you’re working with a sales order or invoice for example to can link back directly to this screen to see the state of the EDI transaction.

If you’re familiar with the D365 Controls, this screen behaves exactly the same, you can search & sort on

  • Transaction Type

  • Trading Partner

  • Dates

  • Purchase Order Number

You also have a summary box on the left-hand side that updates automatically. On the right-hand side, you can see a number of EDI related menu items.

5.jpg

This screen is where we add the data for EDI & D365 processing.

Under the EDI settings, the data on the left is for EDI processing, the data on the right to allow P1 to identify the D365 Customer Number and Address Code.