IJ28393: CALCULATION OF PURCHASE ORDER SECONDARY LINE COST ERROR BMXAA4163E WITH SMALL CURRENCY EXCHANGE

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  BMXAA4163E - The specified value 10,001.00 exceeds the maximum
  field length for the Unit Cost field.
  
  PROBLEM DESCRIPTION
  The calculation of the Unit cost when there is a small exchange
  rate is causing the field to be larger than the Database
  Configuration would allow when the Purchase Order is revised.
  
  PRE-REQUISITES:
  1. Go to Organizations, select EAGLENA and check:
  Base Currency 1: USD
  Base Currency 2: AUD
  
  2. Check the Exchange rate between USD and AUS
  Exchange Rate -> EAGLENA
  Convert from Currency = USD, Convert to Currency = AUD is
  0.0000630
  NOTE: There is no need to have AUD to USD.
  
  3. Go to Database Configuration to verify field length.
  Object: POLINE -> TAB Attributes
  Attribute: LINECOST: DECIMAL 10, Scale: 2
  UNITCOST: DECIMAL 10, Scale: 2
  These are standard out of the box settings
  
  STEPS TO REPRODUCE:
  
  4. Go to Purchase Orders -> NEW 1125
  Currency: USD
  Company: MROMKT
  
  5. TAB -> PO Lines -> New Row
  Line Type: Item, 1002 (it could also be Material)
  Quantity: 1.00
  Conversion Factor: 1.00
  Unit Cost: 10000 and tab out or save
  Work Order: 1005 (needs to be APPR status)
  Save
  Approve Purchase Order
  
  6. Revise PO
  Go to PO Line field, Unit Cost: 9999 tab or save
  
  System Message BMXAA4163E - The specified value 9999 exceeds
  the maximum field length for the Unit Cost field. The maximum
  length is specified in the Database Configuration application.
  
  NOTE: 9999 errors, also 10001, or 10000.01
  
  EXPECTED BEHAVIOUR:
  The Purchase Order unit cost should be saved as it is within
  the Database Configuration settings.
  
  SYSTEM INFO
  Tivoli's process automation engine 7.6.1.1
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of Purchasing with multiple currencies                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The calculation of the Unit cost when there is a small       *
  * exchange rate is causing the field to be larger than the     *
  * Database Configuration would allow when the Purchase Order   *
  * is revised.                                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  	  Release 7.6.1.3 of Base Services
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels