Jarvis Pizzeria: EAN / GTIN code validation in DMN Service by Marcel van de Glind

In this blog we describe the implementation of an EAN / GTIN code validator in een Decision Model Service.

As a Pizzeria that wants to treat the customer like a king, we think it is very important that we can always serve the customer with our full range of pizzas.

For this it is necessary that we have a good stock management policy. Every pizza we make must be processed accurately in the system. To simplify this processing, we provide each pizza box with an EAN barcode that needs to be scanned for stock management.

In this blog we describe a Decision Model that can be used to validate the scanned / entered EAN codes.

The purpose of this blog is to demonstrate that it is fairly easy to implement such an algorithm in a Decision Model.

What is EAN / GTIN?

From wikipedia: EAN also known as European Article Number or EAN) is a standard describing a barcode symbology and numbering system used in global trade to identify a specific retail product type, in a specific packaging configuration, from a specific manufacturer. The standard has been subsumed in the Global Trade Item Number standard from the GS1 organization; the same numbers can be referred to as GTINs and can be encoded in other barcode symbologies defined by GS1.

The most commonly used EAN standard is the thirteen-digit EAN-13.

And from the https://www.gs1.org/ website.

The last digit of all fixed-length, numeric GS1 Identification Keys is a check digit that ensures the integrity of the key. The check digit is calculated using a simple algorithm, based on the other numbers in the key. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress