1. Home
  2. Point-Of-Sale Software
  3. Purchase Order Create Error

Purchase Order Create Error

I am using Store Operations Manager version 1.2.0154 on Windows XP Professional with Service Pack 2 and all posted hot-fixes. When creating a new Purchase Order, I am selecting: 1) Generate based on re-order information 2) Only items in the selected departments (and selecting one department) 3) Order from the primary supplier And then I click on OK. I am then receiving an error message:

Store Operations Business Rules Error #-2147217833 The statement has been terminated. (Source: Microsoft OLE DB Provider for SQL Server) (SQL State: 01000) (NativeError: 3621) No Help file available

SELECT ItemID, SUM(CASE POType WHEN 0 THEN QuantityOrdered - QuantityReceivedToDate WHEN 1 THEN QuantityOrdered - QuantityReceivedToDate WHEN 2 THEN QuantityOrdered - QuantityReceivedToDate WHEN 3 THEN -QuantityOrdered + QuantityReceivedToDate WHEN 4 THEN QuantityOrdered - QuantityReceivedToDate WHEN 5 THEN -QuantityOrdered + QuantityReceivedToDate END) As OnOrder INTO ##TempQuantity FROM PurchaseOrderEntry INNER JOIN PurchaseOrder ON PurchaseOrder.ID PurchaseOrderEntry.PurchaseOrderID WHERE (PurchaseOrder.Status 2) AND (QuantityReceivedToDate < QuantityOrdered) GROUP BY ItemID UPDATE ##TempOrder SET QuantityOrdered CASE WHEN Item.Quantity - Item.QuantityCommitted

Reply to
Ted Archer
Loading thread data ...

Ted,

Before you go too much further, I would update to the latest version as you are about 40 versions behind. 1.2 topped out at 1.2.189 and 1.3 is now at .1003

Reply to
Jeff

Jeff:

I have been using this combination for two years without this error. It worked last Monday, but not on Wednesday. This error has a message id, so there must be an event that this error message was coded to address. I am looking for an explanation of the error and a process for its resolution.

But thanks for your suggestion.

Ted Archer Fairvilla Megastore snipped-for-privacy@fairvilla.com

formatting link

Reply to
Ted Archer

Ted,

Issue

"Run-time error '-2147217833 (80040e57)': String or binary data would be truncated" occurs while creating a Purchase Order in QuickSell Commerce.

Potential Cause

This is caused by one of the fields for an item having an invalid length.The Description and ItemLookUpCode could be the cause of this error if the data was imported into QuickSell Commerce.

The fix is included in the article;

formatting link
Must have access to CustomerSource.

Reply to
Jeff

Jeff,

Thanks for the link. There have been no items added to the database since the last time a PO was created for this department, however, I ran the queries listed in the KB article. There are no items with a Description that is greater than 30 characters or an ItemLookupCode greater than 25 characters. Nor are there any ReorderNumber entries in the SupplierList table that are greater than 17 characters. And I still can't create a PO for this one Department.

Would you have any other thoughts or suggestions?

Ted Archer Fairvilla Megastore snipped-for-privacy@fairvilla.com

formatting link

Reply to
Ted Archer

Make sure there are no strange punctuation marks like a ' or a " in the relevant fields you are querying. RMS has rock bottom ability to handle this type of stuff. (I found out the hard way!)

Reply to
dan

On Friday, I flew to my store where I'm having this problem and upgraded the store to version 1.3R (1.3.1002). It still will not issue a PO for one of my departments. This feature was working, and then stopped. This is a big problem for me since we use JIT purchasing for our stores, with no backstock, and I'm now one cycle behind for this department (we normally order twice a week). Any suggestions would be welcome.

Ted Archer Fairvilla Megastore snipped-for-privacy@fairvilla.com

formatting link

Reply to
Ted Archer

Ted,

I guess a call to MS or your local reseller would be your next step as something is really screwy.

Reply to
Jeff

Jeff:

After the upgrade to 1.3, I tried to create a PO by selecting the Category option instead of the Department, there are seven Categories in this particular Department. After I selected the seven Categories, I received the same error. I then tried using fewer categories (my initial thought was to try to isolate the Category with the misbehaving item), and found that if I selected two categories, the process would run. However, if I selected three or more Categories, the process would fail.

Since the process runs on the individual Categories, I don't see haw there could possibly be a problem with data entry of the items. Maybe someone from Microsoft will follow this problem and offer a solution. If not I guess I'll have to call and open an incident directly, as opposed to a posting here.

Ted Archer Fairvilla Megastore snipped-for-privacy@fairvilla.com

formatting link

Reply to
Ted Archer

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.