Transforming the
D365 Supply Chain

ProcessOne 365 is built using standard technologies within Microsoft .NET

• C#. ProcessOne 365 is developed in C#. ProcessOne has 20 years’ experience in C# development.
• All ProcessOne 365 data is stored in SQL.
• Microsoft Azure cloud
• X++. The D365 Rest APIs and UI are developed in X++. These skills come from both Rangeline and ProcessOne.
• ProcessOne 365 is built on .NET 6

ProcessOne applied the following principles in the design of ProcessOne 365

• Trading partner set-up is simple and easily updated
• Data is pre-mapped directly from D365 to a wide range of EDI transaction sets
• All actions are automated, including send, receive and error notifications to users
• The flow and volume of EDI transactions are easily monitored and viewable
• People can search specific transactions, make needed changes, and print reports
• Adoption of AS2 as the communication mechanism. This means there is no other EDI or communication software required between ProcessOne 365 and your Trading Partners.

ProcessOne 365 will remain current with versions of Microsoft .NET and Azure.

In terms of updating and retrieving data from Microsoft D365, ProcessOne 365 is built on the .NET 6 architecture and integrates through

• Microsoft Open Data Protocol (OData) an open protocol that allows the creation and consumption of query able and interoperable REST APIs in a simple and standard way.
• Rest APIs, Representational State Transfer are service endpoints that support sets of HTTP operations (methods), which provide create, retrieve, update, or delete access to the service’s resources
• JSON, JavaScript Object Notation, an application programming interface designed for lightweight data interchange (text-based data exchange format) between two computer applications operating on the same hardware device or

Whatever technology is required to integrate, ProcessOne 365 has the capabilities to work with this.

• EDI, Electronic Data Interchange, the concept of businesses electronically communicating information that was traditionally communicated on paper, such as purchase orders and invoices. Technical standards for EDI exist to facilitate parties transacting such instruments without having to make special arrangements.
• B2B, Business to Business a situation where one business makes a commercial transaction with another. This typically occurs through web services technology, agreed between the parties in a one on one or one to many contract.
• B2C, Business to Consumer, the business model of selling products directly to customers, bypassing any third-party retailers, wholesalers, or any other middlemen.
• FTP, File Transfer Protocol, a standard communication protocol used for the transfer of computer files from a server to a client on a computer network.
• CSV, a comma-separated values file is a delimited text file that uses a comma to separate values. Each line of the file is a data record. Each record consists of one or more fields, separated by commas.
• Excel, many companies have important data locked up in Excel spreadsheets. ProcessOne 365 has capabilities to both import and extract Excel data.

By maximizing the digital handling of business data between business partners the entire D365 supply chain from end to end, is now automated including manufacturers, warehouses, 3PL’s, distributors and retailers.

ProcessOne 365 reaches into D365 using OData and Rest API’s, grabs the required data and maps these into the standard EDI format.  These EDI transactions are automatically sent directly to the trading partner.

Received EDI transactions are automatically translated and updated in D365 by ProcessOne 365

ProcessOne 365 supports the entire trading cycle.

• Received Purchase Orders are followed by PO Acknowledgements, Change Requests, Shipping Notices sent, Invoices generated and Adjustments acknowledged and reconciled.
• Sent Purchase Orders and Change Requests are generated, Shipping Notices and Invoices received and acknowledged and Adjustments transactions generated.

Everything is managed through the D365 EDI Transaction Inquiry Screen, where the business is set up and activity can be viewed in real time.

• Trading Partner Set-up: Trading partner profiles are also managed in D365, and errors can be easily reconciled anywhere in the process. This includes entering required EDI transaction types, ship-to addresses, AS2 connections, and company codes that link with D365.
• D365 EDI Transaction Inquiry: This provides complete visibility into all EDI transactions for each trading partner, including a search capability and history archive.
• Visibility – ProcessOne 365 displays all related EDI transactions on one screen. Search for an invoice number and in one click see all related POs, ASNs and 997s.  No exhaustive and timely research required.
• Mapping: ProcessOne 365 automatically maps the D365 data to the desired EDI transaction for transmission, as well as reversing this process to update D365 upon receipt of an EDI transaction from the trading partner.
• New product setup – All EDI products for each customer are displayed in a table format.  This allows fast and easy maintenance of product information.
• Error messages – rather than the usual error-message guessing game as to what is really wrong, ProcessOne 365 provides precise error messages allowing for fast resolution.
• Error Recovery – corrected transactions are re-started in one step from a single screen.

Electronic data interchange (EDI) is the concept of businesses electronically communicating information that was traditionally communicated on paper, such as purchase orders and invoices. Technical standards for EDI exist to facilitate parties transacting such instruments without having to make special arrangements.

EDI has existed at least since the early 70s, and there are many EDI standards (including X12, EDIFACT), some of which address the needs of specific industries or regions. It also refers specifically to a family of standards.

As more organizations connected to the Internet, eventually most or all EDI was pushed onto it. Initially, this was through ad hoc conventions, such as unencrypted FTP of ASCII text files to a certain folder on a certain host, permitted only from certain IP addresses.

As of 2002, Walmart has pushed AS2 for EDI. Because of its significant presence in the global supply chain, AS2 has become a commonly adopted approach for EDI.

Business-to-business (B2B or, in some countries, BtoB) is a situation where one business makes a commercial transaction with another.

B2B is often contrasted with business-to-consumer (B2C). In B2B commerce, it is often the case that the parties to the relationship have comparable negotiating power, and even when they do not, each party typically involves professional staff and legal counsel in the negotiation of terms, whereas B2C is shaped to a far greater degree by economic implications of information asymmetry.