Minimum Version Required: 24.09
Steps
Step 1: Purchase Creation
Purchase is created in Encompass with a vendor with the following requirements:
Vendor Trading Partner = “CONA Blockchain”
Vendor License = CONA To Entity Code
Vendor Plant Code = CONA Ship From
Step 2: Update Shipment to Ordered Status
Export_CONABlockchain_Purchases will send PO information to validate the PO with CONA. to Create Purchase Order
If ok:
Exchange Task status will be Successfully Sent
We will get back a TransactionPayload and will
We will send another request with the TransactionPayload
Purchase EDI Status update to Purchase Order Sent
So, it is normal to see two exchange tasks for a purchase that have been Successfully Sent
If failed:
Exchange Task status will be Warning.
Purchase EDI Status update to Purchase Order Failed.
Common Failures or Warnings:
Product Setup - This has usually been caused by a product configuration with an incorrect Supplier Product Num or Case UPC. Odom will need to confirm the Supplier Product Num and Case UPC is correct OR CONA will need to fix the product on their end. Once the product is fixed, users will need to set the EDI Status back to Not Yet Transmitted and can run Export_CONABlockchain_Purchases.
Purchase Order Not Found - This happens when we send the purchase receive confirmation. This happens because a PO was created and received before Export_CONABlockchain_Purchases. Odom is aware this is not the expected workflow.
Step 3: Import_CONABlockchain_Purchases (automated)
This will update the PO by possible adjusting quantities, adding dunnage product, setting pallet tag, code dates, memo (Carrier), and trailer num
Uses Import Routine 558138 - CONA Blockchain (PurchaseOrders EDBL)
Comments:
Multiple exchange tasks will be created
All updates will not happen at once. Dunnage product may get added first. Perhaps days later, when the product is picked at the CONA facility, pallet tag, code dates, memo (Carrier), and trailer number will be updated.
Step 4: Purchase is shipped and received by Odom
Once the shipment is received by Odom, Export_CONABlockchain_Purchases_GR_GI will send the PO to CONA Blockchain (GR - Goods Received or GI - Goods Issued)
GR - Goods Received (BUYS). Positive purchases
GI - Goods Issued (RETURNS) Negative purchases
CONA Blockchain Dashboard
CONA Blockchain - used to monitor, has link to scheduled tasks to resend, and link to the CONA Blockchain Alert
Best Practices
BUYS: Only positive units should be put on a purchase order. Enter +/- num units will not be accepted by CONA
RETURNS: Only negative units. Usually for dunnage but can also be finished goods
Ensure PO is sent before receiving. This will result in a Purchase Order Not Found warning.