Understanding the ediBlockChain example

The example identifies three EDI participants and three non-EDI participants. Each participant adds blocks to the order change by issuing requests to a block chain service. Execution begins with the Buyer having a json order which initiates EDI processes with the supplier. Next the supplier initiates EDI processes with the carrier and buyer. Last, the carrier books trucks for delivery to the buyer.

Each participant folder in the example contains maps for execution with a top-level map beginning with “a". The top-level maps contain the specific calls to the block chain service and shows document flows and execution order on the last output card with the name (mapControl).

The buyer creates an EDI ORDER, creates block chain order, adds participants for access to the chain and edi reference information as a block in the chain. The EDI ORDER contains block chain information in the RFF segment:

RFF+CBB:orderChain^12857654123450000134012345500004'

The supplier receives the EDI ORDER, creates an EDI ORDRESP, supplies the items in the order, initiates shipping via EDI IFTMBF (Carrier Booking), adds participants for access to the chain and edi reference information as a block in the chain. The EDI ORDRESP and EDI IFTMBF contains block chain information in the RFF segment:

RFF+CBB:orderChain^12857654123450000134012345500004'

The carrier receives the EDI IFTMBF, creates EDI IFTMBC (Carrier Booking Confirmation), adds participants for access to the chain and edi reference information as a block in the chain. The carrier adds non-EDI participants as Trucks and each truck will add temperature readings on the shipped items to the block chain.

Each participant will use a predefined control block interface and document definitions and call the block chain service map. The control block identifies the type of call being made and contains information for the block chain service map to process the request and add a block to the chain.