Microsoft Dynamics RMS (Archived)

Automatic PO Number generation causes Error

(0) Share

Report

Posted on by Community Member Microsoft Employee

Howdy,

When I commit a partially received PO, RMS gives the option of creating a New PO with the backordered items.

When I try to do this The system crashes and fails to generate the new PO

The error message indicates that the data is not in an INT format and it cant increment the #.

WE have used alphabetic characters in the PO # field in the past, and This seems to be causing the problem.

Is there any way to reset the # that RMS is using for automatically generating PO #''s

thanks

Jon

*This post is locked for comments

All responses (6)

Answers (1)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Automatic PO Number generation causes Error

this is on store database right??
Community Member Microsoft Employee on at

Like (0)

Report

RE: Automatic PO Number generation causes Error

Muchas Gracias Heidi,

That worked great.

I marked it as answered.

I need to learn some SQL

cheers

jk
Verified answer

Community Member Microsoft Employee on at

Like (0)

Report

RE: Automatic PO Number generation causes Error

Hi Jon,

Sorry correction.... I typed OldPO in a place I should have typed NewPO

-- Begin Query --

DECLARE @NewPO NVARCHAR(20), @OldPO NVARCHAR(20)

SET @NewPO = 'NewPONumberHere'

SET @OldPO = 'OldPONumberHere'

UPDATE PurchaseOrder SET PONumber = @NewPO WHERE PONumber = @OldPO

AND @NewPO NOT IN (SELECT PONumber FROM PurchaseOrder)

-- End Query --
Community Member Microsoft Employee on at

Like (0)

Report

RE: Automatic PO Number generation causes Error

Of course - just edit the second and third lines to indicate the new PO # you want to use and the old (bad) PO #. Keep the PO #s in apostrophes.

-- Begin Query --

DECLARE @NewPO NVARCHAR(20), @OldPO NVARCHAR(20)

SET @NewPO = 'NewPONumberHere'

SET @OldPO = 'OldPONumberHere'

UPDATE PurchaseOrder SET PONumber = @NewPO WHERE PONumber = @OldPO

AND @OldPO NOT IN (SELECT PONumber FROM PurchaseOrder)

-- End Query --
Community Member Microsoft Employee on at

Like (0)

Report

RE: Automatic PO Number generation causes Error

Thanks for replying Heidi,

There is a PO in our system that has this #. It is OLD from 2006.

Unfortunately the PO# is grayed out and is not editable.

I think I need a SQL statement to reset that PONumber.

any help appreciated

jon
Community Member Microsoft Employee on at

Like (0)

Report

RE: Automatic PO Number generation causes Error

Hi Jon,

The only way to reset the PO # that RMS is using is to either change the problematic PO # to something RMS will accept, or manually type in a PO # that is higher that the problematic PO # and then RMS will use that as the starting point for the next PO.

Good luck!