COOPERATIVE SUPPLY AND DISTRIBUTION CHAIN PROCESSING
A ledger associated with a Purchase Order (PO) is maintained in a private blockchain among entities associated with the PO. An Application Programming Interface (API) is provided to hash and store ledger entries, ledger accesses, and/or documents associated with the PO. An interface is provided that uses the API to obtain the ledger, selective entries of the ledger, the PO, selective portions of the PO, ledger accesses, and/or selective documents associated with the PO from the private blockchain.
1 . A method, comprising:
receiving an indication that a purchase order (PO) was created by an entity within a workflow of a system for the entity; and
providing an Application Programming Interface (API) call to process on an entity device that creates a ledger associated with the entity and the PO within a private blockchain (BC) cooperatively maintained by the entity and other entities.
2 . The method of claim 1 , wherein receiving further includes receiving the indication from an agent of the entity device, wherein the agent was called from the workflow after creation of the PO or that was monitoring the workflow for creation of the PO.
3 . The method of claim 1 , wherein receiving further includes receiving the indication from a workflow call made within the workflow after creation of the PO by the system.
4 . The method of claim 1 , wherein receiving further includes receiving the PO with the indication.
5 . The method of claim 4 , wherein providing further includes creating a key for the PO.
6 . The method of claim 5 , wherein creating further includes providing the key with the API call for use when creating the ledger within the private blockchain.
7 . The method of claim 6 , wherein providing the key further includes providing a hash algorithm for hashing the key with the API call and the key into the private blockchain by the entity and the other entities.
8 . The method of claim 1 further comprising:
receiving an event raised from the workflow indicating the PO was sent to a second entity for approval by the second entity; and
providing a second API call to process on the entity device that creates a ledger entry within the ledger on the private blockchain for the event.
9 . The method of claim 8 further comprising:
receiving an event raised from a second workflow of a second entity device for the second entity indicating that terms associated with the PO were accepted by the second entity; and
providing a third API call to process on the second entity device that creates a second ledger entry within the ledger on the private blockchain for the second event.
10 . The method of claim 9 further comprising:
receiving other events raised by the workflow or the second workflow indicating additional entries are necessary within the ledger; and
providing additional API calls for the other events to process on the entity device or the second entity device that creates the additional entries on the private blockchain for the other events.
11 . The method of claim 1 further comprising:
receiving a second request to retrieve the ledger or to retrieve selective ledger entries from the entity device; and
initiating an operation against the private blockchain to retrieve the ledger or the selective ledger entries.
12 . The method of claim 11 further comprising. assembling blocks of information returned from the entity device associated with the entity and returned from other entity device associated with the other entities based on the operation into the ledger or the selective ledger entries; and
providing the ledger or the selective ledger entries to the entity device.
13 . A method, comprising:
monitoring a workflow of a system for an entity for creation of a Purchase Order (PO);
obtaining keys for the entity and the PO;
obtaining an Application Programming Interface (API) call to create a ledger for the PO, make an entry within the ledger for creation of the PO, and store the PO within a private blockchain maintained by the entity and other entities;
processing the API call with the keys to create the ledger, make the entry, and store the PO within the private blockchain.
14 . The method of claim 13 , wherein obtaining the keys further includes generating a PO key for the PO based by hashing data of the PO.
15 . The method of claim 13 , wherein obtaining the API call further includes obtaining a hashing algorithm with the API call for hashing the keys into the private blockchain.
16 . The method of claim 13 further comprising:
continually monitoring the workflow of the system for events indicating that additional entries are necessary within the ledger based on the events;
obtaining the keys and other keys necessary for the additional entries;
obtaining second API calls to store the additional entries and information associated with the additional entries within the private blockchain; and
process the second API calls using the keys and the other keys to create the additional entries within the ledger with the information.
17 . The method of claim 13 further comprising:
providing a user-facing interface to an entity device associated with the entity;
receiving a query provided through the user-facing interface for retrieving the ledger, selective entries of the ledger, or documents associated with the PO;
obtaining query keys associated with the query;
obtaining a second API call for initiating the query on the private blockchain; and
processing the second API call with the query keys to obtain blocks of data associated with query results for the query returned from the private blockchain.
18 . The method of claim 17 further comprising:
assembling the blocks of data into the ledger, the selective entries of the ledger, or the documents associated with the query results; and
providing through the user-facing interface the ledger, the selective entries of the ledger, or the documents to the entity device.
19 . A system, comprising:
a first server comprising a processor and a non-transitory computer-readable storage medium;
the non-transitory computer-readable storage medium comprises executable instructions;
a plurality of entity servers comprising entity devices; and
the executable instructions when executed by the processor from the non-transitory computer-readable storage medium cause the processor to perform operations comprising:
providing Application Programming Interface (API) calls to the entity devices that when processed by the entity devices create, maintain, and retrieve ledgers associated with Purchase Orders (POs), entries within the ledgers, and documents associated with the POs from a private blockchain that is maintained by the entity devices.
20 . The system of claim 19 , wherein the first server is associated with a cloud processing environment, and wherein the executable instructions is a cloud-based service for maintaining and managing the private blockchain.