PO number field length should go back to 20 characters

Posted by stan@retailtech on August 20, 2007, 1:26 pm

Please log in for more thread options

In previous RMS versions, PO number field length was 20 characters. With RMS
2.0, the field length shrunk to 15 characters for no apparent reason. I have
already had 1 customers who changed to 2.0 complain about that. They have
long PO numbers/Transfers numbers because the use descriptions in the
transfer numbers. Others usning 1.2 and 1.3 may also have done this. Plus
what happens to those long po numbers after conversion?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=a7ce09eb-197c-4e3e-81a1-888f223c82fa&dg=microsoft.public.pos

Posted by Ryan @ RITE on August 20, 2007, 1:49 pm

Please log in for more thread options

Stan,
I know this won't be much help but the underlying database has not been
changed. It still supports 20 characters in the PO Number. This must have
just been a UI change by Microsoft, though I have no idea why such a change
would have been made.

--
Thank you,

Ryan Sakry
Program Manager
Retail Information Technology Enterprises (RITE)
rsakry@rite.us
http://www.rite.us
320-230-2282 ext. 4002 (Office)
320-230-1796 (Fax)

> In previous RMS versions, PO number field length was 20 characters. With

> RMS

> 2.0, the field length shrunk to 15 characters for no apparent reason. I

> have

> already had 1 customers who changed to 2.0 complain about that. They have

> long PO numbers/Transfers numbers because the use descriptions in the

> transfer numbers. Others usning 1.2 and 1.3 may also have done this. Plus

> what happens to those long po numbers after conversion?

> ----------------

> This post is a suggestion for Microsoft, and Microsoft responds to the

> suggestions with the most votes. To vote for this suggestion, click the "I

> Agree" button in the message pane. If you do not see the button, follow

> this

> link to open the suggestion in the Microsoft Web-based Newsreader and then

> click "I Agree" in the message pane.

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=a7ce09eb-197c-4e3e-81a1-888f223c82fa&dg=microsoft.public.pos

Posted by stan@retailtech on August 20, 2007, 2:14 pm

Please log in for more thread options

Ryan,

Thanks for the reply. I didn't realize the data structure field length was
still the same just that the GUI field length didn't go past 15 now. I
assumed something chnaged in the data structure upgrade between versions 1.3
and 2.0. That means if MS wants to put it back it should be easier, I would
think. I don't know why that would be changed as well.

My customer just wants to be able to type long PO numbers into those fields
and cannot do what he used to be able to do.

Thanks

Stan

"Ryan @ RITE" wrote:

> Stan,

> I know this won't be much help but the underlying database has not been

> changed. It still supports 20 characters in the PO Number. This must have

> just been a UI change by Microsoft, though I have no idea why such a change

> would have been made.

> --

> Thank you,

> Ryan Sakry

> Program Manager

> Retail Information Technology Enterprises (RITE)

> rsakry@rite.us

> http://www.rite.us

> 320-230-2282 ext. 4002 (Office)

> 320-230-1796 (Fax)

> > In previous RMS versions, PO number field length was 20 characters. With

> > RMS

> > 2.0, the field length shrunk to 15 characters for no apparent reason. I

> > have

> > already had 1 customers who changed to 2.0 complain about that. They have

> > long PO numbers/Transfers numbers because the use descriptions in the

> > transfer numbers. Others usning 1.2 and 1.3 may also have done this. Plus

> > what happens to those long po numbers after conversion?

> >

> > ----------------

> > This post is a suggestion for Microsoft, and Microsoft responds to the

> > suggestions with the most votes. To vote for this suggestion, click the "I

> > Agree" button in the message pane. If you do not see the button, follow

> > this

> > link to open the suggestion in the Microsoft Web-based Newsreader and then

> > click "I Agree" in the message pane.

> >

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=a7ce09eb-197c-4e3e-81a1-888f223c82fa&dg=microsoft.public.pos

Posted by Ryan @ RITE on August 20, 2007, 3:21 pm

Please log in for more thread options

I know this may not be as strait forward as it was, but if there is any
field that the customer is not using, a SQL trigger could be created to fire
when that field is updated and copy that over to the PONumber field in the
database.

--
Thank you,

Ryan Sakry
Program Manager
Retail Information Technology Enterprises (RITE)
rsakry@rite.us
http://www.rite.us
320-230-2282 ext. 4002 (Office)
320-230-1796 (Fax)

> Ryan,

> Thanks for the reply. I didn't realize the data structure field length was

> still the same just that the GUI field length didn't go past 15 now. I

> assumed something chnaged in the data structure upgrade between versions

> 1.3

> and 2.0. That means if MS wants to put it back it should be easier, I

> would

> think. I don't know why that would be changed as well.

> My customer just wants to be able to type long PO numbers into those

> fields

> and cannot do what he used to be able to do.

> Thanks

> Stan

> "Ryan @ RITE" wrote:

>> Stan,

>> I know this won't be much help but the underlying database has not been

>> changed. It still supports 20 characters in the PO Number. This must

>> have

>> just been a UI change by Microsoft, though I have no idea why such a

>> change

>> would have been made.

>> --

>> Thank you,

>> Ryan Sakry

>> Program Manager

>> Retail Information Technology Enterprises (RITE)

>> rsakry@rite.us

>> http://www.rite.us

>> 320-230-2282 ext. 4002 (Office)

>> 320-230-1796 (Fax)

>> wrote

>> > In previous RMS versions, PO number field length was 20 characters.

>> > With

>> > RMS

>> > 2.0, the field length shrunk to 15 characters for no apparent reason. I

>> > have

>> > already had 1 customers who changed to 2.0 complain about that. They

>> > have

>> > long PO numbers/Transfers numbers because the use descriptions in the

>> > transfer numbers. Others usning 1.2 and 1.3 may also have done this.

>> > Plus

>> > what happens to those long po numbers after conversion?

>> >

>> > ----------------

>> > This post is a suggestion for Microsoft, and Microsoft responds to the

>> > suggestions with the most votes. To vote for this suggestion, click the

>> > "I

>> > Agree" button in the message pane. If you do not see the button, follow

>> > this

>> > link to open the suggestion in the Microsoft Web-based Newsreader and

>> > then

>> > click "I Agree" in the message pane.

>> >

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=a7ce09eb-197c-4e3e-81a1-888f223c82fa&dg=microsoft.public.pos

Posted by Ron Reyes on August 23, 2007, 12:32 am

Please log in for more thread options

This was an issue with HQ enviroments, The DB field is 20 char. but HQ adds a
chunk of #s to the front of inter-store transfers and PO#s larger than 14
chars. would 'hang" in HQ. The limit was introduced in 1.3r (thankfully for
me, this was a big headache)

Ideally the limit should be set when you configure HQ in store ops, but at
least for me it's finally there...

There's no way around this without going back to pre-1.3r manager as the
.exe is changed (don't have a clue how to undo that).
--
Total Communications

"Ryan @ RITE" wrote:

> I know this may not be as strait forward as it was, but if there is any

> field that the customer is not using, a SQL trigger could be created to fire

> when that field is updated and copy that over to the PONumber field in the

> database.

> --

> Thank you,

> Ryan Sakry

> Program Manager

> Retail Information Technology Enterprises (RITE)

> rsakry@rite.us

> http://www.rite.us

> 320-230-2282 ext. 4002 (Office)

> 320-230-1796 (Fax)

> > Ryan,

> >

> > Thanks for the reply. I didn't realize the data structure field length was

> > still the same just that the GUI field length didn't go past 15 now. I

> > assumed something chnaged in the data structure upgrade between versions

> > 1.3

> > and 2.0. That means if MS wants to put it back it should be easier, I

> > would

> > think. I don't know why that would be changed as well.

> >

> > My customer just wants to be able to type long PO numbers into those

> > fields

> > and cannot do what he used to be able to do.

> >

> > Thanks

> >

> > Stan

> >

> > "Ryan @ RITE" wrote:

> >

> >> Stan,

> >> I know this won't be much help but the underlying database has not been

> >> changed. It still supports 20 characters in the PO Number. This must

> >> have

> >> just been a UI change by Microsoft, though I have no idea why such a

> >> change

> >> would have been made.

> >>

> >> --

> >> Thank you,

> >>

> >> Ryan Sakry

> >> Program Manager

> >> Retail Information Technology Enterprises (RITE)

> >> rsakry@rite.us

> >> http://www.rite.us

> >> 320-230-2282 ext. 4002 (Office)

> >> 320-230-1796 (Fax)

> >> wrote

> >> > In previous RMS versions, PO number field length was 20 characters.

> >> > With

> >> > RMS

> >> > 2.0, the field length shrunk to 15 characters for no apparent reason. I

> >> > have

> >> > already had 1 customers who changed to 2.0 complain about that. They

> >> > have

> >> > long PO numbers/Transfers numbers because the use descriptions in the

> >> > transfer numbers. Others usning 1.2 and 1.3 may also have done this.

> >> > Plus

> >> > what happens to those long po numbers after conversion?

> >> >

> >> > ----------------

> >> > This post is a suggestion for Microsoft, and Microsoft responds to the

> >> > suggestions with the most votes. To vote for this suggestion, click the

> >> > "I

> >> > Agree" button in the message pane. If you do not see the button, follow

> >> > this

> >> > link to open the suggestion in the Microsoft Web-based Newsreader and

> >> > then

> >> > click "I Agree" in the message pane.

> >> >

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=a7ce09eb-197c-4e3e-81a1-888f223c82fa&dg=microsoft.public.pos

> >>