Перейти к содержимому

AI Wrote a Prophet 21 Purchase Order. The One Field It Must Never Send.

Mike Cali

0:00 / 0:00

AI Wrote a Prophet 21 Purchase Order. The One Field It Must Never Send.

0 просмотров · 1 дн. назад
Mike Cali
10 подписчиков
0 просмотров · 1 дн. назад
Why "Column is disabled: supplier_id" kills your P21 PO import, and the field to send instead. One Telegram message to Ginger, my MeshHand assistant, on my Prophet 21 test company: "make a PO for 10 MESH-DEMO-18 from Big Bell." She raises a real purchase order through the P21 Transaction API, ONE call to the Purchase Order Entry window with a header and one line, and P21 numbers the PO. Then we check her work in Purchase Order Entry. Plus the three lessons we learned the hard way: send vendor_id and let P21 fill the supplier (send supplier_id and P21 says "Column is disabled"), the buyer is required on this install, and a new item's first PO line comes in at a price of zero unless you send the supplier cost. This is the full power that you can give to Ginger, but initially we start her off with read-only access. Every skill she has is one we gave her on purpose. Talk to us: https://meshconnector.com/start.html?... 0:00 Remember this PO number 0:20 "Column is disabled: supplier_id" 1:01 MeshHand, and the read-only disclaimer 2:57 Step two of the chain: buy ten 3:19 The rule: reads by OData, writes through the P21 API 3:43 How I talk to Ginger 4:19 The ask: make a PO 5:10 Her answer: PO 4000043, read back 6:26 How she did it: one call to Purchase Order Entry 6:57 The one field: supplier_id 8:09 Lesson two: the buyer 8:55 Lesson three: price zero on a new item 9:30 Checking her work in Purchase Order Entry 10:42 The first try made things up 11:29 The Planner card 13:35 The one number to count 13:54 Close About me: I work full time as IT Manager at Belmont. This series and Mesh Connector are made on my own time, evenings and weekends. #Prophet21 #Epicor #WholesaleDistribution