Maximo Open Forum

Hello,

I cannot enter the unit cost & line cost greater than 9 digits i.e (100,000,000).I'm getting below errors.

1- "The specified value 100000000 exceeds the maximum field length for the Unit Cost field. The maximum length is specified in the Database Configuration application. (BMXAA4163) More information"
2- "You entered more digits before the decimal point than is permitted in the field. (BMXAA4081E) More information"

 Default  PO and POLINE cost fields length is (Length=12 & Scale=4).

From Database Configuration i updated the cost and amount length:

Firstly, I tried to update the length from PO&POLINE to ((Length=16 & Scale=2). I got the same error.
Secondly, I tried updating the amount length from More Action  "Field Length and Format" and changed the value from 10 to 14. I still get the same error.

Your support is highly appreciated!

Regards,

Anna

#Purchaseorder  #po #fieldlength #unitcost #linecost #poline

#Customizations
#EverythingMaximo
#Procurement

------------------------------
Anna Max
QG
------------------------------

Anna, the data you capture in the unit cost and line cost fields on PO lines is ultimately going to flow to other places, including both decimal and amount-type fields in objects such as matrectrans and matusetrans, and depending on the nature of the purchase, this data may flow to actual cost fields on work orders, etc.  So you are going to need to modify the length of all the attributes to which costs can flow.  The attributes that are decimals will have to be updated individually.  Unfortunately, there is not one attribute that is the "same as" source for all the cost attributes, so you'll have to hunt through the database for the affected fields. In the database configuration application, you can query for tables that contain attributes like "COST". The length of the amount attributes is controlled globally by updating the length for amount-type fields in the Field Length and Format dialog box (Select Action > Field Length and Format).  Note that this action will affect all Amount attributes.     

------------------------------
Nancy Lerner
Brio Consulting
------------------------------

Thanks a lot@Nancy Lerner,

you are right. i also took the the cost field relationship with other tables for this reason i queried all cost tables and adjusted their length, after applying the change in DB configuration from UI, the change was not reflecting and working.  im getting the same error message.

Then i triesd to increase the "Amount Length" from (More Action - Field Length and Format" this was affecting around 121 other objects i applied the change still this approach was not working for me.

I didn't change any value for each (Amount Scale, Integer Length and Small Integer Length) as i thought it does not have any impact and even if i adjust them it will affect almost the entire objects . I don't want to do that!

I'm still looking for a solution to increase the amount fields without any harm.

------------------------------
Anna Max
QG
------------------------------

Original Message:
Sent: 07-02-2024 09:20
From: Nancy Lerner
Subject: Purchase Order Unit Cost & Line Cost Field Length Error

Anna, the data you capture in the unit cost and line cost fields on PO lines is ultimately going to flow to other places, including both decimal and amount-type fields in objects such as matrectrans and matusetrans, and depending on the nature of the purchase, this data may flow to actual cost fields on work orders, etc.  So you are going to need to modify the length of all the attributes to which costs can flow.  The attributes that are decimals will have to be updated individually.  Unfortunately, there is not one attribute that is the "same as" source for all the cost attributes, so you'll have to hunt through the database for the affected fields. In the database configuration application, you can query for tables that contain attributes like "COST". The length of the amount attributes is controlled globally by updating the length for amount-type fields in the Field Length and Format dialog box (Select Action > Field Length and Format).  Note that this action will affect all Amount attributes.     

------------------------------
Nancy Lerner
Brio Consulting
------------------------------

Hi @Anna Max!

You are going to have to increase the length of the amount field and that is something that impacts the entire database where an amount field exists. 

Regards!

------------------------------
Martin Fabra
ARSAT S.A. - Actively seeking employment
------------------------------

Hi Martin!

That is true, When made change, this affected all amount fields in the database. I had a backup before making this change.

Thanks a lot for your input and response to my query!

------------------------------
Anna Max
QG
------------------------------

Original Message:
Sent: 07-02-2024 22:12
From: Martin Fabra
Subject: Purchase Order Unit Cost & Line Cost Field Length Error

Hi @Anna Max!

You are going to have to increase the length of the amount field and that is something that impacts the entire database where an amount field exists. 

Regards!

------------------------------
Martin Fabra
ARSAT S.A. - Actively seeking employment
------------------------------

Hi Anna,

When you have length = 12, scale = 4, you really have the ability to add numerical numbers of 8 digits before the decimal point and 4 digits after the decimal point.

In order to add larger numbers you have to increase the length to allow for the larger number.  Since you are talking about a cost field, you can adjust that from Database Configuration.  A change has already been made so that you have 4 decimal places, though I'm not sure who would have made the length shorter.  The following screenshot shows the standard configuration.  Please remember that this is a major change in Maximo, you MUST have a database backup before actioning the change.

My curiosity is peaked as what requires such huge numbers.  I can only think of one scenario, that is a country with very high inflation so the currency is in like 1 billion is like USD $1.00.

------------------------------
Craig Kokay
Principal Consultant
COSOL

email: craig.kokay@cosol.global
#IBMChampion
------------------------------

Hi @Craig Kokay,

Thank you a lot for your response!

This change is required for only a specific PO in which its currency was not USD and it has a large currency denomination.
From database configuration, I had to increase the decimal field length of all related tables to 16 and also I changed the amount length from "More Action > Field Length and Format" to 16 which is beyond the standard. 

I took a backup of db and followed the below link instructions to make the required change and it worked.

https://www.ibm.com/support/pages/node/533279
 

------------------------------
Anna Max
QG
------------------------------

Original Message:
Sent: 07-03-2024 11:18
From: Craig Kokay
Subject: Purchase Order Unit Cost & Line Cost Field Length Error

Hi Anna,

When you have length = 12, scale = 4, you really have the ability to add numerical numbers of 8 digits before the decimal point and 4 digits after the decimal point.

In order to add larger numbers you have to increase the length to allow for the larger number.  Since you are talking about a cost field, you can adjust that from Database Configuration.  A change has already been made so that you have 4 decimal places, though I'm not sure who would have made the length shorter.  The following screenshot shows the standard configuration.  Please remember that this is a major change in Maximo, you MUST have a database backup before actioning the change.

My curiosity is peaked as what requires such huge numbers.  I can only think of one scenario, that is a country with very high inflation so the currency is in like 1 billion is like USD $1.00.

------------------------------
Craig Kokay
Principal Consultant
COSOL

email: craig.kokay@cosol.global
#IBMChampion
------------------------------