APAR status
Closed as program error.
Error description
While trying to enter a negative value in "Unit Cost" field in Invoice Line of an invoice designated Type=CREDIT, getting the following error BMXAA8123E - Errors exist in the application that prevent this action from being performed. Correct the errors and try again. BMXAA4175 - Positive value required for field Unit Cost. STEPS TO REPRODUCE: Go to Invoice application Create a new invoice Populate the Type field = CREDIT Populate the Vendor Field= FSC Click on Invoice Lines Click new row Create an invoice for either service or standard service Populate the Unit Cost field= -30.00 (negative value) Populate the GL account field Save the Invoice RESULTS: Receive system message BMXAA8123E - Errors exist in the application that prevent this action from being performed. Correct the errors and try again. Click on the Unit cost and you will see BMXAA4175 - Positive value required for field Unit Cost. EXPECTED RESULTS: Should be able to create an invoice of Type CREDIT with an invoice line with a negative unit cost . Business Case use case for this functionality is based on the following scenario: When invoices are paid to large construction vendors, a portion of each invoice is held back for quality and validity checks and then released once performed. The issue being encountered based on the way it currently functions is that if the first invoice has come in, and a mistake was made in the invoicing process by the vendor and they need to re-invoice, it is requried to then submit a credit invoice which needs to show a negative unit cost. Here is the scenario in detail: PO?s are setup in the following manner: PO Line 1 for Construction Services for +$100,000 PO Line 2 setup for HOLDBACK (10%) for -$10,000 PO Line 3 setup for RELEASE (10%) for +$10,000 The reason the Holdback and Release lines are setup in this way is that they have to be accounted for by a specific GL Code per Site ID that must indicate how much money has been held back. Upon release of the funds, it is then removed from this account. When an invoice comes in for any value on the PO it is setup as such: Invoice Line 1 for +$20,000 worth of Construction Services against PO Line 1 Invoice Line 2 for -$2,000 for 10% holdback against PO Line 2 Once it has been inspected for quality a 2nd invoice comes through requesting the release of the funds which the invoice looks like this: Invoice Line 1 for +$2,000 against PO Line 3 The issue being encountered based on the way it currently functions is that if the first invoice has come in, and a mistake was made in the invoicing process by the vendor and they need to re-invoice, they would then submit a credit invoice that should look like the following: Invoice Line 1 for -$20,000 worth of Construction Services against PO Line 1 Invoice Line 2 for +$2,000 for 10% holdback against PO Line 2 (as the initial invoice is no longer valid) As they might have only been paid $18,000 for the work and held back $2000, they cannot be credited for a full $20,000, therfore the holdback must be accounted for as such. Now due to Credit requiring has inverse signs, the above invoice would be of CREDIT type, but the first line would show POSITIVE in the app, and the second line would show NEGATIVE in the app ? this is currently being prevented by the current behavior on the CREDIT invoice i.e. not allowing a negative unit cost on an invoice of Type CREDIT. . REPORTED IN VERSION: IBM Maximo Asset Management 7.6.1.2
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO * **************************************************************** * PROBLEM DESCRIPTION: * * QTY IN CREDIT INVOICE LINE NOT ACCEPTING NEGATIVE VALUE * ****************************************************************
Problem conclusion
The fix for this APAR is contained in the following maintenance package: release\fix pack for Release 8.x Product
Temporary fix
Comments
APAR Information
APAR number
IJ43361
Reported component name
MAXIMO ASST MGM
Reported component ID
5724R46AM
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-10-04
Closed date
2023-02-25
Last modified date
2023-02-25
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
25 February 2023