IJ47075: PROCESSING RULE IS IGNORING SCIENTIFIC FORMAT PROPERTY CONFIGURATION.

APAR status

• Closed as program error.

Error description

• Problem Description
  On TPAE 7613 processing rule is ignoring scientific format
  property configuration, publishing in the scientific format even
  if the value mxe.int.usescientific is 0.
  
  STEPS TO REPRODUCE:
  The steps below use MAXDEMO as an example:
  1)Go to System Properties application and check if the value of
  the property mxe.int.usescientific is 0.
  If it is not, update to 0.
  
  2)Go to Publish Channel application, search for
  MXINVOICEInterface.
  
  Select INVOICECOST table.
  
  Click on New Row button in the Processing Rule section.
  Rule: Test
  Action: SET
  
  Click on Add/Modify Conditions.
  Click on New Row in teh Continions section.
  Click OK.
  
  Click on Sub-Record Fields.
  Click on New Row.
  Field: LINECOST
  Value: 3333333333333333
  Click OK
  
  Enable the Event Listener.
  
  3)Go to Invoices application.
  Create a new record as below:
  Invoice: PF01
  Company: SKF-GO
  
  Click on Invoice Lines tab. Create a new row.
  Line Type: Service
  GL Debit Account: 6000-200-000
  Unit Cost: 123
  
  Save. Approve Invoice
  
  RESULTS:
  Linecost field will publish the value in scientific format.
  3.333333333333333E15
  
  EXPECTED RESULTS:
  If the value of the property mxe.int.usescientific is 0,
  scientific format should not be used.
  
  REPORTED IN VERSION:
  Tivoli's process automation engine 7.6.1.3
  
  Observation:
  This issue was introduced on TPAE 7613.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Integration Publish Channel users                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Publish Channel processing rule ignoring                     *
  * mxe.int.usescientific                                        *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR will be contained in a future release.
  

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

  INTEGRATION

• Fixed component ID

  5724R46I1

Applicable component levels