This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Increase the length of recordkey field in work view object and try
Sent from my Samsung device
-------- Original message --------
From: "'InComm Solutions Inc.' incomm@shaw.ca [MAXIMO]" <MAXIMO@yahoogroups.com>
Date: 17/11/2015 1:29 am (GMT+03:00)
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Maximo 7.6 change lenght of wonum
I second that ... you could also do
Select * from maxattribute where attributename in (‘REFWO’,’WONUM’) and check the length of those fields – that might work.
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, November 16, 2015 10:21 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Maximo 7.6 change lenght of wonum
It sounds as though there is a field that WONUM is being copied too that is
still too small, i.e. its "same as" data was incorrect and therefore did
not get increased in size automatically. It is likely a result of a
customization, an industry solution, a crossover or similar. There's no
simple way to find it, my first point of attack would be to crank up the
debugging ans see if the logs give you any insight.
Chris.
On Wed, Nov 11, 2015 at 1:06 PM, 'Petra Kellers' pk@jostwerner.de [MAXIMO] <
MAXIMO@yahoogroups.com> wrote:
>
>
> Hello,
>
> how can I change the length of wonum in Maximo 7.6.
>
> I have changed the length of the attribute wonum in the object workorder
> from 10 to 25 .
>
> But if I make a new order in workorder tracking, I get the error BMXAA4049E
> - The value specified CXPK123456789 exceeds the maximum field length. Enter
> a value that fits into the length of this attribute.
>
> Field: Workorder
>
> Table.Column: Workorder.Wonum
>
> What can I do?
>
>
>
>
>
Hi all,
I have some problem that i cannot fill in followup work in Workorder
module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits into
the length of this attribute."
This was happended during amend workorder.wonum to UPPER(25) but supposed
this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This was
solved more than 3 years ago.
rgrd,
yudi
"daisonck daisonck@yahoo.com [MAXIMO]" <MAXIMO@yahoogroups.com>
Sent by: MAXIMO@yahoogroups.com
17-11-2015 11:30
Please respond to
MAXIMO@yahoogroups.com
To
MAXIMO@yahoogroups.com
cc
Subject
RE: [MAXIMO List] Maximo 7.6 change lenght of wonum
Increase the length of recordkey field in work view object and try
Sent from my Samsung device
-------- Original message --------
From: "'InComm Solutions Inc.' incomm@shaw.ca [MAXIMO]"
<MAXIMO@yahoogroups.com>
Date: 17/11/2015 1:29 am (GMT+03:00)
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Maximo 7.6 change lenght of wonum
I second that ... you could also do
Select * from maxattribute where attributename in (‘REFWO’,’WONUM’) and
check the length of those fields – that might work.
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, November 16, 2015 10:21 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Maximo 7.6 change lenght of wonum
It sounds as though there is a field that WONUM is being copied too that
is
still too small, i.e. its "same as" data was incorrect and therefore did
not get increased in size automatically. It is likely a result of a
customization, an industry solution, a crossover or similar. There's no
simple way to find it, my first point of attack would be to crank up the
debugging ans see if the logs give you any insight.
Chris.
On Wed, Nov 11, 2015 at 1:06 PM, 'Petra Kellers' pk@jostwerner.de [MAXIMO]
<
MAXIMO@yahoogroups.com> wrote:
>
>
> Hello,
>
> how can I change the length of wonum in Maximo 7.6.
>
> I have changed the length of the attribute wonum in the object workorder
> from 10 to 25 .
>
> But if I make a new order in workorder tracking, I get the error
BMXAA4049E
> - The value specified CXPK123456789 exceeds the maximum field length.
Enter
> a value that fits into the length of this attribute.
>
> Field: Workorder
>
> Table.Column: Workorder.Wonum
>
> What can I do?
>
>
>
>
>
Well, you can check the base table columns first; then check the mattribute and attributecfg columns. If you verify (or modify) those for UPPER(25), you should be good. For sure, if it bombs on insert/update, and SQL logging is set to INFO, you'll see the problem table.
---In MAXIMO@yahoogroups.com, <yudi.irianto@ytljt.com> wrote :
Hi all,
I have some problem that i cannot fill in followup work in Workorder
module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits into
the length of this attribute."
This was happended during amend workorder.wonum to UPPER(25) but supposed
this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This was
solved more than 3 years ago.
rgrd,
yudi
Did you read this article? "Increasing length of WONUM or TICKETID causes
BMXAA4049E error"
http://www-01.ibm.com/support/docview.wss?uid=swg21396141
On Fri, Dec 4, 2015 at 12:01 PM, maximal@wanko.com [MAXIMO] <
MAXIMO@yahoogroups.com> wrote:
>
>
> Well, you can check the base table columns first; then check the
> mattribute and attributecfg columns. If you verify (or modify) those for
> UPPER(25), you should be good. For sure, if it bombs on insert/update, and
> SQL logging is set to INFO, you'll see the problem table.
>
>
> ---In MAXIMO@yahoogroups.com, <yudi.irianto@ytljt.com> wrote :
>
> Hi all,
>
> I have some problem that i cannot fill in followup work in Workorder
> module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
> XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits into
> the length of this attribute."
>
> This was happended during amend workorder.wonum to UPPER(25) but supposed
> this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
> RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This was
> solved more than 3 years ago.
>
> rgrd,
> yudi
>
>
>
>
>
>
>
>
I sure didn't. I can't find a goddamn thing on the IBM site anymore. I'm pretty sure it's Scotty Peluso's fault.
---In MAXIMO@yahoogroups.com, <lawlessc@gmail.com> wrote :
Did you read this article? "Increasing length of WONUM or TICKETID causes
BMXAA4049E error"
http://www-01.ibm.com/support/docview.wss?uid=swg21396141 http://www-01.ibm.com/support/docview.wss?uid=swg21396141
On Fri, Dec 4, 2015 at 12:01 PM, maximal@wanko.com mailto:maximal@wanko.com [MAXIMO] <
MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com> wrote:
>
>
> Well, you can check the base table columns first; then check the
> mattribute and attributecfg columns. If you verify (or modify) those for
> UPPER(25), you should be good. For sure, if it bombs on insert/update, and
> SQL logging is set to INFO, you'll see the problem table.
>
>
> ---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com> wrote :
>
> Hi all,
>
> I have some problem that i cannot fill in followup work in Workorder
> module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
> XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits into
> the length of this attribute."
>
> This was happended during amend workorder.wonum to UPPER(25) but supposed
> this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
> RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This was
> solved more than 3 years ago.
>
> rgrd,
> yudi
>
>
>
>
>
>
>
>
I'm never going to argue against blaming Scott (especially as he's probably
reading this but can't reply!) but this is just for you Chris... ;-)
http://bfy.tw/37ho
On Fri, Dec 4, 2015 at 2:30 PM, maximal@wanko.com [MAXIMO] <
MAXIMO@yahoogroups.com> wrote:
>
>
> I sure didn't. I can't find a goddamn thing on the IBM site anymore. I'm
> pretty sure it's Scotty Peluso's fault.
>
>
> ---In MAXIMO@yahoogroups.com, <lawlessc@gmail.com> wrote :
>
> Did you read this article? "Increasing length of WONUM or TICKETID causes
> BMXAA4049E error"
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141
>
>
> On Fri, Dec 4, 2015 at 12:01 PM, maximal@wanko.com mailto:
> maximal@wanko.com [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com> wrote:
>
> >
> >
> > Well, you can check the base table columns first; then check the
> > mattribute and attributecfg columns. If you verify (or modify) those for
> > UPPER(25), you should be good. For sure, if it bombs on insert/update,
> and
> > SQL logging is set to INFO, you'll see the problem table.
> >
> >
> > ---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <
> yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com> wrote :
> >
> > Hi all,
> >
> > I have some problem that i cannot fill in followup work in Workorder
> > module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
> > XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits
> into
> > the length of this attribute."
> >
> > This was happended during amend workorder.wonum to UPPER(25) but
> supposed
> > this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
> > RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This
> was
> > solved more than 3 years ago.
> >
> > rgrd,
> > yudi
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>
Lolol ...
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Friday, December 4, 2015 11:33 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Maximo 7.6 change lenght of wonum
I'm never going to argue against blaming Scott (especially as he's probably
reading this but can't reply!) but this is just for you Chris... ;-)
http://bfy.tw/37ho
On Fri, Dec 4, 2015 at 2:30 PM, maximal@wanko.com [MAXIMO] <
MAXIMO@yahoogroups.com> wrote:
>
>
> I sure didn't. I can't find a goddamn thing on the IBM site anymore. I'm
> pretty sure it's Scotty Peluso's fault.
>
>
> ---In MAXIMO@yahoogroups.com, <lawlessc@gmail.com> wrote :
>
> Did you read this article? "Increasing length of WONUM or TICKETID causes
> BMXAA4049E error"
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141
>
>
> On Fri, Dec 4, 2015 at 12:01 PM, maximal@wanko.com mailto:
> maximal@wanko.com [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com> wrote:
>
> >
> >
> > Well, you can check the base table columns first; then check the
> > mattribute and attributecfg columns. If you verify (or modify) those for
> > UPPER(25), you should be good. For sure, if it bombs on insert/update,
> and
> > SQL logging is set to INFO, you'll see the problem table.
> >
> >
> > ---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <
> yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com> wrote :
> >
> > Hi all,
> >
> > I have some problem that i cannot fill in followup work in Workorder
> > module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
> > XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits
> into
> > the length of this attribute."
> >
> > This was happended during amend workorder.wonum to UPPER(25) but
> supposed
> > this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
> > RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This
> was
> > solved more than 3 years ago.
> >
> > rgrd,
> > yudi
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>
I don't know why that's for me, I can change field lengths just fine! But I'll admit that's a good one.
And I actually do Google the sh!t out of things but it's always a crapshoot if a particular IBM article is online today... and don't say that's never happened.
-C
From: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com]
Sent: Friday, December 4, 2015 11:33 AM
To: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Maximo 7.6 change lenght of wonum
I'm never going to argue against blaming Scott (especially as he's probably
reading this but can't reply!) but this is just for you Chris... ;-)
http://bfy.tw/37ho http://bfy.tw/37ho
On Fri, Dec 4, 2015 at 2:30 PM, maximal@wanko.com mailto:maximal@wanko.com [MAXIMO] <
MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com> wrote:
>
>
> I sure didn't. I can't find a goddamn thing on the IBM site anymore. I'm
> pretty sure it's Scotty Peluso's fault.
>
>
> ---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <lawlessc@gmail.com mailto:lawlessc@gmail.com> wrote :
>
> Did you read this article? "Increasing length of WONUM or TICKETID causes
> BMXAA4049E error"
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141 http://www-01.ibm.com/support/docview.wss?uid=swg21396141
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141 http://www-01.ibm.com/support/docview.wss?uid=swg21396141
>
>
> On Fri, Dec 4, 2015 at 12:01 PM, maximal@wanko.com mailto:maximal@wanko.com mailto:
> maximal@wanko.com mailto:maximal@wanko.com [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com> wrote:
>
> >
> >
> > Well, you can check the base table columns first; then check the
> > mattribute and attributecfg columns. If you verify (or modify) those for
> > UPPER(25), you should be good. For sure, if it bombs on insert/update,
> and
> > SQL logging is set to INFO, you'll see the problem table.
> >
> >
> > ---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <
> yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com> wrote :
> >
> > Hi all,
> >
> > I have some problem that i cannot fill in followup work in Workorder
> > module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
> > XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits
> into
> > the length of this attribute."
> >
> > This was happended during amend workorder.wonum to UPPER(25) but
> supposed
> > this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
> > RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This
> was
> > solved more than 3 years ago.
> >
> > rgrd,
> > yudi
> >
OK - I have to agree on that one. Sometimes I find a KB article via Google,
sometimes I don't ...
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, December 7, 2015 5:03 AM
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Maximo 7.6 change lenght of wonum
I don't know why that's for me, I can change field lengths just fine! But
I'll admit that's a good one.
And I actually do Google the sh!t out of things but it's always a crapshoot
if a particular IBM article is online today... and don't say that's never
happened.
-C
From: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
[mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
<mailto:MAXIMO@yahoogroups.com%20mailto:MAXIMO@yahoogroups.com> ]
Sent: Friday, December 4, 2015 11:33 AM
To: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Maximo 7.6 change lenght of wonum
I'm never going to argue against blaming Scott (especially as he's probably
reading this but can't reply!) but this is just for you Chris... ;-)
http://bfy.tw/37ho http://bfy.tw/37ho
On Fri, Dec 4, 2015 at 2:30 PM, maximal@wanko.com mailto:maximal@wanko.com
[MAXIMO] <
MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com> wrote:
>
>
> I sure didn't. I can't find a goddamn thing on the IBM site anymore. I'm
> pretty sure it's Scotty Peluso's fault.
>
>
> ---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com,
<lawlessc@gmail.com mailto:lawlessc@gmail.com
<mailto:lawlessc@gmail.com%20mailto:lawlessc@gmail.com> > wrote :
>
> Did you read this article? "Increasing length of WONUM or TICKETID causes
> BMXAA4049E error"
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141
http://www-01.ibm.com/support/docview.wss?uid=swg21396141
> http://www-01.ibm.com/support/docview.wss?uid=swg21396141
http://www-01.ibm.com/support/docview.wss?uid=swg21396141
>
>
> On Fri, Dec 4, 2015 at 12:01 PM, maximal@wanko.com
mailto:maximal@wanko.com mailto:
> maximal@wanko.com mailto:maximal@wanko.com [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com> wrote:
>
> >
> >
> > Well, you can check the base table columns first; then check the
> > mattribute and attributecfg columns. If you verify (or modify) those for
> > UPPER(25), you should be good. For sure, if it bombs on insert/update,
> and
> > SQL logging is set to INFO, you'll see the problem table.
> >
> >
> > ---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <
> yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com
mailto:yudi.irianto@ytljt.com mailto:yudi.irianto@ytljt.com> wrote :
> >
> > Hi all,
> >
> > I have some problem that i cannot fill in followup work in Workorder
> > module (Maximo 7.5.0.1). It says: "BMXAA4049E - The value specified
> > XXXXXXXXXXX exceeds the maximum field length. Enter a value that fits
> into
> > the length of this attribute."
> >
> > This was happended during amend workorder.wonum to UPPER(25) but
> supposed
> > this is one of Maximo bugs that it didn't change field: RELATEDRECORD.
> > RELATEDRECKEY. Try to resize and make it same as WORKORDER.WONUM. This
> was
> > solved more than 3 years ago.
> >
> > rgrd,
> > yudi
> >