Many customers run DSI dcLink with JD Edwards (JDE) for scanning integration in supply chain processes such as quality control, goods receipt, and goods issue because these processes are much more efficient with scanning integration. DSI dcLink integrates with scanners with custom developed scripts. When upgrading DSI for use with JD Edwards, there are three challenges: first, DSI has changed the scripting language for the integration processes; second, DSI has changed from XML to Rest-based calls; and third, DSI continually removes support for scanners.
Upgrades to DSI Scripts and FastForm
As mentioned above, DSI continues to change their scripting language. While it’s normal for scripting languages to evolve and grow over time; DSI’s changes have proven to be especially radical. In their latest release, DSI is now using a new scripting language called FastForm, which provides new features for modern scanners. The downside here is that these changes require customers to rewrite all their DSI integration scripts to the FastForm language.
Updating the scripting language is almost always done by a DSI consultant as part of a consulting services contract. The language is proprietary and DSI has much more documentation and internal resources that need to be explored. The DSI consultant will rewrite the script in the new language, and the customer will then have to unit test the script. When you perform the unit test, you will undoubtedly find defects and bugs. These defects will then have to be resolved by the DSI consultant.
Switching DSI to use REST calls
There are multiple ways to encode data into a structured format and call web services using that structured data. Historically, JD Edwards and DSI have integrated using an XML-based structure for integration calls, but many modern applications are using JSON, which is a simpler and less structured format as part of a REST call that looks like many modern HTTP applications. While data representation and web service calling standards are important, DSI has changed from XML to JSON/REST in recent versions. This change also requires rewrites of many DSI scripts during a DSI upgrade.
The changeover from XML to JSON and REST is requiring many DSI scripts to be rewritten because XML is formed using tags and properties like HMTL documents use. Similar to the changeover to FastForm, changing the calling convention requires engaging with DSI consultants to rewrite the scripts. Significant testing is also required for this changeover.
Changing Scanners
Naturally, scanners are a core component of any scanning solution; and as technology ages, scanners inevitably fall out of support. DSI frequently changes the scanners they support, so it’s likely that upgrading DSI versions will result in a need to update to new scanners as well. This is an expensive and complicated effort, requiring significant investment and testing. DSI dcLink customers will need to be on top of what scanners are supported as they head into any DSI scanning solution upgrade.
Update or Switch?
To update or switch your scanning solution is the question many DSI customers are facing today. With ERP Suites Scanability, JD Edwards users can have a modern, orchestration-based scanning solution at a low cost of ownership. By using Orchestrator, maintenance and updates are much easier, which saves time and money for everyone involved.
David Schenz
David Schenz is a leader in building teams that deliver complex business systems transformations and roll-outs. With nearly ten years SAP experience, he offers deep knowledge of retail accounting processes, insurance accounting, and retail business strategies. As Director at ERP Suites, David guides employees toward a common goal of helping customers achieve optimal success.
