IV66182: VOID RECEIPT ON SERVRECTRANS USING INCORRECT DATE TO SET PERIOD IN ORACLE ADAPTER

APAR status

• Closed as program error.

Error description

• Environment:
  IBM WebSphere Application Server 7.0.0.21
  IBM Maximo Asset Management 7.5.0.5 Build 20130903-1504 DB
  Build V7505-00
  
  Tivoli's process automation engine 7.5.0.5-IFIX20140402-1137
  Build  20130903-1504 DB Build V7505-43 HFDB Build HF7505-08
  
  Oracle Adapter 7.5.0.0-20140305-1724 Build 20110805-1549 DB
  Build V7500-04 HFDB Build HF7500-01
  
  IBM TPAE Integration Framework 7.5.1.0 Build 20130829-1209 DB
  Build V7510-28
  
  Server OS Windows Server 2008 R2 6.1 build 7601 Service Pack 1
  
  Server DB Microsoft SQL Server 10.50 (10.50.2550)
  
  
  Concerns/Problem:
  VOIDRECEIPT on SERVRECTRANS using incorrect date to set period
  in Oracle Adapter
  
  We found an issue with the posting of a GL Transaction for a
  VOIDRECEIPT in Oracle. Here is the scenario,
  We had a service received on 9/29/2014, this means that this
  was posted into the September period. Our September period
  ended on 10/01/2014 but we have an accounting close date of
  10/3/2014. On 10/7/2014, a VOIDRECEIPT was entered for the
  service. In Maximo, the financial period on the void was
  correct, it was 201410 however when it sent to Oracle, it was
  posted to the September period. This is because the Adapter
  uses the ENTERDATE to set the ACCOUNTING_DATE on the
  GL_INTERFACE in Oracle. In this scenario, Maximo should use the
  TRANSDATE instead of ENTERDATE.
  
  The steps I have tested the issue on a demo:
  From the Financial application - select action, to set the
  correct financial periods (one month has one record and set the
  September period closed).
  Find a PO with receipts completed in September, but not
  invoiced.
  From Receiving application, open this PO and click "Select
  Receipts to Void".
  
  Discussed this issue with Oracle MEA experts, they provided the
  below comments:
  In Maximo new release, the void receipts for services will pop
  up a stop message for Entered Date if the date is in closed
  financial period
  Maximo will fix this issue by having the same message for MX75
  in Void Receipts for service. With this fix the Entered Date
  should be valid for Oracle adapter.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users who utilize an Oracle database and are          *
  * attempting to void received services.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When voiding a service receipt, the transaction may be       *
  * posted to the wrong financial period, if the service was     *
  * received in a previous financial period.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is included in the following package:
                        | Release 7.5.0.11 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

  INTEGRATION

• Fixed component ID

  5724R46I1

Applicable component levels

• R750 PSY

     UP

• R760 PSY

     UP